rizwan3d / noto

Automatically exported from code.google.com/p/noto
1 stars 0 forks source link

Unicode 0A70 should be replace by unicode 0A02 when a consonant is folled by dependent vowel #188

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Write any punjabi consonant without matra 
2. Write the unicode 0A3E (AAA) follwoed by unicode 0A70
3. Observe the result

What is the expected output? What do you see instead?
whenever any character is entered with symbol "AAA ki matra"[UNICODE 0A3E] then 
UNICODE[0A70] should not be taken although we tap on this symbol.
                                       it should be taken UNICODE[0A02] 

What version of the product are you using? On what operating system?
NotoSansGurmukhi-Regular.ttf. Version 1.01 August 15 2014
Operating system: Android L version

Please provide any additional information below.
Unicode standard section 9.3
Present practice is to use bindi (0A02) only with the dependent and independent 
forms of the vowels aa, ii, ee, ai, oo, and au, and with the independent vowels 
u and uu; tippi (0A70) is used in the other contexts.
This statement is working for all the vowels except aa. 
Please check

Original issue reported on code.google.com by idiotmad...@gmail.com on 30 Oct 2014 at 10:48

GoogleCodeExporter commented 9 years ago

Original comment by roozbeh@google.com on 31 Oct 2014 at 5:38

GoogleCodeExporter commented 9 years ago
I believe this is not a font problem, but a spelling problem. If you want the 
bindi, use the character U+0A02 instead of U+0A70. If somebody wants the tippi 
(say, for historical spellings that used the tippi with aa), they should be 
able to use it.

What Noto is doing in rendering sequences such as <ka, aa, tippi> is also 
consistent with how Windows fonts render them.

Original comment by roozbeh@google.com on 2 Apr 2015 at 3:50