LCIDs are are really bad idea

Well, it’s been 4 years since I posted about the deprecation of LCIDs, though I started discussing the topic over a decade ago. It’s pretty much time to dump LCIDs. LCIDs were an OK idea when they were invented, though a couple quirks quickly broke their pattern.  However on a modern Windows 10 machine they’re…

0

Locale Data in Windows 10 & CLDR

I’ve blogged about Locale Data Churn a couple times in the past, and mentioned how to use the Locale Builder to modify Finnish for Windows 10, but I’d like to talk a bit more about Locale Data in Windows 10. A Data Collection Problem As I’ve mentioned before, Locale Data changes over time for various reasons. …

0

Locale (Culture) Data Churn

Data Churn Some of you have noticed churn in the Locale Data (which ends up as Culture data in .Net).  I’ve mentioned before that this stuff shouldn’t be considered stable, but in Windows 10 we have a little more churn than normal. What happens is that, over time, locale data preferences change around the world. …

0

Locale Builder and Finnish or other locales…

The Locale Builder tool, https://aka.ms/localebuilder, runs on Windows 10 and can be used to modify your computer’s locale if you don’t want the defaults that ship in the OS.  For example, the Finnish locale was updated to use . for the time separator, however that is currently causing some confusion because it is identical to…

2

Locale Builder v2.0 for Windows 8.1/Server 2012 R2 Released!

There’s a new Locale Builder for creating your own custom locales live on the Download Center at http://www.microsoft.com/en-us/download/details.aspx?id=41158.  The direct link to the setup exe is http://download.microsoft.com/download/C/6/8/C68BDDC5-50CB-47E1-9EF7-B5651D68BDDF/LocaleBuilderSetup.exe  Locale Builder 2.0 is designed primarily for Windows 8.1/Server 2012 R2, including a few new data fields for those locales.  The constructed locales might work OK on previous versions, or…

8

LCIDs vs Locale Names and the deprecation of LCIDs.

As Windows XP nears the end of its extended support (see lifecycle fact sheet), I thought I’d mention Locale Names again.  I’ve been asking for years for people to use locale names, but now we’re reaching a step closer to deprecating LCIDs. In the modern and managed worlds we’ve been using Locale Names/Culture Names/Language Names for some…

8

pIqaD Font for Bing’s Klingon Translator

[Halloween, 2013, updated link, Bing fixed the script code for pIqaD] People have asked me where to get a pIqaD font to use with Bing’s Klingon Translator http://www.bing.com/translator/?from=en&to=tlh-Qaak&text=Hello%20Earth,%20I%20made%20the%20font That’s actually a font I made.  (I’m not a font designer, so it has some rough spots, but it seems to work for most purposes). The pIqaD…

3

Bing Translator, Klingon High Council, and Klingon Language Institute announce support for Klingon as a Bing Translator Option!

The Bing Translator folks have announced support for Klingon as a translator option.   This was also proclaimed by the Klingon High Council. I’ve blogged about making a Windows Klingon Custom Locale and Klingon font fallback for the Windows 8 lock screen, and now you can translate all those Klingon web pages too! You’ll never guess who gave them the font 😉 -Shawn  

2

Klingon Win8 Lock Screen: Might Sell Qurgh on Win8 After All :)

A while ago I blogged about Klingon in pIqaD in a Custom Locale – that worked OK in Vista & Win7 using Uniscribe font fallback, but Win8 uses DWrite in a lot of places, and DWrite really would prefer EUDC (End User Defined Character) fallback.  So my pIqaD didnʻt work so hot on Win8 🙁  Fortunately…

7