<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Arabic PDF export is messy in old files < 5.3"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=113428#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Arabic PDF export is messy in old files < 5.3"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=113428">bug 113428</a>
from <span class="vcard"><a class="email" href="mailto:xiscofauli@libreoffice.org" title="Xisco FaulĂ <xiscofauli@libreoffice.org>"> <span class="fn">Xisco FaulĂ</span></a>
</span></b>
<pre>Ok, I've bisected it again using the UI at export time and it points me to this
commit instead:
author Khaled Hosny <<a href="mailto:khaledhosny@eglug.org">khaledhosny@eglug.org</a>> 2016-12-07 22:43:09 (GMT)
committer Khaled Hosny <<a href="mailto:khaledhosny@eglug.org">khaledhosny@eglug.org</a>> 2016-12-10 00:58:26
(GMT)
commit b894104a0b02a9b074c76feb925389d7bee6a493 (patch)
tree 93e8a9362281f2c992f503a4e38ec17d04a9132b
parent b52167df08511239c3d08904a3d12a3c92141f38 (diff)
Pass GlyphItem around
We have this nice structure that contains (almost) all the information
we need, so pass it around instead of passing separate fragments of said
information.
The ultimate is to kill the horrible sal_GlyphId hack if encoding
various bits of information in the higher bits of a 32-bit integer.
@Khaled, Does it make more sense now?</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>