> a) Currently the characters are painted in two ways in the current source: > 1) the source itself handles the shaping > 2) Qt handles the shaping > It seems that it is possible to let Qt do a part (not all) of the first item > too. I am not sure yet! I will investigate the suggestion more. >
I see no great advantage to doing this at the moment, and on the other
hand I think it would involve a large amount of work, and major changes
which would almost certainly introduce new bugs. Given that the current
situation is very stable, I think it would be a mistake to try to
switch, unless there is a very compelling reason to do so.
I see. This is currently a right decision.
> b) The current code in the method "Paragraph::transformChar" has a bug,
> when the prev_char is a COMPOSE character (such as FATHA) and the previous
> BASE character is a SPECIAL character (such as ALEF). In this case the
> current character (such as BAA) gets the medial form and gets connected to
> the previous SPECIAL character which is not correct. The correct way to
> handle this situation is that, similar to the next_char, the first previous
> non-COMPOSE character should be assigned to the prev_char if exists.
>
Any progress with this, Mostafa? I don't know the transformChar code,
but it sounds like the changes you're suggesting shouldn't be too
hard...? If I can help out in any way, I'd be happy to try...
It is attached.
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
diff.paragraph.C
Description: 1599317532-diff.paragraph.C
