81
andrey3761
Re: XOOPS 2.4.x Translations


82
anderssk
Re: XOOPS 2.4.x Translations
  • 2010/2/10 21:10

  • anderssk

  • Quite a regular

  • Posts: 335

  • Since: 2006/3/21


Be aware! The 2.5.0alpha has a lot of changes.
All files in the system module is changed.

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?

83
omeech
Re: XOOPS 2.4.x Translations
  • 2010/2/10 21:31

  • omeech

  • Just popping in

  • Posts: 28

  • Since: 2009/2/28


It is possible that 2.4.5 will be final in versions 2.4.xx
Therefore, a high-quality translation for this version.
or am I wrong?

84
KeiichiSHIGA
Re: XOOPS 2.4.x Translations

I show a Japanese language file experimentally as topic of this place

https://code.google.com/p/xoops-japanese/

There was not inconvenience and reflects it to SourceForge.net.

85
ghia
Re: XOOPS 2.4.x Translations
  • 2010/2/11 8:09

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


It is looking good! I think you are on the right way with this!

86
Mamba
Re: XOOPS 2.4.x Translations
  • 2010/2/11 15:21

  • Mamba

  • Moderator

  • Posts: 11251

  • Since: 2004/4/23


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!!!

87
andrey3761
Re: XOOPS 2.4.x Translations


88
DCrussader
Re: XOOPS 2.4.x Translations

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.
May The Source Be With You!

89
sadistiko
Re: XOOPS 2.4.x Translations
  • 2010/4/23 5:28

  • sadistiko

  • Friend of XOOPS

  • Posts: 477

  • Since: 2004/12/13


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.
Croatian Xoops support site:
www.xoopshr.org
Lowcost linux hosting:
www.adpgroup.hr

90
andrey3761
Re: XOOPS 2.4.x Translations


Login

Who's Online

67 user(s) are online (42 user(s) are browsing Support Forums)


Members: 0


Guests: 67


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits