<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - handling of rtl text inversion is too naive" href="https://bugs.freedesktop.org/show_bug.cgi?id=55977#c59">Comment # 59</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - handling of rtl text inversion is too naive" href="https://bugs.freedesktop.org/show_bug.cgi?id=55977">bug 55977</a> from <a class="email" href="mailto:khaledhosny@eglug.org" title="Khaled Hosny <khaledhosny@eglug.org>"> Khaled Hosny</a> <pre>Created <a href="attachment.cgi?id=120046" name="attach_120046" title="Fix finding Arabic Presentation Forms ligatures">attachment 120046</a> <a href="attachment.cgi?id=120046&action=edit" title="Fix finding Arabic Presentation Forms ligatures">[details]</a> <a href='page.cgi?id=splinter.html&bug=55977&attachment=120046'>[review]</a> Fix finding Arabic Presentation Forms ligatures PDF text containing Arabic Presentation forms ligatures is still not found after the previous commit. This because the ligatures are decomposed in logical order after normalisation, while the whole string is in visual order. For example the RTL text ABCD in visual order will be DCBA, and assuming B is a ligature, it will be decomposed to B1B2 so the string after normalization will be DCB1B2A while we are expecting it to be DCB2B1A. This patch reverses the order of the decomposition of RTL characters to work around this issue. This is to be applied on top of the previous patch.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>