On Tue, 07 Aug 2007, Tim Ansell wrote:
> > Hummm...
> > True that we only localise the message body, not the args.
>
> Don't forget JLP's post about argument positions - we can't just use a
> printf like system is seems.

True. I forsee pain and suffering for me.

> > And what would you do for player uploaded messages?
>
> I think we just ignore them for the moment. It's not a problem that is
> really solvable. If you really wanted you could run them through an
> automatic translator :)
>
> Mostly people will play on servers with people who speak their own
> language, this may not be english :)

True. Do we need to be able to tag a message to say its in a particular 
language?

> > > It would also allow two players of different languages to share an
> > > account.
> >
> > Really? Why would that be helpful?
>
> Or the same player to switch between languages?

Hummm.... true.

> > > I'm not sure if I like this method or not, it would be trivial for me
> > > to implement in tpserver-py, but it might be much harder to
> > > tpserver-cpp.
> >
> > Not really too hard.
>
> ***
> So using a filter is a good idea?
> ***

How many languages are there? 

/me checks wikipedia

6,000-7,000 languages (approx)
26^2 = 676 possible two char codes (ISO 639-1) (ie, EN, FR, etc.)
26^3 = 17576 possible three char codes (ISO 639-2) (ie, eng, fra, etc) (464 
currently assigned)
10,000's two char plus location (ISO 3166) (ie en-AU, en-NZ, en-US, etc)
(Start on the page on "Language Code")


Feature space is 2^32.
Assigned spaces are:
0xffff - 0xffffffff for optimisations
0x1000 - 0xffff for filters
7 individual assignments.

Filter space is 65536 - 4096 = 61440
Two are assigned, range appears to be 0x1000 to 0x1fff, leaving 0x2000 to 
0xffff available, 57344

We would need a sane way to assign filter ids (feature ids) to languages, 
preferably without having to keep a list ourselves. Either find a (ISO or 
IETF) standard list giving integers and adding 0x2000, or mapping two or 
three char (ISO) codes to integers in the range. I think I prefer the second 
(less lookup/simpler conversion).

This doesn't address how i18n will be done for messages from the server, but 
would give a way to set the language.

Given that 57344 > 7000 and your stated preference to use filters for this 
purpose, I guess that will be fine.

> Mithro

Later
Lee

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel

Reply via email to