https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 Amit Gupta <amitddng135@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amitddng135@gmail.com -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 --- Comment #1 from Chris Nighswonger <cnighswonger@foundations.edu> --- Quoting from the mailing list: This problem seems to be present for most Indian languages whenever they have conjunct clusters in their call numbers (depicted as grapheme clusters in an unicoded string). To describe the problem simply - the order of chars rendered is incorrect in the output. For example the string - "শেখর" is represented by the following code points - \x{09B6}\x{09C7}\x{0996}\x{09B0}. Now here is the catch: \x{09B6} represents the bengali letter SHA, whereas \x{09C7} represents the bengali vowel sign E; however in the correct linguistic visual presentation, the vowel sign E sits before the SHA, which is not how the codepoints are arranged in the unicode string. I looked around PDF::Reuse, Text::PDF::TTFont etc modules, what seems to me to be the root of this problem is the unpacku() method which is pushing the unicode characters into an array in order to introduce them into the PDF content stream with the correct font information. However, being pushed in in that order, I think may be the cause of this problem, which would make this an upstream issue rather than a Koha bug. cheers indranil -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 --- Comment #3 from Indranil Das Gupta <indradg@l2c2.co.in> --- Yes! In fact, I was perhaps hasty in trashing unpacku() method. The root of the trouble is the out_text() method where the the actual glyphs are parsed into the PDF content stream. What is happening here is that the individual codepoints pushed into @clist by unpacku() are being listed out one at a time into the PDF content stream as glyphs, *without* the necessary glyph reordering taking place. So I would expect every single abiguda writing system to be be impacted. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 --- Comment #5 from Indranil Das Gupta <indradg@l2c2.co.in> --- Hi Chris, The example I referred to on the m/l has the following codepoint order \x{09B6}\x{09C7}\x{0996}\x{09B0} and that's exactly how PDF::Reuse and PDI::API2 is pushing it out. However as per rules of glyph reordered necessity by Bengali, the actual ordering of glyphs (as opposed to the codepoint order) should be \x{09C7}\x{09B6}\x{0996}\x{09B0}. LibreOffice which uses the ICU rules, handles this perfectly within ODF as well as during the PDF export, as does any software that uses Pango as the rendering backend. basically calls need to be made to pick up the correct information from the GSUB and GPOS tables of the font being embedded, which this two perl libs apparently (from my limited reading so far) do not do. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 Josef Moravec <josef.moravec@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |BLOCKED CC| |josef.moravec@gmail.com --- Comment #7 from Josef Moravec <josef.moravec@gmail.com> --- Marking blocked because of comment 6 -- You are receiving this mail because: You are watching all bug changes.