Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara
On Sat, 4 Jan 2020 22:15:59 + James Kass via Unicode wrote: > For the Grantha examples above, Grantha (1) displays much better > here. It seems daft to put a spacing character between a base > character and any mark which is supposed to combine with the base > character. Although it's not related to this issue, that happens in the USE scheme. It puts vowels before vowel modifiers, which has this problem if any of the vowel modifiers precede a vowel in visual order, as happens in Thai and closely related writing systems. Richard.
Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara
On 2020-01-04 12:50 PM, Richard Wordingham via Unicode wrote: dev2: कः꣡ dev3: क꣡ः Grantha: (1) 𑌕𑍧𑌃 (2) 𑌕𑌃𑍧 The second Grantha spelling is enabled by a Harfbuzz-only change to the USE categorisations. It treats Grantha visarga and spacing anusvara as though inpc=Top rather than inpc=Right. As I am using Ubuntu 16.04, this override isn't supported in applications that use the system HarfBuzz library, such as my email client. We are now establishing incompatible Devanagari font-specific encodings fully compliant with TUS! This seems to be a very bad approach. And apparently it isn't limited to the Devanagari script. For the Grantha examples above, Grantha (1) displays much better here. It seems daft to put a spacing character between a base character and any mark which is supposed to combine with the base character.
Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara
On Thu, 2 Jan 2020 20:20:34 + Richard Wordingham via Unicode wrote: > There's a project whose basis I can't find to convert Indian Indic > rendering at least to use the USE. Now, according to the > specification of the USE, visarga, anusvara and cantillation marks > are all classified as vowel modifiers, and are so ordered relative to > one another in the Indian Indic order: left, top, bottom, right. So, > the problem should already be solved for Grantha, and, if the plans > come to fruition, will work with a font whose Devanagari script tag > is 'dev3'. However, I may have overlooked a set of overrides to the > USE categorisations. I've now knocked up a partial* representation* of a Devanagari dev3 and a Grantha font (which I'm dubbing 'Mock Indic 3'). The supported orders of COMBINING DIGIT ONE and VISARGA, as in Firefox on Linux, are: dev2: कः꣡ dev3: क꣡ः Grantha: (1) 𑌕𑍧𑌃 (2) 𑌕𑌃𑍧 The second Grantha spelling is enabled by a Harfbuzz-only change to the USE categorisations. It treats Grantha visarga and spacing anusvara as though inpc=Top rather than inpc=Right. As I am using Ubuntu 16.04, this override isn't supported in applications that use the system HarfBuzz library, such as my email client. We are now establishing incompatible Devanagari font-specific encodings fully compliant with TUS! Richard. * Partial = much is not handled * Representation = glyphs are wrong, merely showing arrangement. (I've actually re-used a Tai Tham font.)
