The spell checker I was invoking was to allow fixing basic the typography
(e.g. the ae and oe ligatures contextually, it does not have to be a full
spell checker, but only concentrate on the typography, not the orthography,
most transforms should be limited to one or two characters, so that it is
On Wed, 31 Jan 2018 19:05:17 +0100, Philippe Verdy wrote:
>
> Another idea: you can already have multiple layouts loaded for the same
> language : For French, nothing prohibits to have a "technical/programmer
> layout", favoring input of ASCII, a "bibliographic/typographical" one with
> improved
>
> 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
Another idea: you can already have multiple layouts loaded for the same
language : For French, nothing prohibits to have a "technical/programmer
layout", favoring input of ASCII, a "bibliographic/typographical" one with
improved characters (e.g. the correct curly apostrophe); the
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
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 Tue, 30 Jan 2018 08:18:49 +0100, Philippe Verdy wrote:
>
> 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:
Many people in Fɽanƈë are wondering, but it is primarily a matter of honoring
a
On Tue, 30 Jan 2018 11:50:49 -0700, Doug Ewell wrote:
>
> Marcel Schneider wrote:
> >
> > http://recycledknowledge.blogspot.com/2013/09/us-moby-latin-keyboard-for-windows.html
> >
> >
> > Sadly the downloads are still unavailable (as formerly discussed). But
> > I saved in time, too (June
On Tue, 30 Jan 2018 11:34:40 -0700, Doug Ewell via Unicode wrote:
>
> Marcel Schneider wrote:
>
> > That tends to prove that Mac users accept changes, while Windows users
> > refuse changes.
>
> I was going to say that was a gross over-generalization, but that didn't
> adequately express how
On Tue, 30 Jan 2018 10:20:46 +, Alastair Houghton wrote:
>
> On 30 Jan 2018, at 05:31, Marcel Schneider via Unicode wrote:
> >
> > OnMon, 29 Jan 2018 11:13:21 -0700, Tom Gewecke wrote:
> >>
[…]
> >>
> >> They are also all on the MacOS "US International PC", provided since 2009
> >> by
Marcel Schneider wrote:
>> http://recycledknowledge.blogspot.com/2013/09/us-moby-latin-keyboard-for-windows.html
>
> Sadly the downloads are still unavailable (as formerly discussed). But
> I saved in time, too (June 2015).
Sorry, try this:
http://vrici.lojban.org/~cowan/MobyLatinKeyboard.zip
Marcel Schneider wrote:
> That tends to prove that Mac users accept changes, while Windows users
> refuse changes.
I was going to say that was a gross over-generalization, but that didn't
adequately express how gross it was. It's just plain wrong. Pardon my
bluntness.
How about: Windows is
On Tue, 30 Jan 2018 08:54:19 -0700, Tom Gewecke wrote:
>
> > 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
> 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 “⌥”.
Indeed.
But "Faÿ-lès-Nemours" / "FAŸ-LÈS-NEMOURS". "lès" in French place names
means "near", typically followed by another city name or a river name.
In the case of "L'Haÿ-les-Roses", it's just that they have a famous rose
garden, so "les".
Eric.
On 1/30/2018 12:06 AM, Martin J. Dürst via
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
On 2018/01/30 16:18, Philippe Verdy via Unicode wrote:
- Adding Y to the list of allowed letters after the dieresis deadkey to
produce "Ÿ" : the most frequent case is L'HAŸE-LÈS-ROSES, the official name
of a French municipality when written with full capitalisation, almost all
spell checkers
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
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
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”
(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
BTW the 5 dead keys of Windows US Intl are already on
Appleʼs *normal* US layout, along with the letter o-with-e.
US Extended adds 20 more deadkeys.
On Sun, 28 Jan 2018 16:20:16 -0700, Doug Ewell wrote:
[…]
> Nothing in the PRI #367 blog post or background document communicated to
> me that
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
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,
>>
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
>
On Sun, 28 Jan 2018 16:20:16 -0700, 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
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
30 matches
Mail list logo