>
> Note the French "touch" keyboard layout is complete for French (provided
> you select the one of the 3 new layouts with Emoji: it has the extra "key"
> for selecting the input language in all 4 layouts)
>
> But the "full" (dockable) touch layout in French which emulates a physical
> keyboard is
On Tue, 30 Jan 2018 23:30:59 +, David Starner via Unicode wrote:
>
> On Tue, Jan 30, 2018 at 2:23 AM Alastair Houghton via Unicode wrote:
>
> > This pattern exists across the board at the two companies; the Windows API
> > hasn’t changed all that much
> > since Windows NT 4/95, whereas Apple
On Tue, Jan 30, 2018 at 2:23 AM Alastair Houghton via Unicode <
unicode@unicode.org> wrote:
> This pattern exists across the board at the two companies; the Windows API
> hasn’t changed all that much since Windows NT 4/95, whereas Apple has
> basically thrown away all the work it did up to Mac OS
> On Jan 30, 2018, at 3:20 AM, Alastair Houghton
> wrote:
>
> The “alt” annotation isn’t on the latest keyboards (go look in an Apple
> Store if you don’t believe me :-)).
Interesting! Apple’s documentation shows these keys mostly with “alt” and “⌥”.
https://support.apple.com/en-us/HT2017
On 30 Jan 2018, at 05:31, Marcel Schneider via Unicode
wrote:
>
> OnMon, 29 Jan 2018 11:13:21 -0700, Tom Gewecke wrote:
>>
>>> On Jan 29, 2018, at 4:26 AM, Marcel Schneider via Unicode wrote:
>>>
>>>
>>> the Windows US-Intl
>>> does not allow to write French in a usable manner, as the Œœ is
I have always wondered why Microsoft did not push itself at least the five
simple additions needed since long in French for the French AZERTY LAYOUT:
- [AltGr]+[²] to produce the cedilla dead key (needed only before capital
C in French) : this is frequently needed, the alternative would be
[AltGr
OnMon, 29 Jan 2018 11:13:21 -0700, Tom Gewecke wrote:
>
> > On Jan 29, 2018, at 4:26 AM, Marcel Schneider via Unicode wrote:
> >
> >
> > the Windows US-Intl
> > does not allow to write French in a usable manner, as the Œœ is still
> > missing, and does not allow to type German correctly neith
On Mon, 29 Jan 2018 16:07:11 -0700, Doug Ewell wrote:
>
> Marcel Schneider wrote:
>
> > Prior to this thread, I believed that the ratio of Windows users
> > liking the US-International vs Mac users liking the US-Extended was
> > like other “Windows implementation” vs “Apple implementation” ratios
(b) it doesn't ship with Windows
Of course that is not a "luxury." Knowing that third-party options are
available, let alone free and easily installed ones, is the luxury.
--
Doug Ewell | Thornton, CO, US | ewellic.org
Marcel Schneider wrote:
> Prior to this thread, I believed that the ratio of Windows users
> liking the US-International vs Mac users liking the US-Extended was
> like other “Windows implementation” vs “Apple implementation” ratios.
For many users, it may not be a question of what they like, but
> On Jan 29, 2018, at 4:26 AM, Marcel Schneider via Unicode
> wrote:
>
>
> the Windows US-Intl
> does not allow to write French in a usable manner, as the Œœ is still
> missing, and does not allow to type German correctly neither due to
> the lack of single angle quotation marks (used in s
On Sun, 28 Jan 2018 21:56:25 -0800, Mark Davis replied to Doug Ewell:
>
> It is not a goal to get "vendors to retire these keyboard layouts and
> replace them" — that's not our role. (And I'm sure that a lot of people
> like and would continue to use the Windows Intl keyboard.)
Instead of “replac
On Sun, Jan 28, 2018 at 3:20 PM, Doug Ewell wrote:
> Mark Davis wrote:
>
> One addition: with the expansion of keyboards in
>> http://blog.unicode.org/2018/01/unicode-ldml-keyboard-enhancements.html
>> we are looking to expand the repository to not merely represent those,
>> but to also serve as
On Sun, 28 Jan 2018 14:11:06 -0700, Doug Ewell wrote:
>
> Marcel Schneider wrote:
>
> > We can only hope that now, CLDR is thoroughly re-engineering the way
> > international or otherwise extended keyboards are mapped.
>
> I suspect you already know this and just misspoke, but CLDR doesn't
> pre
Mark Davis wrote:
One addition: with the expansion of keyboards in
http://blog.unicode.org/2018/01/unicode-ldml-keyboard-enhancements.html
we are looking to expand the repository to not merely represent those,
but to also serve as a resource that vendors can draw on.
Would you say, then, that
One addition: with the expansion of keyboards in
http://blog.unicode.org/2018/01/unicode-ldml-keyboard-enhancements.html we
are looking to expand the repository to not merely represent those, but to
also serve as a resource that vendors can draw on.
Mark
On Sun, Jan 28, 2018 at 1:11 PM, Doug Ewel
Marcel Schneider wrote:
We can only hope that now, CLDR is thoroughly re-engineering the way
international or otherwise extended keyboards are mapped.
I suspect you already know this and just misspoke, but CLDR doesn't
prescribe any vendor's keyboard layouts. CLDR mappings reflect what
vendo
17 matches
Mail list logo
