<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN pdf: When opening a PDF with RTL language text in Draw, text gets mirrored" href="https://bugs.documentfoundation.org/show_bug.cgi?id=89471#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN pdf: When opening a PDF with RTL language text in Draw, text gets mirrored" href="https://bugs.documentfoundation.org/show_bug.cgi?id=89471">bug 89471</a> from <a class="email" href="mailto:eyalroz@technion.ac.il" title="Eyal Rozenberg <eyalroz@technion.ac.il>"> Eyal Rozenberg</a> <pre>(In reply to Khaled Hosny from <a href="show_bug.cgi?id=89471#c18">comment #18</a>) > PDF outputs glyphs in visual order, so the original (logical) order of the > text is lost, so the reverse of the bidi algorithm needs to be applied to > the text extracted from the PDF, but there is no reliable or documented > algorithm to do this. Oh, no no no! We seem to have a huge misunderstanding with respect to this bug. Stuart, Khaled - the bug is not about how the original text order reconstruction is failing for RTL. The bug is that it is _performed_ at all. Basically, nothing in the PDF should be touched when we open it in Draw, unless the user actively change it. If I open a PDF file in Draw, then save it - I should get a PDF with essentially the same thing that came in. Only if I modify a specific frame/box/object within the PDF is Draw allowed to do any of this reconstruction stuff. If I touch something and the RTL text gets flipped or messed up due to my edit - that's sad, but it's not terrible. I can either not-touch it, or replace it (but just it) with newly-written text. Now, I agree that proper reconstruction of RTL text runs from arbitrary PDFs is difficult and challenging; but that would be a request of an interesting future feature, not a bug report. (PS - If LO Draw could write meta-data/hints regarding the correct logical order, it could at least do perfect reconstruction for those files. But that too is a feature request and doesn't belong in this bug.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>