Support Forums - XOOPS Web Application System

Subject:* <
Name/Email:* <
Message Icon:* <
Select* <
Message:* <	xx-Small x-Small Small Medium Large x-Large xx-Large Arial Courier Georgia Helvetica Impact Verdana Haettenschweiler Black Blue Brown Green Grey Orange Paper Purple Red White Yellow Click the Preview to see the content in action.
Options:* <	Enable Smiley Enable Xoops Code
Confirmation Code* <	7 - 4 = ? Input the result from the expression Maximum attempts you can try: 10
* <

Re: XOOPS 2.4.x Translations

by andrey3761 on 2010/7/13 14:38:15

XOOPS 2.4.5 Final Russian UTF-8
http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsLanguages/russian/core/2.4.5/

Re: XOOPS 2.4.x Translations

by sadistiko on 2010/4/23 5:28:30

I agreed with you DCrussader. Best practice for now is that new strings are added at end of file (and commented part is where are introduced - what version). I hope developers will continue this practice.

And about translating. I translate only when I have free time, and if I nedd new version of xoops imediately for some client upgrade or new instalation. So I usualy translate only RC or final version.

Re: XOOPS 2.4.x Translations

by DCrussader on 2010/4/22 14:35:52

Quote:

It's good to have 2.4.x translation, and then go ahead and start working on 2.5.0 Alpha, reusing what we can from 2.4.x

And using Winmerge or something similar, it should be easy to spot any new language definitions that need translation.

Better add new strings to be added in the end or beginning of each file, this way saves more time for the translators.

Also to NOT recommend translating Alpha/Beta release, bcz there are huge amount of changes, something added in Alpha 2, may drop in Beta 3, and in RC2 to be added analogue of this thing. Some of the translators wasn't here during the Mith's XOOPS releases.....

Winmerge is ok for 2-3 files.... but for the whole core ?

Or maintain changelog for language files too, example:
http://code.google.com/p/opencart/source/detail?r=105

Every file can be accessed via link, and the changes are marked in different color, also u can pick the diff files.

Every release of OC, have huge amount of changes to the language files, there is no stable (like XOOPS or Joomla), and this is the easiest way to find what's changed, where and what is not.

Re: XOOPS 2.4.x Translations

by andrey3761 on 2010/4/22 12:38:39

XOOPS 2.4.5 RC Russian UTF-8
http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsLanguages/russian/core/2.4.5/

Re: XOOPS 2.4.x Translations

by Mamba on 2010/2/11 15:21:10

Quote:

So - if you are are translating from the button my advice may be to wait to 2.5.0 release instead of 2.4.x

Michael: Do You agree?

It's good to have 2.4.x translation, and then go ahead and start working on 2.5.0 Alpha, reusing what we can from 2.4.x

And using Winmerge or something similar, it should be easy to spot any new language definitions that need translation.

And thank you for the latest Russian and Japanese translations!!!