[Deagle]

Originally Posted by sanaell every lang can be support but you must use the ENGLISH ALPHABETIC RESTRICT so only the azertyuiopqsdfghjklmwxcvbn character can be support no àéèÜÖÏËÄ etc....

sure but why are u shouting?
i normally use the ENGLISH ALPHABETIC RESTRICT
and Turkish is also european alphabetic with a few changes

[NiLuJe]

Wheeeeeee \o/

Good Job ;]

Looking for french translators? We're here ! ;)

[sanaell]

Originally Posted by NiLuJe Wheeeeeee \o/ Good Job ;] Looking for french translators? We're here ! ;)

lol first

[johnjg75]

hmm, sounds like a good idea, i guess those four months of planning and coding paid off, good work guys

[daRope]

Nice idea, but...

You first mention that the translation.txt files use language sections titled [english], [german],[french] and so on. But then you mention further down in the text "two letter language codes". You never say what the user should use when setting a language in his client. So which is it?

I have an issue with the way you chose to set the client language. As you should be aware the space available in the setinfo buffer is very sparse. Statsme even managed to already fill it all up. So saving on setinfo buffer space is paramount. If you plan to make users set their client language with "_language english", that would be an unnecessary waste of space, IMNSHO.

That's why I urge you to make another change before you release and use "lang" as the setinfo key and the standard two letter language codes for the value. People could even use the three letter extensions for sublanguages if they want to and still have a shorter value than most language names. That means that a client would set his language to english with "lang en", saving ten valuable bytes of the setinfo buffer compared to version above.

It also has the added benefit that the size of the setinfo key-value pair has a fixed maximum, the language has not got to be sepcified in english and it prevents ambiguosity using de-facto standard language codes.

[sanaell]

vote for 3 letter code

FRE
ENG
GER

[SniperBeamer]

setinfo _language en
but there will be a menu where you can set the language

[Deagle]

dude i can use english letters to translate without any problems and so can u, besides most letters out of the english alphabet doesnt show right
in game lets keep it simple... ur looking for a turkish translator or danish for that matter im here!

[Johnny got his gun]

Two letters should be enough considering the top level domains only use two (se, dk, uk, fr etc)

[daRope]

Originally Posted by SniperBeamer setinfo _language en but there will be a menu where you can set the language

Then why use english language names in the txt files? Isn't that confusing?

And I still urge you to use lang instead of _language as the setinfo key.