[ https://issues.apache.org/jira/browse/FOP-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811800#comment-15811800 ]
simon steiner commented on FOP-2580: ------------------------------------ Try adding to fop.xconf after <fop version="1.0">: <complex-scripts disabled="true" /> > Wrong Position of Thai Glyph in FOP 2.0+ (Binary version) > --------------------------------------------------------- > > Key: FOP-2580 > URL: https://issues.apache.org/jira/browse/FOP-2580 > Project: FOP > Issue Type: Bug > Components: documentation, font/unqualified > Affects Versions: 2.0, 2.1 > Environment: Windows 10 64bit CPU Core I-5 Ram 8G JRE 1.80_73 fop > binary 2.1 > Reporter: AEKAPAN TAWEELUER > Labels: build > Fix For: 1.1 > > Attachments: Norasi.ttf, fop.xconf, leelawad.ttf, log.txt, true.pdf, > wrong.fo, wrong.pdf > > > Glyph of Thai Font have problem when start in new line or have white space in > front of word. > In Example Wrong.pdf you'll see upper and lower glyph shift to the right 1 > character when the base character no have any character before or have white > space before. > "อ ิ" the true is should be "อิ" > "อกี" the true is should be "อีก" > "อ ุ" the true is should be "อุ" > "อบุ" the true is should be "อุบ" > remark : Font Angsana New AngsanaUPC , Leelawadee , Norasi and Tahoma are > most use in Thai font. > I use Windows command line (cmd) to generate pdf file. > example command line > C:\fop-2.1>fop.bat fop -c conf\fop.xconf -fo wrong.fo wrong.pdf -- This message was sent by Atlassian JIRA (v6.3.4#6332)