DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 Glenn Adams changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #6 from Glenn Adams 2012-04-01 13:42:57 UTC --- batch transition to closed for remaining resolved bugs -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
Jonathan, I should also add that an important effect of using writing-mode="rl" on fo:page-sequence is that this makes the default bidirectional level right-to-left on blocks (e.g., paragraphs). If you then need to have certain blocks use left-to-right as their default bidi level, then you can use one of the following: (1) wrap the block's content with fo:bidi-override, e.g., ... (2) wrap the block's content with explicit Unicode bidi control characters (i.e., RLE and PDF): ... (3) wrap the block with a relative block-container with a left-to-right writing mode, e.g., ... These techniques actually produce slightly different treatment at the bidi level. The first and second above keep the block at the same default bidi level prescribed by the page-sequence's writing mode, namely right-to-left, but inserts a new left-to-right embedding level into which the block's content is scoped. In contrast, the third technique actually changes the default bidi level of the blocks contained in the block-container to left-to-right. Note that neither of the following work: ... or ... because neither of these properties (writing-mode and direction) apply to fo:block. It's a little confusing, as one might guess these would work, however, that's not how XSL-FO is defined. Note also that techniques (1) and (2) above are logically equivalent. That is, fo:bidi-override is just a way to express Unicode BIDI control characters using XML markup instead of plain text control characters. Regards, Glenn On Mon, Oct 10, 2011 at 11:07 PM, Jonathan Levinson < jonathan.levin...@intersystems.com> wrote: > Our team switched to the version at https://github.com/skynavga/fop and > did not run into the issue. > > Our thanks to Glenn Adams for his extremely helpful critique of our .fo > file. Specifying writing-mode solved an issue for us. > > Best Regards, > Jonathan Levinson > Senior Software Developer > Object Group > InterSystems > > > > -Original Message- > > From: bugzi...@apache.org [mailto:bugzi...@apache.org] > > Sent: Monday, October 10, 2011 11:01 AM > > To: fop-dev@xmlgraphics.apache.org > > Subject: DO NOT REPLY [Bug 51984] Complex script version of FOP goes into > > infinite loop > > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 > > > > --- Comment #4 from Matthias Reischenbacher 2011- > > 10-10 15:01:09 UTC --- This could be related to: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=51282 > > which was actually a bug introduced in trunk. Probably you are using an > older > > version of the complex script branch, where the fix hasn't been merged > yet. > > > > -- > > Configure bugmail: > https://issues.apache.org/bugzilla/userprefs.cgi?tab=email > > --- You are receiving this mail because: --- You are the assignee > for the > > bug. > >
DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 --- Comment #5 from Glenn Adams 2011-10-10 23:23:43 UTC --- (In reply to comment #2) > (2) you should use the writing-mode attribute on fo:page-sequence (or on > fo:block-container) to specify the writing mode of the generated reference > areas; for example, specifying writing-mode="rl" on fo:page-sequence will > automatically make the first column in a multi-column page the right-most > column, and make the first column in a table the right-most column, and will > align the start edge with the right edge, so you don't need to explicitly > specify right alignment; note that text-align="start|end" is now resolved > according to writing mode; I should also add that an important effect of using writing-mode="rl" on fo:page-sequence is that this makes the default bidirectional level right-to-left on blocks (e.g., paragraphs). If you then need to have certain blocks use left-to-right as their default bidi level, then you can use one of the following: (1) wrap the block's content with fo:bidi-override, e.g., ... (2) wrap the block's content with explicit Unicode bidi control characters (i.e., RLE and PDF): ... (3) wrap the block with a relative block-container with a left-to-right writing mode, e.g., ... These techniques actually produce slightly different treatment at the bidi level. The first and second above keep the block at the same default bidi level prescribed by the page-sequence's writing mode, namely right-to-left, but inserts a new left-to-right embedding level into which the block's content is scoped. In contrast, the third technique actually changes the default bidi level of the blocks contained in the block-container to left-to-right. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
RE: DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
Our team switched to the version at https://github.com/skynavga/fop and did not run into the issue. Our thanks to Glenn Adams for his extremely helpful critique of our .fo file. Specifying writing-mode solved an issue for us. Best Regards, Jonathan Levinson Senior Software Developer Object Group InterSystems > -Original Message- > From: bugzi...@apache.org [mailto:bugzi...@apache.org] > Sent: Monday, October 10, 2011 11:01 AM > To: fop-dev@xmlgraphics.apache.org > Subject: DO NOT REPLY [Bug 51984] Complex script version of FOP goes into > infinite loop > > https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 > > --- Comment #4 from Matthias Reischenbacher 2011- > 10-10 15:01:09 UTC --- This could be related to: > https://issues.apache.org/bugzilla/show_bug.cgi?id=51282 > which was actually a bug introduced in trunk. Probably you are using an older > version of the complex script branch, where the fix hasn't been merged yet. > > -- > Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email > --- You are receiving this mail because: --- You are the assignee for > the > bug.
DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 --- Comment #4 from Matthias Reischenbacher 2011-10-10 15:01:09 UTC --- This could be related to: https://issues.apache.org/bugzilla/show_bug.cgi?id=51282 which was actually a bug introduced in trunk. Probably you are using an older version of the complex script branch, where the fix hasn't been merged yet. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 --- Comment #3 from Glenn Adams 2011-10-09 03:02:29 UTC --- Created attachment 27743 --> https://issues.apache.org/bugzilla/attachment.cgi?id=27743 generated PDF using arial with current dev branch code -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 Glenn Adams changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME OS/Version||All --- Comment #2 from Glenn Adams 2011-10-09 03:00:22 UTC --- The supplied input FO file WORKSFORME without any loop behavior, execution time 3 secs (mostly startup). I'm attaching the output PDF file. I did not use the XCONF file. For the most part, you do not need to use XCONF to configure fonts in FOP 1.0 and later, unless you wish to subset your system installed fonts. My XCONF file has the following PDF renderer configuration: flate I'm using my current dev work branch at [1]. I can't say whether the build you tried works or not, as that is not one of my builds. Also, please note the following: (1) in general, you should use fonts designed for Arabic and indicated to be supported at [2], e.g., Simplified Arabic, Traditional Arabic, etc.; other OpenType fonts that contain Arabic glyphs and OpenType AAT (GSUB/GPOS) tables may work, but haven't been verified; [apparently Arial on my Mac does happen to have Arabic glyphs and OTF AAT tables, so it happens to work] (2) you should use the writing-mode attribute on fo:page-sequence (or on fo:block-container) to specify the writing mode of the generated reference areas; for example, specifying writing-mode="rl" on fo:page-sequence will automatically make the first column in a multi-column page the right-most column, and make the first column in a table the right-most column, and will align the start edge with the right edge, so you don't need to explicitly specify right alignment; note that text-align="start|end" is now resolved according to writing mode; [1] http://github.com/skynavga/fop [2] http://skynav.trac.cvsdude.com/fop/wiki/SupportedFonts -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 51984] Complex script version of FOP goes into infinite loop
https://issues.apache.org/bugzilla/show_bug.cgi?id=51984 --- Comment #1 from Jonathan Levinson 2011-10-06 23:01:30 UTC --- Created attachment 27713 --> https://issues.apache.org/bugzilla/attachment.cgi?id=27713 fop.xconf used in reproducing problem This is the fop.xconf I used in what looks like an infinite loop problem. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
