On Wed, 29 Jul 2015 10:10:02 +0200 (CEST) Marcel Schneider <[email protected]> wrote:
> On 02 Jul 2015, at 12:22, I replied: > > > However, I believe that WJs being a part of plain text, they should > > be properly supported on all text handling applications. And they > > should be on the keyboard. > > > The solution I suggest is therefore to have the word joiner (and > > the sequences containing it) on Ctrl+Alt or Kana, and the zero > > width no-break space on Shift+Ctrl+Alt or Shift+Kana, so that users > > working efficently on good software may access the preferred > > character a bit easier than users who must use the deprecated > > character because their word processor does not properly support > > the preferred one. > Unfortunately that doesnʼt work on at least one recent version of > Windows. An unambigous bug was due to the presence of 0x2060 in the > Ligatures table. This has cost me a whole workday to retrieve, fix, > and verify. > The effect of the bug was that Word, Excel, Firefox and Zotero were > unstartable. > As a result, the WORD JOINER cannot be implemented on a driver based > keyboard layout for general use on Windows. By contrast, the ZWNBSP > can. Your lament is a bit vague - I'm not sure what U+2060 is doing in a 'ligature table'. I can say that a Windows keyboard mapping that maps AltGr-M to WJ which was created using MSKLC on Windows 7 in April 2011 still works. Richard.
