Multi-language support in the futur ?

[cyberyeye]

Sorry if this question has already being asked, but i've done a quick search, and i find no topic about this....

Something like a language.ini config file in gk dir, would be great to translate Gk in other language :-)

Any chance to see something like that in 0.29 version ???

PS: thanks to all the dev team for the great great works done in a few weeks ;)

[cyberyeye]

Is my question so stupid ? No reply for my answer.....

:confused:

[len0x]

I see no connection between stupidity and no answers...
I think it's the right of developer to refuse answering a feature request before he makes up his mind...

p.s. it's highly unlikely that current GK will support other languages. May be "GK next generation" will (lets call it that) :)

[cyberyeye]

Thanks for your reply Lenox :-)

If Gk Nextgen will support a system of language.ini or whatever like that this will be a very good things :-)

[tHe gLouCh]

I just release a French version (in beta state, but fonctionnal I think) of GK 0.28.1 (based on CVS files).

If you are interested go to (french)
http://atlas2.tgv.net/~media-video/forum2/viewtopic.php?t=2370&sid=f8337c9946a3f2b248a8715190477dfa

@Lenox
It was not very hard to move const to ResourceString and then create internationalized .dll. The most difficult part, was translation ! But anyway it is a good start for any developper who wants to give another language version of this great tool.
If you want to see the source tell me..

PS: I have move all the ResourceString to a separate file. Is that a good idea for Team development ?

[len0x]

that's the spirit! :)

But I actually don't believe that making _every_single_label_ pointing to resourse string is a simple task. Very tidious work...
(but I'd like to see the code anyway)

P.S. I don't like dll approach - I like ini files better, since translation can be done by any non-programmer at all in that case...

[tHe gLouCh]

Well I am not talking user point of view, but developper. Because I don't think the "average user" will translate the ini file, but search for an already translated one. So why bother when you can add a .dll to an .exe ? If you have a french, german, etc.. developper to update the .dll, the "average user" will download it and "basta!".

I think you already know that but:

1- isolate the strings in resourcestring.
2- isolate the window interface (done by (3)).
3- create language dll with DLL Resource Expert.
4- translate the (1)
5- translate the (2)

and the work is done...

And so from that, when the team modify the REAL code or the interface, you "just" have to update via the Expert Resource DLL and translate new strings and controls labels.

This processus is done almost without touch of the REAL code. I am not talking about connecting controls labels, text, lines, etc... to .ini file, because as you say it is a tedious work.

Sample of code: I have just replace the strings in the source, include unit unRessources in the necessary .pas files, and translate the resourcestrings.

unit unRessources;

interface

resourcestring
errUnableToConnect = 'Unable to connect to the registry on %s (%d)';
S1Hour = '1 hour, ';
S1LittleNoise = '# 1) little noise';
S1Minute = '1 minute, ';
S1Second = '1 second.';
S2MediumNoise = '# 2) medium noise';
S3HeavyNoise = '# 3) heavy noise';
SAddingThisScriptTo = 'Adding this script to %s :';
SAntiShit = ' AntiShit: ';
SAppendingCredits = 'Appending Credits';
.
.
implementation
end.

[cyberyeye]

Thanks "tHe gLouCh" :-)

Great idea, even if this not a ini file "this is better than nothing" (translation of a french expression lol).

Excellente idée, meme si c'est pas un fichier ini, c'est déjà mieux que rien lol (translation in french of a bad translation in french-english lol).

o_o

Of course ini file would be great cause non-dev could participate for translating all string.

@All: Good works ;)

Gk NextGen ^^

[len0x]

Originally posted by tHe gLouCh
If you have a french, german, etc.. developper to update the .dll, the "average user" will download it and "basta!".


Haha, we don't :) And probably won't... So it's much easier to have just ini file which can be modified by anyone (So we don't even have any spelling error which require work of developer).

Originally posted by tHe gLouCh
This processus is done almost without touch of the REAL code. I am not talking about connecting controls labels, text, lines, etc... to .ini file, because as you say it is a tedious work.


Well, I don't see the point of translation just part of GK and leave another as it is... Proper translation means: not a single english word :)

Are you up for translating every single lable and doing all the connections?

[tHe gLouCh]

Well, I don't see the point of translation just part of GK and leave another as it is... Proper translation means: not a single english word
I have already translate 99% of GK in french (soon a GK0.28.2b french version will be online). And it has "not a single english word" !
Are you up for translating every single lable and doing all the connections?
First: done !
Second: why not ?

Well, as I said you must do 2 jobs:

Translate the strings in the code (ini or dll)
AND Translate the UI (ini or dll)

I have done a test in 1 form with the "FormStorage" component from the free rxLib. This component store any control's property you choose in an .ini file. Label, buttons Caption, etc... When you launch the program the .ini file is loaded and... It's working well !

BUT, there is a little speed decrease every time you open a window (not very annoying since GK has not so many forms).
BUT this component works only for UI controls. So, what for consts ? I have isolated ~400 strings to translate. What is the best method ? Use a TIniFile ?