Re: #x200b; (Zero width space) not work
Hi i can add a file, is not very short because this bug is visible if there is two pages document! http://old.nabble.com/file/p32873641/fo.xml fo.xml Pascal Sancho wrote: Can you post a [short] XSL-FO (not XSL-T) that demonstrates the issue? I cannot reproduce what you describe. Le 22/11/2011 14:16, pedro a écrit : I use fop 0,95 and the output is a pdf that i open with Acrobat X or Foxit Redaer. Pascal Sancho wrote: Pedro, what is the output? PDF, XSL-FO, other? whitch tool (and version) do you use to see it? I suspect this is a viewer issue, FOP works fine with such character. Note that [disable-output-escaping=yes] is only for lt; or amp;, and its use is discourged by good practices. Le 22/11/2011 12:11, pedro a écrit : Hi all i use the #x200b; character in a table cell before i call a marker-retriever to workaround a bug(the solution is good), but the proble is that #x200b; characher is printed like a ? while i think isn't a printable character. Ani idea? [code] fo:table-cell fo:block font-family=Courier font-size=8pt text-align=center xsl:text disable-output-escaping=yes#x200b;/xsl:text fo:retrieve-marker retrieve-class-name=contr-conai retrieve-position=last-ending-within-page retrieve-boundary=page-sequence/ /fo:block /fo:table-cell [/code] i try also to put #x200b; directly in block or with ZWNJ and doesn't work. -- Pascal -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://old.nabble.com/--x200b--%28Zero-width-space%29-not-work-tp32872366p32873641.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: #x200b; (Zero width space) not work
Hi Pedro, I see no ZWSP in your file. you can insert it by hand directly in your FO, just before each fo:retrieve-marker, then check if output is correct. If yes, then have a look into your XSLT or XSLT engine (I don't know witch engine you use). If no, re-attach moddified XSL-FO, this including ZWSP. Le 23/11/2011 09:09, pedro a écrit : Hi i can add a file, is not very short because this bug is visible if there is two pages document! http://old.nabble.com/file/p32873641/fo.xml fo.xml Pascal Sancho wrote: Can you post a [short] XSL-FO (not XSL-T) that demonstrates the issue? I cannot reproduce what you describe. Le 22/11/2011 14:16, pedro a écrit : I use fop 0,95 and the output is a pdf that i open with Acrobat X or Foxit Redaer. Pascal Sancho wrote: Pedro, what is the output? PDF, XSL-FO, other? whitch tool (and version) do you use to see it? I suspect this is a viewer issue, FOP works fine with such character. Note that [disable-output-escaping=yes] is only for lt; or amp;, and its use is discourged by good practices. Le 22/11/2011 12:11, pedro a écrit : Hi all i use the #x200b; character in a table cell before i call a marker-retriever to workaround a bug(the solution is good), but the proble is that #x200b; characher is printed like a ? while i think isn't a printable character. Ani idea? [code] fo:table-cell fo:block font-family=Courier font-size=8pt text-align=center xsl:text disable-output-escaping=yes#x200b;/xsl:text fo:retrieve-marker retrieve-class-name=contr-conai retrieve-position=last-ending-within-page retrieve-boundary=page-sequence/ /fo:block /fo:table-cell [/code] i try also to put #x200b; directly in block or with ZWNJ and doesn't work. -- Pascal -- Pascal -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Multi threading problems with FOP 1.0
Dear FOP users, I am using the FOP version 1.0 under Windows x64. Lately I have integrated JPPF in order to regenerate my PDFs faster and I experience the followings strange errors. For example inside the XSLT I place 8pt but the error in the console outputs (pt8pt): [ERROR][org.apache.fop.fo.properties.PropertyMaker.convert(148)]: Unknown length unit 'pt8pt' This kind of behaviour happens at other places as well: [ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value encountered in color=whitewhite: org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined whitewhite; property:'color' (See position 57:85) Only white at the XSLT. [ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value encountered in background-color=#6777cf#6777cf: org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined #6777cf#6777cf; property:'background-color' (See position 57:100) [ERROR][org.apache.fop.apps.FopFactory.resolveURI(755)]: Attempt to resolve URI 'F:\JPF:\JPPF\Node1\resources\images\na_b.gif')' failed: Here the URI is given correctly at the XSLT processor: F:\JPPF\Node1\resources\images These kind of errors continue. Any pointer would be really helpful. I am considering using the trunk version as well in order to close some other reported and patched bugs of FOP 1.0 Regards, Klearchos - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Multi threading problems with FOP 1.0
Hello I have similar things but as far I can remember this was always related to svg as part of an fo stylesheet. I should/could dive into the mail archives (and perhaps) bugzilla to refresh my memory, as I remember there were discussion on this, but perhaps you can indicate whether you are using svg at all in your fo? Peter On 23 Nov 2011, at 12:12, Klearchos Klearchou wrote: Dear FOP users, I am using the FOP version 1.0 under Windows x64. Lately I have integrated JPPF in order to regenerate my PDFs faster and I experience the followings strange errors. For example inside the XSLT I place 8pt but the error in the console outputs (pt8pt): [ERROR][org.apache.fop.fo.properties.PropertyMaker.convert(148)]: Unknown length unit 'pt8pt' This kind of behaviour happens at other places as well: [ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value encountered in color=whitewhite: org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined whitewhite; property:'color' (See position 57:85) Only white at the XSLT. [ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value encountered in background-color=#6777cf#6777cf: org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined #6777cf#6777cf; property:'background-color' (See position 57:100) [ERROR][org.apache.fop.apps.FopFactory.resolveURI(755)]: Attempt to resolve URI 'F:\JPF:\JPPF\Node1\resources\images\na_b.gif')' failed: Here the URI is given correctly at the XSLT processor: F:\JPPF\Node1\resources\images These kind of errors continue. Any pointer would be really helpful. I am considering using the trunk version as well in order to close some other reported and patched bugs of FOP 1.0 Regards, Klearchos - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Multi threading problems with FOP 1.0
Hello,
I found this link related to SVG:
http://xmlgraphics.apache.org/fop/trunk/graphics.html#svg
based on that I use this:
fo:external-graphic src=url('{$link}') content-width=scale-to-fit
width=20mm /
The link is an absolute path to a JPEG file.
This erroneous behaviour happens not only at the URI of the image but in
other places.
For example I have hard-coded in my XSLT the following '8pt' and the
generated FO contains the problematic 'pt8pt'.
I print the whole FO when an error happens in order to check it.
Please let me know if you need more information.
Regards,
Klearchos
On 11/23/2011 2:18 PM, Peter Coppens wrote:
Hello
I have similar things but as far I can remember this was always related to svg
as part of an fo stylesheet.
I should/could dive into the mail archives (and perhaps) bugzilla to refresh my
memory, as I remember there were discussion on this, but perhaps you can
indicate whether you are using svg at all in your fo?
Peter
On 23 Nov 2011, at 12:12, Klearchos Klearchou wrote:
Dear FOP users,
I am using the FOP version 1.0 under Windows x64.
Lately I have integrated JPPF in order to regenerate my PDFs faster and I
experience the followings strange errors.
For example inside the XSLT I place 8pt but the error in the console outputs
(pt8pt):
[ERROR][org.apache.fop.fo.properties.PropertyMaker.convert(148)]: Unknown
length unit 'pt8pt'
This kind of behaviour happens at other places as well:
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value
encountered in color=whitewhite: org.apache.fop.fo.expr.PropertyException:
null:56:15: No conversion defined whitewhite; property:'color' (See position 57:85)
Only white at the XSLT.
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value
encountered in background-color=#6777cf#6777cf:
org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined
#6777cf#6777cf; property:'background-color' (See position 57:100)
[ERROR][org.apache.fop.apps.FopFactory.resolveURI(755)]: Attempt to resolve URI
'F:\JPF:\JPPF\Node1\resources\images\na_b.gif')' failed:
Here the URI is given correctly at the XSLT processor:
F:\JPPF\Node1\resources\images
These kind of errors continue.
Any pointer would be really helpful.
I am considering using the trunk version as well in order to close some other
reported and patched bugs of FOP 1.0
Regards,
Klearchos
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Multi threading problems with FOP 1.0
Hi,
As you wrote, the problem occurs during the transformation of XML + XSLT to
XSL:FO and therefore this is not related to Apache FOP. I had a similar issue
some years ago and the problem was a concurrency issue inside Xalan. Try
upgrading to Xalan 2.7.1 were this was definitely fixed. Note that Xalan may
also be loaded from the 'endorsed' directory of application servers.
Having said that, there are indeed a few concurrency issues in Apache 1.0 which
are fixed in FOP trunk. They don't seem to be related to this but if you have
many threads running , I am sure you will sooner or later encounter them. If
this does not solve the problem, then explaining or attaching code on how you
use Apache FOP will help.
Alexis
On Nov 23, 2011, at 2:44 PM, Klearchos Klearchou wrote:
Hello,
I found this link related to SVG:
http://xmlgraphics.apache.org/fop/trunk/graphics.html#svg
based on that I use this:
fo:external-graphic src=url('{$link}') content-width=scale-to-fit
width=20mm /
The link is an absolute path to a JPEG file.
This erroneous behaviour happens not only at the URI of the image but in
other places.
For example I have hard-coded in my XSLT the following '8pt' and the
generated FO contains the problematic 'pt8pt'.
I print the whole FO when an error happens in order to check it.
Please let me know if you need more information.
Regards,
Klearchos
On 11/23/2011 2:18 PM, Peter Coppens wrote:
Hello
I have similar things but as far I can remember this was always related to
svg as part of an fo stylesheet.
I should/could dive into the mail archives (and perhaps) bugzilla to refresh
my memory, as I remember there were discussion on this, but perhaps you can
indicate whether you are using svg at all in your fo?
Peter
On 23 Nov 2011, at 12:12, Klearchos Klearchou wrote:
Dear FOP users,
I am using the FOP version 1.0 under Windows x64.
Lately I have integrated JPPF in order to regenerate my PDFs faster and I
experience the followings strange errors.
For example inside the XSLT I place 8pt but the error in the console
outputs (pt8pt):
[ERROR][org.apache.fop.fo.properties.PropertyMaker.convert(148)]: Unknown
length unit 'pt8pt'
This kind of behaviour happens at other places as well:
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property
value encountered in color=whitewhite:
org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined
whitewhite; property:'color' (See position 57:85)
Only white at the XSLT.
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property
value encountered in background-color=#6777cf#6777cf:
org.apache.fop.fo.expr.PropertyException: null:56:15: No conversion defined
#6777cf#6777cf; property:'background-color' (See position 57:100)
[ERROR][org.apache.fop.apps.FopFactory.resolveURI(755)]: Attempt to resolve
URI 'F:\JPF:\JPPF\Node1\resources\images\na_b.gif')' failed:
Here the URI is given correctly at the XSLT processor:
F:\JPPF\Node1\resources\images
These kind of errors continue.
Any pointer would be really helpful.
I am considering using the trunk version as well in order to close some
other reported and patched bugs of FOP 1.0
Regards,
Klearchos
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Multi threading problems with FOP 1.0
Thank you Pascal,
I will correct this and I will introduce the file protocol in front.
Regards,
Klearchos
On 11/23/2011 5:01 PM, Pascal Sancho wrote:
Hi,
'D:\java\...' is not a valid URL (mainly because of antislashes).
Try 'file:///D:/java/...'.
I think you can omit the host part: 'file:/D:/java/...'.
Le 23/11/2011 15:24, Klearchos Klearchou a écrit :
Hi Alexi,
thank you for your answer.
It seems that with the 2.7.1 these kind of problems disappear.
It seems that this is the solution for the problem!
I tried to use the FOP trunk as well but I receive the following error:
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(83)]: Invalid
property value encountered in
src=url('D:\java\JPPF-2.5-node\resources\images\false_alerts\image.jpg'):
org.apache.fop.fo.expr.PropertyException: Invalid URI specified (See
position 57:143)
org.apache.fop.fo.expr.PropertyException: Invalid URI specified
at
org.apache.fop.fo.properties.URIProperty$Maker.make(URIProperty.java:141)
at
org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:409)
at
org.apache.fop.fo.PropertyList.addAttributesToList(PropertyList.java:317)
at org.apache.fop.fo.FObj.processNode(FObj.java:120)
at
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:282)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:171)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
at test.package.CreatePDFTask.convertFO2PDF(CreatePDFTask.java:291)
It reminds me an issue that I have seen yesterday at FOP's bugzilla.
Have you encountered this error as well?
Regards,
Klearchos
On 11/23/2011 3:09 PM, Alexios Giotis wrote:
Hi,
As you wrote, the problem occurs during the transformation of XML + XSLT to
XSL:FO and therefore this is not related to Apache FOP. I had a similar issue
some years ago and the problem was a concurrency issue inside Xalan. Try
upgrading to Xalan 2.7.1 were this was definitely fixed. Note that Xalan may
also be loaded from the 'endorsed' directory of application servers.
Having said that, there are indeed a few concurrency issues in Apache 1.0 which
are fixed in FOP trunk. They don't seem to be related to this but if you have
many threads running , I am sure you will sooner or later encounter them. If
this does not solve the problem, then explaining or attaching code on how you
use Apache FOP will help.
Alexis
On Nov 23, 2011, at 2:44 PM, Klearchos Klearchou wrote:
Hello,
I found this link related to SVG:
http://xmlgraphics.apache.org/fop/trunk/graphics.html#svg
based on that I use this:
fo:external-graphic src=url('{$link}') content-width=scale-to-fit
width=20mm /
The link is an absolute path to a JPEG file.
This erroneous behaviour happens not only at the URI of the image but in other
places.
For example I have hard-coded in my XSLT the following '8pt' and the generated
FO contains the problematic 'pt8pt'.
I print the whole FO when an error happens in order to check it.
Please let me know if you need more information.
Regards,
Klearchos
On 11/23/2011 2:18 PM, Peter Coppens wrote:
Hello
I have similar things but as far I can remember this was always related to svg
as part of an fo stylesheet.
I should/could dive into the mail archives (and perhaps) bugzilla to refresh my
memory, as I remember there were discussion on this, but perhaps you can
indicate whether you are using svg at all in your fo?
Peter
On 23 Nov 2011, at 12:12, Klearchos Klearchou wrote:
Dear FOP users,
I am using the FOP version 1.0 under Windows x64.
Lately I have integrated JPPF in order to regenerate my PDFs faster and I
experience the followings strange errors.
For example inside the XSLT I place 8pt but the error in the console outputs
(pt8pt):
[ERROR][org.apache.fop.fo.properties.PropertyMaker.convert(148)]: Unknown
length unit 'pt8pt'
This kind of behaviour happens at other places as well:
[ERROR][org.apache.fop.apps.FOUserAgent.processEvent(82)]: Invalid property value
encountered in color=whitewhite:
Re: #x200b; (Zero width space) not work
Hi i think i attach a bad file, but i see in my fo transformation that the ZWNJ is replaced by a ? Is possible is a codification problem? http://old.nabble.com/file/p32874268/fo.xml fo.xml pedro wrote: Hi all i use the #x200b; character in a table cell before i call a marker-retriever to workaround a bug(the solution is good), but the proble is that #x200b; characher is printed like a ? while i think isn't a printable character. Ani idea? [code] fo:table-cell fo:block font-family=Courier font-size=8pt text-align=center xsl:text disable-output-escaping=yes#x200b;/xsl:text fo:retrieve-marker retrieve-class-name=contr-conai retrieve-position=last-ending-within-page retrieve-boundary=page-sequence/ /fo:block /fo:table-cell [/code] i try also to put #x200b; directly in block or with ZWNJ and doesn't work. -- View this message in context: http://old.nabble.com/--x200b--%28Zero-width-space%29-not-work-tp32872366p32874268.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Problem generating pdf from tifs whose dpi is set to zero
Hi I am using Apache FOP to generate PDF from jpegs and tifs.When generating pdf from tifs which have a dpi of 0 an IllegalStateException : resolution mus be set is thrown. I tried setting source resolution to 96dpi on FOPFactory ,but that did not work.I am using FOP 0.95. Please advise what I am missing to do. Thankyou -- View this message in context: http://old.nabble.com/Problem-generating-pdf-from-tifs-whose-dpi-is-set-to-zero-tp32874293p32874293.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Problem generating PDF from tifs with zero dpi
Have you tried setting the dpi in the image to something meaningful? You can use Gimp for that (assuming it will not choke with such image): Image -- Print Size..., and then set Resolution. Luis On 11/23/11 4:51 PM, qns.java wrote: Hi I am using Apache FOP to generate PDF from jpegs and tifs.When generating pdf from tifs which have a dpi of 0 an IllegalStateException : resolution mus be set is thrown. I tried setting source resolution to 96dpi on FOPFactory ,but that did not work.I am using FOP 0.95. Please advise what I am missing to do. Thankyou - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: #x200b; (Zero width space) not work
I see the ? in your source file (and in the generated PDF). Once I replace them by #x200b; they disappear from the PDF too. On 11/23/11 4:29 PM, pedro wrote: Hi i think i attach a bad file, but i see in my fo transformation that the ZWNJ is replaced by a ? Is possible is a codification problem? http://old.nabble.com/file/p32874268/fo.xml fo.xml pedro wrote: Hi all i use the#x200b; character in a table cell before i call a marker-retriever to workaround a bug(the solution is good), but the proble is that#x200b; characher is printed like a ? while i think isn't a printable character. Ani idea? [code] fo:table-cell fo:block font-family=Courier font-size=8pt text-align=center xsl:text disable-output-escaping=yes#x200b;/xsl:text fo:retrieve-marker retrieve-class-name=contr-conai retrieve-position=last-ending-within-page retrieve-boundary=page-sequence/ /fo:block /fo:table-cell [/code] i try also to put#x200b; directly in block or with ZWNJ and doesn't work. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
