Suggestion for the SVN struct of discuz

fanha99

hi,

I have some suggestion:

1. Could you pls move the languages folder out of the "upload / source / language" and use external links instead?
reason: some one don't need all of the language inside, but when checkout (or update), it will pull all of them. Some time, they use there own language pack for edit or translate, it may make some conflict when check out?

2. Is there a way to put all the language pack inside the "upload / source" folder, and name it as "language_en", "language_sc", "language_vn" .... and still keep the origin as "language"?

just some suggest

vot

We have allready discussed this problem here:
http://codersclub.org/discuzx/fo ... &extra=page%3D1

My opinion as a coder:
It is easier to maintaint all the languages in one repository.

fanha99 want to move language packs from main package to separate repository.

Is there any other opinion?

fanha99

1. X2.5_trunk         
   
2.          readme
   
3.          upload
   
4.          utility
   
5. X2.5_language_trunk
   
6.          language_en
   
7.          language_sc
   
8.          language_...
   

Copy the Code

by default checkout, we will get:

1. upload/source/language      <--- keep the origin pack here, wiil help to check with origin
   
2. upload/source/language_en  <--- this folder is an external link to language_trunk/language_en
   
3. upload/source/language_sc  <--- this folder is an external link to language_trunk/language_sc

Copy the Code

when user need the other language, they will set the property of upload/source, then add some other extenal link to the lang they want, they can point to the langpack provide by coder, or just there own pack in case they are translating.

In my opition:
- in most of case, user down need all of the language pack. So don't need to waste time to download them all.
- for developer, we can use the extenal link to get all of them inside easily (but the source folder is in red) or just set an child check out inside. I this developer can handle this easily
- for end user, we can provide the language pack, and tell them where to get, and how to install. or just show them the direct link to their language pack SVN, they will check out and copy into there install.
- by setting all the language folder the same level as the origin language folder will help us (or just VOT) to compare when an update is ready.
- and the language folder look clear. with current setting, there is lots of file and folder inside, some of them is from origin pack, some of them is the other language. they are messing.

vot

All the x2.5ML language packs placed in a separate repository:

http://code.google.com/p/discuz-lang/

Attention:
The language repository is not SVN type, but Mercurial !!!
Because of Mercurial is more convenient for maintain.