Ditto<br><br><div><span class="gmail_quote">On 6/23/06, <b class="gmail_sendername">Doug Ewell</b> <<a href="mailto:dewell@adelphia.net">dewell@adelphia.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Joze Fabcic <joze dot fabcic at hermes dot si> wrote:<br><br>> My immediate aim is to create system which enables alternative English<br>> to be used exclusively. The system has functions similar to any other<br>
> language typically used for software localizations. The system also<br>> takes care of communicating with people using English written in<br>> another orthography.<br><br>This sounds like an elaborate and ambitious experiment, similar to a
<br>person localizing an operating system or major tool into Klingon.<br>Google provides "foreign language" interfaces in Mock Swedish ("bork,<br>bork, bork"), Elmer Fudd-speak, Hacker-speak, and Pig Latin, as well as
<br>Latin-script Klingon. This project reminds me of that.<br><br>> So, why do I need a registration of a language subtag? The second<br>> artifact already involves language designation. I want to have a<br>> language variant listed at
<br>> <<a href="http://l10n.openoffice.org/languages.html">http://l10n.openoffice.org/languages.html</a>>. If the <a href="http://openoffice.org">openoffice.org</a><br>> group doesn't want to cooperate, I can choose another, simpler,
<br>> program to start with. Without a language specification, a potential<br>> for confusion is larger.<br><br>The OpenOffice list doesn't appear a likely place for this kind of<br>innovation. All of the tags on that list are strictly "language" or
<br>"language-region", including the widely abused "zh-CN" and "zh-TW" for<br>Simplified and Traditional Chinese, and including a really odd pairing,<br>"sh-YU" for Serbian Latin and "sr-CS" for Serbian Cyrillic.
<br><br>Without at least a semblance of a base of users of Cut Spelling that<br>would take advantage of this new software, this particular project seems<br>more like an exercise in localization than a true language tagging need.
<br>I'm inclined to recommend "en-x-cutspell" as Addison has.<br><br>--<br>Doug Ewell<br>Fullerton, California, USA<br><a href="http://users.adelphia.net/~dewell/">http://users.adelphia.net/~dewell/</a><br><br><br>
_______________________________________________<br>Ietf-languages mailing list<br><a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">
http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br></blockquote></div><br>