Creating a Custom Culture (Locale) From Microsoft-ish LDML

[Updated 11 Aug 2006 to reflect IETF style locale names] This is just a simple example of creating a custom culture from an LDML file.  The LDML file has to have Microsoft specific tags otherwise you will get some errors for the missing data.  The resulting custom culture/locale works in .Net Framework 2.0 (new CultureInfo(“tlh-Latn-US”))…

5

Klingon Custom Culture/Locale MS LDML File

This is intended to go with the custom culture LDML example.  Cut & paste this into a file called “tlh-Latn-US.ldml”.  Notepad should work. <?xml version=”1.0″ encoding=”utf-8″?><ldml>  <identity>    <version number=”1.1″>ldml version 1.1</version>    <generation date=”2005-11-23″ />    <special xmlns:msLocale=”http://schemas.microsoft.com/globalization/2004/08/carib/ldml“>      <msLocale:cultureInfoVersion type=”1.0″ />      <msLocale:cultureAndRegionInfoName type=”tlh-Latn-US” />      <msLocale:geoId>244</msLocale:geoId>      <msLocale:parentName type=”en-US” />      <msLocale:languageNameAbbr type=”TLH” />      <msLocale:languageIsoName type=”threeLetters”>tlh</msLocale:languageIsoName>      <msLocale:languageIsoName type=”twoLetters”>tlh</msLocale:languageIsoName>      <msLocale:nativeName type=”tlhIngan…

2