Bug report for Fop [2012/07/22]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] visibility property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align=end | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align=justify doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PATCH] Handling of page-number-citation-last |
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #6 from na...@th.ibm.com --- The first 3 lines of generated PDF from you give a near correct look. The problem is at character 26, Mai-Ek. It ship too far to the left. I have few questions regarding to your output. I changed my fo:block element removing all attribute except font-family. My result is different from what you got. It is look similar to the second line in first jpg attachment. Why the different ? Another question is whether the dflt shall be loaded when specific language is given ? Most Thai fonts gsub/gpos information use dflt language and thai script. Please correct me if i'm wrong. Per http://www.microsoft.com/typography/otfntdev/standot/appen.aspx, my understanding is when the th language is missing from font info, it shall fall back to dflt. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #7 from na...@th.ibm.com --- Created attachment 29094 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29094action=edit the xml data used to reproduce a problem -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #8 from na...@th.ibm.com --- Created attachment 29095 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29095action=edit the xslt which transform thaidata.xml into fo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #9 from na...@th.ibm.com --- Created attachment 29096 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29096action=edit The generated PDF file. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 na...@th.ibm.com changed: What|Removed |Added Attachment #29095|application/octet-stream|text/xml mime type|| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #10 from Glenn Adams gad...@apache.org --- (In reply to comment #6) The first 3 lines of generated PDF from you give a near correct look. The problem is at character 26, Mai-Ek. It ship too far to the left. I understand. I will investigate this further. I have few questions regarding to your output. I changed my fo:block element removing all attribute except font-family. My result is different from what you got. It is look similar to the second line in first jpg attachment. Why the different ? That's hard to say. I am using FOP1.1rc1 and Version 5.0 of the AngsanaUPC font (from Windows 7). If you are using different versions, then that could cause the difference. Another question is whether the dflt shall be loaded when specific language is given ? Most Thai fonts gsub/gpos information use dflt language and thai script. Please correct me if i'm wrong. Per http://www.microsoft.com/typography/otfntdev/standot/appen.aspx, my understanding is when the th language is missing from font info, it shall fall back to dflt. The current implementation in FOP will use 'dflt' for the OT Language lookup if the value of the language attribute is not specified or is specified as an empty string. Similarly, it will use 'thai' for the OT Script lookup if the dominant characters are Thai, the script attribute is not specified, is specified as the empty string, as 'auto', or as 'thai'. If 'th' or 'TH' is specified as the language, then presumably it should also produce a successful lookup. However, this will depend on whether the font designer/creator provides an OT lookup for language = 'th'|'TH' and script = 'thai'. Taking a look at AngsanaUPC (using the Adobe TTX tool), I see that the GSUB table only lists the default language system, and does not include 'TH', so that would explain why specifying language='TH' results in no lookup. ScriptList !-- ScriptCount=1 -- ScriptRecord index=0 ScriptTag value=thai/ Script DefaultLangSys ReqFeatureIndex value=65535/ !-- FeatureCount=1 -- FeatureIndex index=0 value=0/ /DefaultLangSys !-- LangSysCount=0 -- /Script /ScriptRecord /ScriptList -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #11 from Glenn Adams gad...@apache.org --- (In reply to comment #8) Created attachment 29095 [details] the xslt which transform thaidata.xml into fo Please provide an FO input file. I don't care about XSLT/XML files (they are just noise). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #12 from na...@th.ibm.com --- Created attachment 29097 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29097action=edit FO file for reproduce the problem -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53573] Fop invalid position combining mark for Thai text (CTL)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53573 --- Comment #13 from na...@th.ibm.com --- (In reply to comment #10) (In reply to comment #6) The first 3 lines of generated PDF from you give a near correct look. The problem is at character 26, Mai-Ek. It ship too far to the left. I understand. I will investigate this further. I have few questions regarding to your output. I changed my fo:block element removing all attribute except font-family. My result is different from what you got. It is look similar to the second line in first jpg attachment. Why the different ? That's hard to say. I am using FOP1.1rc1 and Version 5.0 of the AngsanaUPC font (from Windows 7). If you are using different versions, then that could cause the difference. I'm using AngsanaUPC 5.0 from Windows 7 SP1 64 bits [Version 6.1.7601] I uses FOP from SVN trunk, checked out today. -- You are receiving this mail because: You are the assignee for the bug.
