Hi guys.
I didn't get any response and decided to remind about this patch. Do I
need to change/fix it?
Regards,
Dmitry
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
On 15.8.2018 at 12:56 zyx wrote:
there's a real mess when pdf_uint16be really holds big-endian value
Oops, there was meant to be pdf_utf16be, not pdf_uint16be, of course.
zyx
--
Check out the vibrant tech comm
Hi,
I just committed a change, r1935 [1], which tries to address an issue
with some characters not being found by
PdfFontMetricsBase14::GetGlyphIdUnicode(). This had been discovered
with a PdfEncodingDifference and I chose this lame change only because
there's a real mess when pdf_uint16be