<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Text runs of RTL scripts (e.g. Arabic, Hebrew, Persian) from imported PDF are reversed, PDFIProcessor::mirrorString not behaving"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=104597#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Text runs of RTL scripts (e.g. Arabic, Hebrew, Persian) from imported PDF are reversed, PDFIProcessor::mirrorString not behaving"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=104597">bug 104597</a>
from <span class="vcard"><a class="email" href="mailto:vvort@yandex.ru" title="vvort@yandex.ru">vvort@yandex.ru</a>
</span></b>
<pre>TextElements are created just in one place: inside processGlyphLine function.
Also there they are placed inside new FrameElement.
Characters, which are processed inside processGlyphLine call are having the
same transformation because of checks inside drawGlyphs call.
So I think that transformation check inside optimizeTextElements call should be
removed. Alongside with notTransformed function.
But, sadly, this can still produce side effects, because lot of poorly tested
semi-dead code of pdfimport may come to life.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>