Ævar wrote:
That still doesn't avoid the problem of
1. Us allocating a site under a SIL code or some draft
ISO spec
2. ISO allocating a code that equals the SIL code for a different
language or the ISO changing its mind in the final revision of its
standard
3. Us having to deal with the mess
Which is why I think it would be a good idea to put
languages that
don't have *official* ISO codes or only have SIL codes under some name
that defenetly won't conflict with future ISO allocations.
Me too, I believe those codes will be taken over as they are now when ISO 639-3 will
become official. But then again, believing is not knowing, of course.
I'm not sure if using caps for subdomain names will prevent more confusion than it
will possibly cause to many users.
A while ago, when this issue was discussed at Wikipedia-l somebody (could've been
me, not sure...) suggested to use locally defined four-lettered codes for languages that
don't have ISO codes yet. Thus, any potential interference with future ISO codes (in
other words: "mess") could definitely be avoided. Plus it's probably more
user-friendly than those somewhat clumsy three-plus-three letter codes.
Arbeo
---------------------------------
Sarah Connor, Moshammer oder Papst Benedikt die Top-Suchen 2005.