Description of problem: a) it does not implement 'pstf' to create a post-base form of Ya when entering Virama + Ya. See TUS 4.0, ch9, p235. b)two simple additions of Adak Bindi and Visarg at U+0A01 and U+0A03 would enable Unicode 4.0 support for the font. c) u0A07 + u0A70, where there is no such combination is there in Punjabi. d) Chaining Substitution by coverage -Rule 0 Back coverage -1: u0A07 Coverage 0: u0A70 -Apply at 0 'L005' u0A70 => glyph147 e) These variable put worng constrains on Punjabi combination. -'vatu' Vattu Variants u0A15_u0A30_u0A4D.blwf.vatu <= u0A15 u0A30_u0A4D.blwf u0A21_u0A30_u0A4D.blwf.vatu <= u0A21 u0A30_u0A4D.blwf u0A24_u0A30_u0A4D.blwf.vatu <= u0A24 u0A30_u0A4D.blwf u0A26_u0A30_u0A4D.blwf.vatu <= u0A26 u0A30_u0A4D.blwf u0A2D_u0A30_u0A4D.blwf.vatu <= u0A2D u0A30_u0A4D.blwf f) One other rule in same area make incorrect combination. Rule 0 Back coverage -1: u0A3F Coverage 0: u0A70 -Apply at 0 'L005' u0A70 => glyph147 Version-Release number of selected component (if applicable): ttfonts-pa-1.8-1 How reproducible: Everytime Steps to Reproduce: 1. Enter Cons + Virama + Ya 2. 3. Actual results: a) full form of Ya with a Halant (Virama). c) incorrect combination Expected results: a)Post-base form of Ya c)Character should render as such Additional info:
Created attachment 112164 [details] Lohist fonts problem (c, d,e)
Created attachment 112165 [details] Output fontforge Output for Fontforge, showing incorrect combination in fonts
Is there any plan to update fonts???
Does anyone know who is in charge of the Lohit Punjabi font? It is unusable in its current state for Punjabi and should either be fixed or removed completely. As far as I know, Red Hat contracted someone to make these Unicode fonts - I suggest they either get their money back or get the original contractors to fix it.
there is need to add following characters from Hindi Unicode 0964 DEVANAGARI DANDA = purna viram ⢠phrase separator 0965 DEVANAGARI DOUBLE DANDA = deergh viram these characters are used in Punjabi to show end of Line as Full stop (.) in English without this OpenOffice is not showing (Danda), but BLOCK instead.
Created attachment 114408 [details] font problem in OpenOffice font problem with OpenOffic
Devel ACK for U2.
There are seven issues reported in this bug. I will use this bug as a tracker and create seven individual bug report. Hope this will make our tracking effort easier. a) it does not implement 'pstf' to create a post-base form of Ya when entering Virama + Ya. - FAIL b)two simple additions of Adak Bindi and Visarg at U+0A01 and U+0A03 would enable Unicode 4.0 support for the font. - FAIL c) u0A07 + u0A70, where there is no such combination is there in Punjabi. - PASS d) Chaining Substitution by coverage - FAIL -Rule 0 Back coverage -1: u0A07 Coverage 0: u0A70 -Apply at 0 'L005' u0A70 => glyph147 e) These variable put worng constrains on Punjabi combination. - PASS -'vatu' Vattu Variants u0A15_u0A30_u0A4D.blwf.vatu <= u0A15 u0A30_u0A4D.blwf u0A21_u0A30_u0A4D.blwf.vatu <= u0A21 u0A30_u0A4D.blwf u0A24_u0A30_u0A4D.blwf.vatu <= u0A24 u0A30_u0A4D.blwf u0A26_u0A30_u0A4D.blwf.vatu <= u0A26 u0A30_u0A4D.blwf u0A2D_u0A30_u0A4D.blwf.vatu <= u0A2D u0A30_u0A4D.blwf f) One other rule in same area make incorrect combination. - FAIL Rule 0 Back coverage -1: u0A3F Coverage 0: u0A70 -Apply at 0 'L005' u0A70 => glyph147 g) adding the following from Hindi Undicode - FAIL 0964 DEVANAGARI DANDA = purna viram ⢠phrase separator 0965 DEVANAGARI DOUBLE DANDA = deergh viram these characters are used in Punjabi to show end of Line as Full stop (.) in English without this OpenOffice is not showing (Danda), but BLOCK instead.
The new bugs are as follows: a. Bug 167590 (relates to glyph 149) b. Bug 167591, c. Bug 167592, d.+ f. Bug 167594, (relates to glyph 147) e. Bug 167595, g. Bug 167599
Removing all deps as bugs created today will be closed automatically soon after this bug is closed by ERRATA.
Priority for bugs in comment #15 is as follows: c, e, g, d, f, a, b
Found another bug: U+0A5E (à©) and the corresponding 'nukt' feature is missing. This should take priority over all the above bugs.
@Comment #18: Sukhjinder, is it possible to submit another bug for this issue? We can then pass the problem up.
Added Bug 151630.
Created attachment 118544 [details] Gurmukhi Test Case This should be useful for you. More useful for rendering engines I suppose, but you still may find it helpful.
Ignore comment 21, the correct bug is bug 167692
Comment #22, Thank you for your Test Case. These are very valuable during testing. Could you please take a screenshot of your test case? It will be good for matching test result.
Created attachment 119263 [details] Test Case Solutions
Shows how a rendering engine in combination with a font *should* show Gurmukhi text. The last one is missed out because the ICU CVS build I've used is only allowing the OO + U combination (and not U + OO) for double vowel signs. Because the UTC hasn't decided anything yet in regards to preferred orders, it might be dangerous implementing a behaviour that allows one method over the other.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-636.html
The fix has dramatically improved the situation in my limited testing. However, it still does not implement 'pstf' to create a post-base form of Ya when entering Virama + Ya. But, for some reason, it works fine on Linux and not at all on Windows.
I've also now noticed that the font doesn't include Danda or Double Danda which is also required for a Gurmukhi font ;) Shall I open new bugs for these problems? PS. Your font designer may use AnmolUni or Saab for references at http://guca.sourceforge.net/typography/fonts/ - they are both GPL fonts.