First extend packages (and projects) with a languages directory with po
files. When a project is built (or published) all language files of all
dependent packages will be gathered add add in a languages subdirectory
relatively to the executable or at another predefined place (i.e.
/usr/local/share/appname/languages), configurable like the Help file of an
application now. On startup all resourcestrings will be read from the
appropriate files.
I will not write tools to create or maintain po-files, just make it easier
to use po-files in applications.
I hope this makes clear, what my plans are.
he first hint i have to this, is not to translate simply at app startup.
the user must can retranslate the app at runtime.
And at example for me any translation feature that cannot be used by the
end-user is useless for me.
When lazarus dont use standart gettext tools / formats for the translation
its absoulutly useless for me and i think also for
some other peoples. My example in the last mail was the vr-china. I dont
speak chinese but they can make her own translation
from english. Also belgium i dont speak ther language but the have maked
ther own translation with gettext tools.
I think its better to stay compatible to the gettext package.
Christian
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
