Closed GoogleCodeExporter closed 9 years ago
Russian? Do you know that Russia is mother for this game? Proof:
http://nike.homeunix.com/assets/violetland-thread-1.xhtml It is better if you
will
help me with translating the game to English because actually I don't know much
English.
But seriously, it is more task for programming, not for translate. You can try
to
implement support of language files in the program.
I like that you are so active, but I think that the project needs of
improvements of
gameplay and design first.
Anyway we have now the issue for task of localization so it will not forgotten.
Original comment by 5253...@gmail.com
on 28 Jan 2010 at 6:40
interesting thought ;D i think it is not so hard to implement with gettext. i
can translate to german.
Original comment by filecorpse@googlemail.com
on 28 Jan 2010 at 10:00
There really not difficult get i10n for game. Actually I already made it :).
But this
is still need some preparations and cleanups.
First at all, game should support UTF-8: functions and fonts. For functions -
included patch.
For fonts... well, there many choices, I used DejaVu for testing.
Original comment by azamat.h...@gmail.com
on 15 Feb 2010 at 7:46
Attachments:
The system is in place, I just have to use the translation function in all
files and finish the french traduction. I'll make a tuto for other traductors.
Some strings are already translatable.
Original comment by come.bernigaud@gmail.com
on 15 Sep 2010 at 11:43
About the current i18n&l10n system:
- The xgettext command should be used by the development team whenever new
strings are added, so translators shouldn't actually care about it.
- Translations should have a folder, like 'po', where both violetland.pot and
language.po files should be saved.
- I think it's better to use the language code instead of the language english
name for the files, so 'fr.po' instead of 'gl.po'.
- It would be great if there were an script for developers to run it whenever
new strings are added, and that do an xgetext and then a msgmerge for all PO
files.
- PO files should be compiled during the installation.
Original comment by adriyeti...@gmail.com
on 20 Sep 2010 at 9:17
*'fr.po' instead of 'french.po'
Original comment by adriyeti...@gmail.com
on 20 Sep 2010 at 9:20
I'm doing a patch :)
Original comment by adriyeti...@gmail.com
on 20 Sep 2010 at 9:31
Don't know hot to create a patch for SVN so...
1. Remove both 'french.po' file and 'fr' directory.
2. Extract po.tar.gz in the main directory.
Now, you can run "generate.sh" from the 'po' directory to update POT and PO
files.
Original comment by adriyeti...@gmail.com
on 20 Sep 2010 at 10:16
Attachments:
use "svn diff" to do a patch
Original comment by come.bernigaud@gmail.com
on 21 Sep 2010 at 6:35
svn diff gave me troubles because of the deleted files ("'fr' folder not
found", or similar).
Original comment by adriyeti...@gmail.com
on 21 Sep 2010 at 11:53
Ok, I'll look at your tar.gz this evening ;-) (and probably commit the changes
you suggested)
Original comment by come.bernigaud@gmail.com
on 21 Sep 2010 at 1:51
By the way, it would be cool to make a "Call for translations" a couple of days
or a week before a release, so translators can update the PO files to make it
to the release :)
Original comment by adriyeti...@gmail.com
on 2 Oct 2010 at 11:14
Currently only I make releases, so I will making a "call" at google group. It
will be better if I share task of release making with someone.
Original comment by 5253...@gmail.com
on 6 Oct 2010 at 12:50
Original comment by 5253...@gmail.com
on 12 Nov 2010 at 11:38
Original issue reported on code.google.com by
feebleha...@mail.ru
on 28 Jan 2010 at 4:56