In the Internationalization HOWTO page I mentioned technosauruses/L18L's 't12s' method and that it might be our preferred method. However, the DoOcracy has been demonstrated, with rodin.s submitting a huge collection of files using the 'gettext' method.
However, the t12s method is good and any existing non-internationalized scripts or future scripts will be welcome to use it.
Note, Woof currently only has one t12s'ed script, /usr/sbin/xdelta_gui.
Blog post on t12s:
Earlier blog post describing localization:
What I am planning on working on next is a GUI tool to make it easy to create translation files. We have the i18n'ed scripts (and some XML and .desktop files) but now need to make it very easy for users to create non-English translations. This will be for the gettext'ed scripts.
I might be a bit unresponsive to other to-do requests for a few days
Comments:Posted on 5 Feb 2012, 10:17 by shinobar
I have to express my thought on the 't12s' system.
First of all, i cannot see what is the problem in 'gettext' and what is the issue the 't12s' intends to improve.
Posted on 5 Feb 2012, 10:57 by technosaurus
flat text files are more accessible to edit
(everyone can use a text editor, making it easier to contribute translations)
gettext is not available in initrd
gettext is necessary for compiled programs but unnecessary in scripts - people just used what was already in use
gettext files don't compress as well on an sfs
gettext requires additional work
on the other hand if something is already gettexted...
gettext is only slightly slower
gettext is only a small extra dependency and is going to be there as long as there is any compiled NLS-enabled program
really its not worth changing if the translations are already done in gettext
Posted on 5 Feb 2012, 20:39 by shinobar
Is the t12s easier than gettext?
[quote="technosaurus"]flat text files are more accessible to edit[/quote]
The .po files are flat text file and the tanslayers can post .po files using editors,
but using poeditor or something is easier i guess.
T12s flat text files can be edited by using editors, but using t12s editor is better.
I cannot find any difference between the gettext and the t12s.
The point is which is familiar with the gettext or the t12s.
Anyway, the gettext is essential for Puppy applications and the t12s is not.
I have already pointed out the no meaning of the running time.
I cannot find any applications slowed by the gettext messaging.
Posted on 6 Feb 2012, 2:57 by argolance
... I guess I actually don't see benefits translators can get from this way to internationalize applications compared to gettext and poeditor...