Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years ago. Active 9 years ago. Viewed 10k times. Would it make any difference? Archived Forums. Also discuss all the other Microsoft libraries that are built on or extend the. Sign in to vote. Wednesday, April 23, PM. Hi mljj, As far as I know, there is a CultureInfo class in.
For example: Code Snippet. Friday, April 25, AM. C is mostly used for implementing operating systems and embedded applications. FR - CH.
FR -CI. Write Your Answer. Similar Asks What is the mean of the sample means? The tag always begins with a language subtag - either one of the ISO codes or a registered value. It can then, optionally, be followed by various subtags. Today there are five kinds of subtags that follow the language identifier: scripts, regions, variants, extensions, and private use. The order, length, and content of each subtag type is fixed, so a tag processor can always identify exactly which type of subtag it has, even if the processor doesn't have that subtag in its copy of the registry or has no copy of the registry at all!
Script subtags we've already met. These are based on ISO and indicate the writing system. The script subtag can occur at most once it may be omitted and must appear directly after the language. Some languages have a field in the registry indicating that a particular script code should be "suppressed".
For example, "zh-Hant" and "zh-Hans" represent Chinese written in Traditional and Simplified scripts respectively, while the language subtag "en" has a "Suppress-Script" field in the registry indicating that most English texts are written in the Latin script, discouraging a tag such as "en-Latn-US".
Region subtags we've also met: these are based mostly on ISO code and indicate the country or regional variation. The region code can also include selected UN M. The region code can occur at most once it may be omitted and must follow any language and script codes. Variant subtags are not based on an external standard. They are all individually registered values, mostly indicating particular dialects or other language variations not covered by scripts or regions.
Multiple variant subtags can be included in a tag. Each variant has fields in the registry, though, indicating which subtags it is intended for use with. For example, the "nedis" subtag has a prefix of "sl" Slovenian since it represents a dialect of Slovenian. Variants shouldn't be used together unless one variant lists the other in its "prefix".
Extensions are a mechanism whereby future additions to language tags can be standardized. Each extension has a single character subtag a "singleton" that identifies it.
Various restrictions apply to extensions and how they are formed, used, and administered. Extensions form the basis for future addition of features to language tags. Private use. Private use subtags are not based on any standard at all.
They are for use by individuals or groups that need to identify something language related that might not rise to the level of standardization. RFC included private use tags, but the whole tag was private use this is still valid, of course.
Now private use and generative subtags can be used together. The single-letter subtag "x" identifies where the private use subtags begin. For example: en-US-x-twain might identify writing by Mark Twain between two colleagues studying American literature. One benefit of this ability to mix the two is that vendors who extend language tags for proprietary reasons in the future can do so while preserving the maximum amount of interoperability between their system and others.
The new tag syntax uses length and content to distinguish each type of subtag, making it easier than ever to validate the contents of a tag, even without a copy of the registry. The following table shows a number of examples of the new tags:. A critical point of debate during the development of the new language tags was the positioning of the script subtag after the language subtag but before the region subtag. Nothing in RFC or RFC guaranteed that the region subtag would appear in the second position and, prior to , when this effort started, no registered tags existed that would clarify whether it was valid to assume that the region code, if it existed, would always appear second it was quite clear that other values, such as script, could appear second.
Some people felt that putting scripts into the second position presented some problems.
0コメント