-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Malayalam needs to support the Unicode 8.0 Virama and joiner sequences #7
Comments
No HarfBuzz changes should be needed. Jelle, let me know if you need anything. |
[well, we need to update the indic shaper's data table for Unicode 8. |
@behdad, this shouldn't need any update to the shaping tables. There's no new characters, just new sequences that used to have undefined behavior before, but is now specified to form certain forms of conjuncts. |
@roozbehp Ok I thought there's a new virama character involved... |
The existing fonts already support ligatures with U-200D + virama. That is On 09-aug.-15 14:23, "Behdad Esfahbod" notifications@github.com wrote:
|
Supporting the spec for optional ligatures can be lot of work for reformed orthography fonts like Noto Malayalam Sans; as many additional glyphs available in an traditional orthography script needs to be supported. For example, KA + ZWJ + VIRAMA + RA should return a connected ligature. So question would be how much more are we willing to draw. Depending on the answer we can come up with a subset of relevant traditional ligatures. |
Unicode 8.0 adds a mechanism for selecting various forms of Malayalam conjuncts. The actual Core Specification is still pending publication (it will be available in a few weeks), but until then, the best documentation available is at http://www.unicode.org/review/pri263/pri263-malayalam.pdf.
Assigning to @cibu to provide a complete list of needed conjuncts and the sequences that are supposed to generate them, so they could be added to the fonts.
CC-ing @behdad and @JelleBosmaMT in case any changes may be required to HarfBuzz.
The text was updated successfully, but these errors were encountered: