To be clear, the Opentype application II profile at least (initially
defined for Arabic) may also be needed in Latin for correctly rendering
cursive Latin styles.
For now this Application profile II (
https://docs.microsoft.com/fr-fr/typography/script-development/use#featureapplicationii)
has not
2018-02-18 20:38 GMT+01:00 Richard Wordingham via Unicode <
unicode@unicode.org>:
> On Sun, 18 Feb 2018 14:13:22 +0100
> Philippe Verdy via Unicode wrote:
>
> > But any operation in OpenType that requires reordering requires a
> > glyphs buffer. This could even apply to Latin if Microsoft really
On Sun, 18 Feb 2018 14:13:22 +0100
Philippe Verdy via Unicode wrote:
> But any operation in OpenType that requires reordering requires a
> glyphs buffer. This could even apply to Latin if Microsoft really
> intends to support normalization (i.e. canonical equivalences) in its
> own USE engine (fo
20But any operation in OpenType that requires reordering requires a glyphs
buffer. This could even apply to Latin if Microsoft really intends to
support normalization (i.e. canonical equivalences) in its own USE engine
(for now it does not) because it would also require a glyphs buffer to
allow cor
Now what I suspect in Apple's implementation is the following:
the OpenType specification details the steps to parse strings, find
clusters boundaries, identify the various character types (joining,
associativity, decomposable characters...)
At first Apple parses the clusters and marks those that
Yes, I found other possible crashes all caused by the glyph reordering. It
seems really that Apple implemented some unsafe shortcuts by not creating a
glyphs buffer in all cases (using lasy instanciation only when needed), but
forgot some cases and the code assumes that the glyphs buffer has been
i
Doug Ewell wrote,
> I've linked Manish's post on FB as a reply to one of those mainstream
> articles that repeatedly calls the conjunct a "single character," written by
> a staffer who couldn't be bothered to find out how a writing system used by
> 78 million people works.
Linking Manish's inform
Oh, also vatu.
Seems like that ordering algorithm is indeed relevant.
-Manish
On Sat, Feb 17, 2018 at 11:57 PM, Manish Goregaokar
wrote:
> Ah, looking at that the OpenType `pstf` feature seems relevant, though I
> cannot get it to crash with Gurmukhi (where the consonant ya is a postform)
>
>
Ah, looking at that the OpenType `pstf` feature seems relevant, though I
cannot get it to crash with Gurmukhi (where the consonant ya is a postform)
-Manish
On Sat, Feb 17, 2018 at 4:40 PM, Philippe Verdy wrote:
> An interesting read:
>
> https://docs.microsoft.com/fr-fr/typography/script-
> de
An interesting read:
https://docs.microsoft.com/fr-fr/typography/script-development/bengali#reor
2018-02-18 1:30 GMT+01:00 Philippe Verdy :
> My opinion about this bug is that Apple's text renderer dynamically
> allocates a glyphs buffer only when needed (lazily), but a test is missing
> for th
My opinion about this bug is that Apple's text renderer dynamically
allocates a glyphs buffer only when needed (lazily), but a test is missing
for the lazy construction of this buffer (which is not needed for most
texts not needing glyph substitutions or reordering when a single accessor
from the c
On 17/02/18 21:01, Doug Ewell via Unicode wrote:
[…]
>
> I've linked Manish's post on FB as a reply to one of those mainstream
> articles that repeatedly calls the conjunct a "single character,"
> written by a staffer who couldn't be bothered to find out how a writing
> system used by 78 millio
Heh, I wasn't aware of the word "phala-form", though that seems
Bengali-specific?
Interesting observation about the vowel glyphs, I'll mention this in the
post. Initially I missed this because I hadn't realized that the bengali o
vowel crashed (which made me discount this).
Thanks!
-Manish
On
I would have liked that your invented term of "left-joining consonants"
took the usual name "phala forms" (to represent RA or JA/JO after a virama,
generally named "raphala" or "japhala/jophala").
And why this bug does not occur with some vowels is because these are
vowels in two parts, that are f
Manish Goregaokar wrote:
FWIW I dissected the crashing strings, it's basically all sequences in Telugu, Bengali,
Devanagari where the consonant is suffix-joining (ra in Devanagari,
jo and ro in Bengali, and all Telugu consonants), the vowel is not
Bengali au or o / Telugu ai, and if the second
FWIW I dissected the crashing strings, it's basically all sequences in Telugu, Bengali, Devanagari
where the consonant is suffix-joining (ra in Devanagari, jo and ro in
Bengali, and all Telugu consonants), the vowel is not Bengali au or o /
Telugu ai, and if the second consonant is ra/ro the first
That's probably not a bug of Unicode but of MacOS/iOS text renderers with
some fonts using advanced composition feature.
Similar bugs could as well the new advanced features added in Windows or
Android to support multicolored emojis, variable fonts, contextual glyph
transforms, style variants, or
This article:
https://techcrunch.com/2018/02/15/iphone-text-bomb-ios-mac-crash-apple/?ncid=mobilenavtrend
The single Unicode symbol referred to in the article results from a
string of Telugu characters. The article doesn't list or display the
characters, so Mac users can visit the above link. A
18 matches
Mail list logo
