Kannada and Brahmi jihvamuliya and upadhmaniya don't work correctly #7
Comments
|
|
|
In the upcoming version of Noto Brahmi, the following ligatures will be provided: Jihvamuliya (11003) + Ka (11013)
|
|
What about the conjuncts with aspirated consonants (𑀃𑀔 and 𑀄𑀨)? |
|
In Sanskrit the following ligatures can also occur |
|
@dscorbett |
|
The aspirated conjuncts look just like the unaspirated conjuncts, but with aspirated consonant glyphs instead of unaspirated consonant glyphs. L2/13-242 has examples in Kannada. |
|
The Noto Sans Kannada now support this: at least for Harfbuzz and the Apple shaper. The Microsoft shaper seems to ignore 0CF1 and 0CF2 for shaping Be aware that when it come to having a vowel, harfbuzz puts the vowel in front of the subscript, Apple after (the above image is Safari). |
|
Can we please give get alpha/beta version of the font? |
|
I am testing this in mac OS and Pages with the previously posted test build in a different thread. Noto Sans Kannada works for only the example shown in Unicode document. But it doesn't work for other consonants and diacritics. Also, the diacritic should be smaller in size.
|
|
This works for 4 specific combinations. ẖka, ẖkh, ḫpa, ḫpha. As sridatta1 mentioned there are a few combinations with an second consonant. That works too. This is a image from Chrome, showing the vowels being re-ordered, which I thinks looks better.
|
|
The glyphs for upadhmaniya+pa/pha need to be corrected. They don't have
subscript forms. See www.unicode.org/L2/L2013/13242-kannada-rep.pdf and
upadhmaniya is of smaller size.
…On Wed 13 Jun, 2018 9:26 am Jelle Bosma, ***@***.***> wrote:
This works for 4 specific combinations. ẖka, ẖkh, ḫpa, ḫpha. As sridatta1
mentioned there are a few combinations with an second consonant. That works
too. This is a image from Chrome, showing the vowels being re-ordered,
which I thinks looks better.
[image: image]
<https://user-images.githubusercontent.com/12729011/41329490-56439946-6ece-11e8-9ca1-9da250b280aa.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/googlei18n/noto-fonts/issues/459#issuecomment-396805726>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWL568jDoNTJ3n97UhZVbVXm-024hP-0ks5t8I1bgaJpZM4FlvyW>
.
|
|
Of the samples given in www.unicode.org/L2/L2013/13242-kannada-rep.pdf, figure 6 shows the most attractive (and most modern) typeface, so that is the interpretation I used. |
|
It was due to lack of proper glyphs in the typeface(as the character is not
required for Kannada language) and also the had glyph similar to x for
jinvamuliya again due to he same reason. The book ha used ೦೦ two zeroes and
pa-ottu. The glyphs in the images in the rest of the books should be used.
…On Wed 13 Jun, 2018 11:58 am Jelle Bosma, ***@***.***> wrote:
Of the samples given in www.unicode.org/L2/L2013/13242-kannada-rep.pdf,
figure 6 shows the most attractive (and most modern) typeface, so that is
the interpretation I used.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/googlei18n/noto-fonts/issues/459#issuecomment-396828129>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWL5609V2c4XvHmQh7vhXTi5DkP2dIwKks5t8LD9gaJpZM4FlvyW>
.
|
|
I am sorry to hear I haven't got it right. In September I made a design proposal, which Google had reviewed. So I thought it to be OK. But I am releasing the fonts today anyway, because in the big picture this doesn't seem a showstopper. I probably get feedback to fix one or another thing, and then add a ligature, tweak render rules. And this project covers Unicode 9.0. Once this project is done, we have to update with a new character and what looks like three new Vedic script extension characters that Unicode added in the mean time. |
|
additional comment from "Got this to work for Apple and Google shapers. I implemented this as in the approved design proposal. But I may have used the wrong example according to the bug reporters. In the context of the work this is not a showstopper. I can deal with this once we have feedback with more issues, or the Unicode 10-11 updates." Will be dealt with in the future release |
moved from https://github.com/googlei18n/noto-alpha/issues/279
Imported from Google Code issue notofonts/noto-fonts#279 created by [email protected] on 2015-02-19T18:45:32.000Z:
According to Unicode, the Kannada and Brahmi jihvamuliya and upadhmaniya should form ligatures with the following consonant without using any virama, but they don't do that in Noto Kannada and Noto Brahmi.
For Kannada reference, see page 485-486 of http://www.unicode.org/versions/Unicode7.0.0/ch12.pdf
For Brahmi reference, see page 539 of http://www.unicode.org/versions/Unicode7.0.0/ch14.pdf
Attaching the rendering of the three sequences <0CF1, 0C95>, <0CF2, 0CAB>, and <0CF1, 0C95. 0CBF> in Noto Sans Kannada. Compare with images in first reference above.
I haven't tested with Uniscribe yet, but I believe it has the same behavior as HarfBuzz.
@behdad
= = = = = = = = = = = = = = = = =
behdad commented on Jun 30
Comment notofonts/khmer#10 originally posted by [email protected] on 2015-02-19T20:04:10.000Z:
With regard to Kannada:
In theory the shaper software could be enabled to create the subscript consonant after 0CF1, without any change to the existing fonts. It would have to pretend there is a virama in between and apply the blwf feature. Failing that, we could have a contextual lookup added to one of the presentation features to do the work, because there is no feature defined for creating the below base forms without a virama in the sequence.
Support for displaying 0CF2 as a mark over a crestless consonant is something that would be added to the fonts. Not sure if the information given by Unicode is sufficient to know how that is supposed to work with other consonants and what these consonants are and how to handle the presence of other marks.
I see this as a new feature request, not as a bug.
The text was updated successfully, but these errors were encountered: