Localized Strings

Post by **dlh** » Fri Jul 29, 2005 7:46 pm

We seem to have alot of Spanish players, but no Spanish translation. Can anyone recruit someone?

Post by **Lucifer** » Fri Jul 29, 2005 7:54 pm

Hmmm, I'll ask when I see. Maybe we can get Blade Runner to stop running for a few minutes and give up a translation?

If all else fails, I can probably throw one together with a spanish dictionary. I know enough of syntax and grammar in spanish to get away without making an All your base translation, but a native speaker would do a much better job.

(and be able to include all the accents and stuff)

Post by **Tank Program** » Fri Jul 29, 2005 8:05 pm

I could theoretically do it, but things may come out crazy sounding. I think a native speaker should do it. (One that understands both english and spanish very well. I understand english well, but I really do think I'd make a botch of the spanish. "/1 fuera matado a /2 por /3 puntos" etc.)

Walking Tree · Post by **Walking Tree** » Fri Jul 29, 2005 8:12 pm

as you're talking about accents: how well are non-ASCII characters supported ? Is there
a default character set ? which ?
And why can't I enter letters like 'ä' in the chat ? can this be changed ? [ where would I
have to look if I wanted to do it myself ? ]

klax · Post by **klax** » Fri Jul 29, 2005 8:56 pm

I started one time ago while ""working"" in the afternoons at my old job.
It's from April and very incomplete.
I'll try to recruit spanish people to help me

Accents aren't a problem in spanish (lot of people write without them), but the letter ñ is a problem :s

Edit: deleted posted very old and incomplete spanish.txt. Now in cvs there is a new one almost completed.

Website · Post by **Z-Man** » Fri Jul 29, 2005 9:06 pm

All non-ASCII characters are currently eaten by the networking system, Jonathan and Nemo found out that they may cause problems (Don't ask me why they should; Jonathan was able to do something bad to Nemo's server by sending them). And the input routines don't let non-ASCII characters through either; that filter is in uMenu.cpp, look for c.unicode if you want to play with it.
But locally, in the language files, all characters that are present in the fonts textures can be used.
I'll push up an update for the French accents shortly. The charset is the egocentric ISO Latin 1, but in the long run, we should be switching to Unicode with UTF-8 encoding in the files.

Luke-Jr · Post by **Luke-Jr** » Fri Jul 29, 2005 10:13 pm

z-man wrote:in the long run, we should be switching to Unicode with UTF-8 encoding in the files.

How are we going to pull that off, I'm wondering

There's a number of users using non-ASCII characters right now

Walking Tree · Post by **Walking Tree** » Fri Jul 29, 2005 10:37 pm

yeah... like 'Döner' and 'löcotus'...
I don't know much about how armagetron works at the moment, but switching to unicode
could be done by creating special unicode servers where old clients are immediately kicked.
New clients would forbid unicode on old servers.
That could be a clean (but very painful) solution.
Anyway, who am I to discuss the future of a armagetron when I haven't even (properly)
looked at the source code

Luke-Jr · Post by **Luke-Jr** » Fri Jul 29, 2005 10:58 pm

Walking Tree wrote:yeah... like 'Döner' and 'löcotus'...
I don't know much about how armagetron works at the moment, but switching to unicode
could be done by creating special unicode servers where old clients are immediately kicked.
New clients would forbid unicode on old servers.
That could be a clean (but very painful) solution.
Anyway, who am I to discuss the future of a armagetron when I haven't even (properly)
looked at the source code

Well, I guess in theory we could assume "pre-3.0 = Latin1 thing and 3.0+ = UTF-8"...

Jonathan · Post by **Jonathan** » Fri Jul 29, 2005 11:02 pm

Walking Tree wrote:yeah... like 'Döner' and 'löcotus'...
I don't know much about how armagetron works at the moment, but switching to unicode
could be done by creating special unicode servers where old clients are immediately kicked.

Not needed. UTF-8 is ASCII in the low half and extends it in the high half, so it's already almost 100% compatible. If a new version receives something from an old version it can easily convert characters in the high half to UTF-8. When sending something to an old version it can convert characters that exist in the old set, and replace/ignore others.

Walking Tree · Post by **Walking Tree** » Fri Jul 29, 2005 11:22 pm

Jonathan wrote:Not needed. UTF-8 is ASCII in the low half and extends it in the high half, so it's already almost 100% compatible. If a new version receives something from an old version it can easily convert characters in the high half to UTF-8. When sending something to an old version it can convert characters that exist in the old set, and replace/ignore others.

do you meen that the unicode-aware server functions as a character set translator in
that it converts UTF-8 to ISO-8859-1 as good as possible for old clients and alt least tells
the unicode-aware client that it's recieving ISO-8859-1 characters ?

that would indeed be a better solution, but before worrying about
inter-version communication, displaying unicode (read: japanese) could be a challenge...

Luke-Jr · Post by **Luke-Jr** » Fri Jul 29, 2005 11:42 pm

Jonathan wrote:Not needed. UTF-8 is ASCII in the low half and extends it in the high half, so it's already almost 100% compatible.

UTF-8 encompasses ASCII, correct, so it's 100% backward compatible... however, many people are relying on ISO-8859-1 encoding, which isn't.

Jonathan wrote:If a new version receives something from an old version it can easily convert characters in the high half to UTF-8. When sending something to an old version it can convert characters that exist in the old set, and replace/ignore others.

You mean when the server is new, I assume... As far as non-ISO-8859-1 characters, I think the standard behaviour is to convert them to "?".

Walking Tree wrote:do you meen that the unicode-aware server functions as a character set translator in that it converts UTF-8 to ISO-8859-1 as good as possible for old clients and alt least tells the unicode-aware client that it's recieving ISO-8859-1 characters ?

Converts, most likely. It's not very complicated

Walking Tree wrote:that would indeed be a better solution, but before worrying about
inter-version communication, displaying unicode (read: japanese) could be a challenge...

Nothing displays all unicode. Most of the characters aren't even defined, IIRC...

Jonathan · Post by **Jonathan** » Sat Jul 30, 2005 1:26 am

Luke-Jr wrote:
Jonathan wrote:Not needed. UTF-8 is ASCII in the low half and extends it in the high half, so it's already almost 100% compatible.
UTF-8 encompasses ASCII, correct, so it's 100% backward compatible...

Yes.

however, many people are relying on ISO-8859-1 encoding, which isn't.

Including Armagetron (OK OK, Armagetron is not people) which I meant with "it" above.

Walking Tree · Post by **Walking Tree** » Sat Jul 30, 2005 6:20 am

Luke-Jr wrote:
Walking Tree wrote:that would indeed be a better solution, but before worrying about
inter-version communication, displaying unicode (read: japanese) could be a challenge...
Nothing displays all unicode. Most of the characters aren't even defined, IIRC...

Good point

but japanese would be cool...
but, latin-type accents have higher priority since we have any spanish, french, german and
pollish (not ISO-8859-1 afaik) players (and a few swedish ones )

klax · Post by **klax** » Sat Jul 30, 2005 11:27 pm

Almost complete spanish.txt commited to cvs

I trashed the old one. This time I mixed some translations from english and some from french, and I believe the result is quite good.

All day working in this uff (I heard lot of music while translating hehe)
Tomorrow I'll change of discography and I'll finish it.