=2 means: as far as we know, the language tag is customarily used with all of these scripts, and no others.Unfortunately, this interpretation breaks down because of Braille. There are hundreds of languages that can be written in Braille script, not one of which is written solely in that script. So to specify Braille alone would be misleading, to specify Braille and other scripts would be as hard as Suppress-Script, and to omit Braille would be to say that it should not be used with (otherwise) multiscript languages.
Braille is an example of a script you would always have to identify. That is, it represents *exactly* the sort of "distinguishing value" that requires a script subtag.
It is useful to note that *no* languages are "natively written" in Braille. There are hundreds of languages that are transcribed into Braille, and, while there is no doubt that some--even many--texts are authored natively in Braille, there is also no doubt in my mind that no language claims it as a primary script (i.e. documents are not "customarily" written in it, they are always *exceptionally* written in it).
It's non-listing in the registry means exactly the foregoing: if you have a document in Braille, then you, by all rights, really SHOULD tag the content as being in Braille, as it will most probably be inaccessible to native speakers of the language. Just as if, when I find an English document written in the Arabic script, I would naturally feel compelled to identify that fact: "en-Arab".
The "two or more" rule for Script would mean, basically: yes, this language (say Serbian) is customarily written in the script you are using (say Cyrillic). You still need to identify the script because there are other common scripts for this particular language.
addison -- Addison Phillips Globalization Architect -- Yahoo! Inc. Internationalization is an architecture. It is not a feature. _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.