https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084
--- Comment #1 from Chris Nighswonger <[email protected]> --- 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. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
