The ISO list of codes could be used for the languages, but ignoring the actual codes in favor of autonyms. IOW, if a language is on the list, it should have a name (although all languages should have names), but not using the code itself in the formation of that name. Many of the languages will, of course, have names that are similar to the codes, since the codes were apparently based on the autonyms.
stevoOn Wed, Mar 31, 2010 at 11:00 AM, Christopher Doty <suomichris@gmail.com> wrote:
On Tue, Mar 30, 2010 at 18:29, Oren <get.oren@gmail.com> wrote:If we want a dense and obvious indicator, we can just use { gugde + <ISO 3166-1-alpha-2 code> }No, I'm serious.Man, I keep looking at that and going back and forth. It does have a certain elegance, but is also has a certain, you know, just saying codes. I think the main problem with this method is--what if the ISO changes the codes, as recently happened with the language codes? I'm not sure the meanings of Lojban terms should be tied to the ISO codes, although I do still think the ISO lists are a great place to start.Oren, can you clarify what you meant by "top-level" before in terms of language codes?Chris--You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
--
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.