2018-02-01 2:38 GMT+01:00 Richard Wordingham via Unicode <
unicode@unicode.org>:
> On Wed, 31 Jan 2018 19:45:56 +0100
> Philippe Verdy via Unicode wrote:
>
> > 2018-01-29 21:53 GMT+01:00 Richard Wordingham via Unicode <
> > unicode@unicode.org>:
>
> > > On Mon, 29 Jan 2018
On Wed, 31 Jan 2018 19:45:56 +0100
Philippe Verdy via Unicode wrote:
> 2018-01-29 21:53 GMT+01:00 Richard Wordingham via Unicode <
> unicode@unicode.org>:
> > On Mon, 29 Jan 2018 14:15:04 +0100
> > was meant to be an example of a
> > searched string. For example, >
Greetings and Happy New Year,
The discussion of CLDR Keyboards and layout is getting lengthy and
it should probably be moved to the CLDR-Users mail list where it is
more appropriate. Especially because it is so technically detailed.
Please see this page for instructions about how to subscribe:
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
2018-01-29 21:53 GMT+01:00 Richard Wordingham via Unicode <
unicode@unicode.org>:
> On Mon, 29 Jan 2018 14:15:04 +0100
> > The case of u with diaeresis and macron is simpler: it has two
> > combining characters of the same combining class and they don't
> > commute, still the regexp to match it
> On Jan 31, 2018, at 12:51 PM, Tom Gewecke via Unicode
> wrote:
>
> There may be something here:
>
> https://chinese.stackexchange.com/questions/24210/how-to-display-cjk-extension-f
That post claims "Hanazono hasn't been updated in a while and only supports up
to
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 Jan 31, 2018, at 10:25 AM, John H. Jenkins via Unicode
> wrote:
>
> I'm not aware of any publically available fonts for Extension F but would
> gladly install one myself if it's available.
>
There may be something here:
macOS (and iOS, for that matter) fully support Extension F provided fonts are
availble. I'm not aware of any work that Apple has done to its fonts for
Extension F support. Indeed, I'm not aware of any publically available fonts
for Extension F but would gladly install one myself if it's
11 matches
Mail list logo