On Mon, 15 Jul 2013 18:19:34 +1000 Andrew Cunningham <[email protected]> wrote:
> On 15/07/2013 6:02 PM, "Christopher Fynn" <[email protected]> > wrote: > > MS Office seems to want to do is apply fonts based on the language > > being used - the input "language" being determined by the keyboard > > or IME currently selected. When using a custom keyboard (e.g. one > > created with MSKLC) or IME MS Office frequently does not accuratly > > determine the language and consequently overides your font > > selection. > I am wondering if building a MSKLC against a custom locale will get > around the problem, or would make no difference? Can one actually build MSKLC against a custom locale? The documentation on the easiest way of building a custom locale implies that it is only available for Windows Vista, whereas I only have XP and Windows 7. The .klc files MSKLC created use a numerical locale ID (LCID); I don't see any way to check what the general .klc file format is - the format seemed very delicate when I had to edit it by hand, at least, not for the SMP. Neither Akkadian nor Hittite comes up on the pick list. (I might choose Hittite because the cuneiform font I have is for Hittite.) I suppose I might have problems with cuneiform because I chose the only Mesopotamian locale available - Iraqi Arabic. Richard.
