by Michael S. Kaplan, published on 2011/09/29 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2011/09/29/10218142.aspx
We have been trying to use Welsh and found that the NLS table (http://msdn.microsoft.com/en-gb/goglobal/bb896001.aspx) maps Welsh to codepage 1252.
This has confused me because Welsh can contain Ux0174 (and others) that are not in 1252. (http://www.microsoft.com/globaldev/handson/user/welsh.mspx)
Is there going to be any changes to this mapping to create a Welsh codepage, or an equivalent of Celtic?
Unfortunately, we really are out of the code page creation business. It was never terribly lucrative.
And almost every language fails the test here now....
So Welsh has lots of distinguished company.
But use Unicode to support them all!
Must resist temptation to make a "Welsh/Welch pun"....
Doug Ewell on 29 Sep 2011 7:12 AM:
Didn't you write this blog two years ago?
Michael S. Kaplan on 29 Sep 2011 8:10 AM:
I did? Uh oh!
Did I change the answer?
John Cowan on 29 Sep 2011 11:02 AM:
In fact "welsh" and "welch" are interchangeable here: a "welsher" is someone (either the bookie or the customer) who fails to pay what they owe on a bet. In extended usage it can refer to any business transaction rather than just a bet. So you welshed on the codepage promise.
The exact origin of the verb is not known. Needless to say, the Welsh take it as just another slur perpetrated by the English: "Taffy was a Welshman / Taffy was a thief" and all that.
(The Royal Welch Fusiliers were until 2006 an infantry regiment of the British Army, so named because their ceremonial commander is the Prince of Wales. The archaic spelling dates back to the founding of the regiment in 1689, and has nothing to do with welshing/welching.)
Joshua on 3 Oct 2011 2:32 PM:
We managed to paint ourselves into a corner where we cannot convert to Unicode unless the SQL row limit can be exceeded.
go to newer or older post, or back to index or month or day