<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Some keyboarding terms</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx</link><description>This posting will try to clear up some of the problems in documentation and info regading keyboards, since there is plenty left in those things to be confusing and there is no need to throw bewildering terms into the mix. Future posts will build on this</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Larkware</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#279727</link><pubDate>Fri, 10 Dec 2004 22:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:279727</guid><dc:creator>TrackBack</dc:creator><description>They get up early so we don't have to. :-)</description></item><item><title>re: Some keyboarding terms</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#329430</link><pubDate>Wed, 22 Dec 2004 02:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:329430</guid><dc:creator>Norman Diamond</dc:creator><description>If Layout ID and KLID are two separate identifiers, how come Windows still suffers from the forcing a single value to misrepresent both the keyboard layout and IME together?  This is the root cause of some of the problems I've mentioned in feedback to some of your later postings.  The physical keyboard has a physical layout of what is shown on its keys, and the IME is a separate layer on top of that.  Why can't users (of either a real IME or &amp;quot;Global&amp;quot; IME) independently say what their real keyboard layout is and say what IME they wish to use on top of it?</description></item><item><title>re: Some keyboarding terms</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#329602</link><pubDate>Wed, 22 Dec 2004 06:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:329602</guid><dc:creator>Michael Kaplan</dc:creator><description>Your issue has nothing to do these two things being separate. I'll work at trying to help with the other issues you bring up in a different post though as this one is unrelated.</description></item><item><title>re: Some keyboarding terms</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#329627</link><pubDate>Wed, 22 Dec 2004 07:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:329627</guid><dc:creator>Norman Diamond</dc:creator><description>Well, I used to think that Microsoft had one single identifier into which they forced the combination of real keyboard layout and IME, resulting in the described problems.  I used to think that those problems could be avoided by using two separate identifiers.  Then in your posting I learned that there ARE two separate identifiers.  So why didn't one identifier get one of these meanings and the other identifier get the other meaning?  Why did both of them still get the combination of the same two meanings squashed together?&lt;br&gt;&lt;br&gt;I understand that you will bring this up in another post, I thank you and I look forward to it.  But meanwhile it still looks to me like my question was on-topic.</description></item><item><title>re: Some keyboarding terms</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#329643</link><pubDate>Wed, 22 Dec 2004 07:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:329643</guid><dc:creator>Michael Kaplan</dc:creator><description>They are different meanings, and the meaning relate to important tracking issues within the USER subsystem and the architecture of keyboards.&lt;br&gt;&lt;br&gt;Your interest in adding yet a third meaning is a separate issue. So the reason that that meaning was not captured here is that they were busy with the other stuff? :-)</description></item><item><title>The ever-misleadingly incorrect usage of the word DEFAULT</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#406414</link><pubDate>Fri, 08 Apr 2005 07:21:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:406414</guid><dc:creator>Sorting It All Out</dc:creator><description>Back after Windows 2000 shipped, everyone though the word LOCALE was simply used too much, in fact that...</description></item><item><title>Why are the HKL and KLID of the keyboard different?</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#409033</link><pubDate>Mon, 18 Apr 2005 00:58:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:409033</guid><dc:creator>Sorting It All Out</dc:creator><description>I actually get this question on a regular basis, believe it or not.&lt;br&gt;People look at the two numbers,...</description></item><item><title>internationalizaton vs. localizability</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#462864</link><pubDate>Fri, 09 Sep 2005 15:14:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:462864</guid><dc:creator>Sorting It All Out</dc:creator><description>Yesterday, in response to my post Its not localization, really, regular reader CornedBee commented:...</description></item><item><title>I do not think that word means what the Platform SDK thinks it means</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#1618844</link><pubDate>Wed, 07 Feb 2007 14:37:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1618844</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;Looking back at some of the comments to this post , particularly this one and this one , I am actually&lt;/p&gt;
</description></item><item><title>Getting the language (and more!) of an LCID-less keyboard</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#4535060</link><pubDate>Fri, 24 Aug 2007 05:10:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4535060</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;So back in May when I was talking about Getting the language of an LCID-less keyboard , I promised to&lt;/p&gt;
</description></item><item><title>The UK Extended keyboard -- over-extended? Or weirdly extended?</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#6600201</link><pubDate>Thu, 29 Nov 2007 19:29:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6600201</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;I have a regular reader who is kind of fond of the blog. She admits to skimming it regularly, kind of&lt;/p&gt;</description></item><item><title>What a tangled web we weave when a KLID from an HKL we must receive</title><link>http://blogs.msdn.com/michkap/archive/2004/11/27/270931.aspx#8968532</link><pubDate>Mon, 29 Sep 2008 10:03:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8968532</guid><dc:creator>Sorting it all Out</dc:creator><description>&lt;p&gt;For the title to work best, you have to use the pronunciations from Some keyboarding terms for the terms...&lt;/p&gt;
</description></item></channel></rss>