Created attachment 433089 [details]
Description of problem:
0D4D (unicode) Character is cut if it present at End of Word in Label. It is
effecting Many applications in Desktop (Malayalam). It appears in Text Editor,
but in real-time, it is not appearing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run gedit in malayalam (ml_IN)
2. type 0D4D, check cursor position
3. run ibus-preferences, check 2nd tab Text
Character is cut at last on Tab
it should complete
1) in gedit, paste
Check "P" at 1st word, it is mixed with (്) Character
in 2nd row, position of cursor is in-between instead of End of Character
(In reply to comment #0)
> Created an attachment (id=433089) [details]
> Ibus Problem
> Description of problem:
> 0D4D (unicode) Character is cut if it present at End of Word in Label. It is
> effecting Many applications in Desktop (Malayalam). It appears in Text Editor,
> but in real-time, it is not appearing.
> Version-Release number of selected component (if applicable):
I assume this is a problem only with Meera font - is it reproducible with Rachana or any other font?
This might be the same issue of fontconf matrix...
(In reply to comment #1)
> I assume this is a problem only with Meera font - is it reproducible with
> Rachana or any other font?
> This might be the same issue of fontconf matrix...
this is happening due to Em- square issue of U+0D4D
see its right bearing is just 10, even though it required right bearing at 299
thats why next letter 'P' is merging with U+0D4D
why right bearing is kept so less?
I think it should be 299+ when U+0D4d will be last character.
same for U+0D02
I have tested this with Meera, Rachana and Lohit. For Meera, the cursor stands before 0D4D (്), Rachana in the middle and Lohit at the end. Screenshots attached
Created attachment 433323 [details]
Cursor position for 0D4D in Meera
Created attachment 433328 [details]
Cursor position for 0D4D in Rachana
Created attachment 433329 [details]
Cursor position for 0D4D in Lohit
Created attachment 433345 [details]
working sfd for Meera
was trying to investigate problem with pravi.a and naveen,
by adding dist feature we can resolve this problem, but need to check some exceptional condition as well
attaching .sfd with added dist feature in it, but not complete (and not working for all cases) need to update and test it for all cases
resolved this one!!
scratch build is available on http://koji.fedoraproject.org/koji/taskinfo?taskID=2353995
i have tested it from my side so it will not add any regression
please test this and let me know your view on same
modified source file is @ http://pravins.fedorapeople.org/Meera.sfd
binary file for testing @ http://pravins.fedorapeople.org/Meera.ttf
Naveen can you build this for devel?
Created attachment 436040 [details]
sfd file working well on pango and icu
working more on same problem
things word well with Pango and ICU but looks like QT is not processing ZWNJ in gusb and gpos
Created attachment 436041 [details]
ttf file for testing
(In reply to comment #13)
> Created an attachment (id=436041) [details]
> ttf file for testing
naveen lets wait for testing of this ttf
then will do build for fedora
Created attachment 437843 [details]
source file with enhancements
this file is fixing isssue
i.e when U+0d4d followed by any punctuation mark
ക്( ക്1 ക്: etc
and also resolved problem of cut for U+0d02 and U+0d03
naveen can you build this for fedora?
Yep, I will do it.
Created attachment 438942 [details]
smc-fonts_616324.patch: created from modified file submitted by Pravin S
smc-fonts-4.4-2.fc14 has been submitted as an update for Fedora 14.
smc-fonts-4.4-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update smc-fonts'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/smc-fonts-4.4-2.fc14
smc-fonts-4.4-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.