Re: numbering programlisting/screen lines
Hi dear Chris! So you mean that this problem refers to some xsltproc issue... Thanks Nancy cbowditch wrote: nancy_b wrote: Hi dear Andreas! by the 'function' I mean the LineNumberring function. There is no such function in XSL-FO. The terms you are referring to, sound like docbook terminology. This list is about FOP and XSL-FO. For help with docbook I suggest that you subscribe to the docbook apps mailing list. Chris snip/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/numbering-programlisting-screen-lines-tf4271687.html#a12231881 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: numbering programlisting/screen lines
nancy_b wrote: Hi dear Chris! So you mean that this problem refers to some xsltproc issue... yes thats what it sounds like from what you've said! Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: embedding font Bundesbahn-Pi at FOP
Hi William, Most of the work involves entering all the charset data for ExpertEncoding and ExpertSubsetEncoding (contained in Appendix C of http://www.adobe.com/devnet/font/pdfs/5176.CFF.pdf) into src/codegen/fonts/encodings.xml - see http://issues.apache.org/bugzilla/show_bug.cgi?id=43143. Its not a difficult job, just quite a long one. If you are able to find the time to do this then I would be more happy get it working for you. Adrian. william wrote: Thanks Adrian, I wouldn't mind fixing it if there's no one wants to do it. But I would need some guidance on how to and what should I do since I've never followed fop-dev before. Thanks. Adrian Cumiskey wrote: Hi William (and all), This did turn out to be an encoding problem after all. Unfortunately I do not have the time at the moment to provide a fix for this problem. but I have provided a patch which provides the ability for FOP to correctly identify the type 1 font encoding. At least now you will be provided with a human readable log error message rather than NullPointerException :-). Maybe someone could take a look at implementing support for these encoding types? It wouldn't be too difficult, it would mostly involve adding data to src/codegen/fonts/encodings.xml. Most of the background information anyone would require for providing support for these encodings can be found in the patch I provided (http://issues.apache.org/bugzilla/show_bug.cgi?id=43143). If you are still using a metrics-url in your font configuration then you will need to regenerate your metrics file once this patch has been applied as the font encoding detection is flawed for detecting these encoding types for type 1 fonts in the existing implementation. Of course font you don't need to specify metrics-url attributes in your fop.xconf anymore in the latest trunk code and in the forthcoming 0.94 (and 0.93 if I am correct). You can just provide an embed-url and FOP will generate the metrics on the fly. e.g. font kerning=yes embed-url=Bundesba.pfb font-triplet name=Bundesbahn style=normal weight=normal/ /font All the best, Adrian. william wrote: Thanks Adrian and everyone, I have sent it to you for you to take a look at it (font and FO). if there's something that is useful for me/others to know, please do tell me. Otherwise, does anyone has any idea where else I can look for software solution that might accommodate this ? William. Adrian Cumiskey wrote: Hi William, Yes I think that might be the problem, it does look like an encoding problem to me. I took a quick look at the code and the NullPointerException you are experiencing would indicate that the encoding is not recognised by FOP and its failing to provide a CodePointMapping instance which is used internally by SingleByteFont. If you send me the font (and fo) I will try and take a quick look at it. Adrian. william wrote: Hi All, First of all, would like to thank you all developers and commiters at FOP. i've been using it for awhile now. I haven't had problem with embedding fonts before, except on this Bundesbahn-Pi font and another symbol/pi font. The error message is posted below. I'm using fop 0.93 and I need help with embedding this font. Is there anything to do with this? /currently present a problem because FOP cannot correctly determine the encoding of these two single-byte fonts through the PFM file. FOP now correctly interprets the encoding value in the XML font metrics file, but the PFMReader application writes UnknownEncoding to the generated XML file /If someone would try to work it out for me, i can send you the font to try out + .fo file. This is my configuration for the font: font metrics-url=Bundesbahn.xml kerning=yes embed-url=Bundesba.pfb font-triplet name=Bundesbahn style=normal weight=normal/ /font / *Error message generated by FOP:* 10/08/2007 06:16:13 org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:160) at org.apache.fop.cli.Main.main(Main.java:191) - java.lang.NullPointerException at org.apache.fop.fonts.SingleByteFont.hasChar(SingleByteFont.java:103) at org.apache.fop.fonts.LazyFont.hasChar(LazyFont.java:166) at org.apache.fop.fonts.Font.hasChar(Font.java:189) at org.apache.fop.fonts.Font.getCharWidth(Font.java:231) at org.apache.fop.layoutmgr.inline.TextLayoutManager.initialize(TextLayoutManager.java:188) ... Thank you, / - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To
horizontal text adjustement with FOP
Hi mailing list, does FOP support the horizontal adjustment of texts? thnx a lot! Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: horizontal text adjustement with FOP
Hi Simo, yes, try fo:block text-align=centerMy Text/fo:block cheers matthias - Ursprüngliche Mail Von: Sidi Mohamed Idrissi Yaghir [EMAIL PROTECTED] An: fop-users@xmlgraphics.apache.org Gesendet: Montag, den 20. August 2007, 14:03:40 Uhr Betreff: horizontal text adjustement with FOP Hi mailing list, does FOP support the horizontal adjustment of texts? thnx a lot! Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Alles was der Gesundheit und Entspannung dient. BE A BETTER MEDIZINMANN! www.yahoo.de/clever - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: horizontal text adjustement with FOP
Hi mailing list, Sorry, i meant in my last mail the vertical text adjustment and the 90° rotation of texts? is this possible with fop? thnx Simo Quoting Sidi Mohamed Idrissi Yaghir [EMAIL PROTECTED]: Hi mailing list, does FOP support the horizontal adjustment of texts? thnx a lot! Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Attributes of the fo-elements as parameter
Hi mailing list, is there a possibility to use the attributes of the fo-elements in the XSLT file as parameters??? this hier e.g. didn´t work: fo:table-cell width=xsl:value-of select=$widthParam / border-width=1px border-style=solid padding-right=10px i get this Error: [Fatal Error] test.xsl:24:40: The value of attribute width associated with an element type fo:table-cell must not contain the '' character. thnx Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Attributes of the fo-elements as parameter
Hi Simo, I would do: fo:table-cell border-width=1px border-style=solid padding-right=10px xsl:attribute name=widthxsl:value-of select=$widthParam //xsl:attirbute /fo:table Sidi Mohamed Idrissi Yaghir schrieb: Hi mailing list, is there a possibility to use the attributes of the fo-elements in the XSLT file as parameters??? this hier e.g. didn´t work: fo:table-cell width=xsl:value-of select=$widthParam / border-width=1px border-style=solid padding-right=10px i get this Error: [Fatal Error] test.xsl:24:40: The value of attribute width associated with an element type fo:table-cell must not contain the '' character. thnx Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Attributes of the fo-elements as parameter
or use this syntax :
fo:table-cell width={$widthParam}
border-width=1px border-style=solid padding-right=10px
2007/8/20, Stefan Heuer [EMAIL PROTECTED]:
Hi Simo,
I would do:
fo:table-cell border-width=1px border-style=solid
padding-right=10px
xsl:attribute name=widthxsl:value-of select=$widthParam
//xsl:attirbute
/fo:table
Sidi Mohamed Idrissi Yaghir schrieb:
Hi mailing list,
is there a possibility to use the attributes of the fo-elements in
the XSLT file as parameters???
this hier e.g. didn´t work:
fo:table-cell width=xsl:value-of select=$widthParam /
border-width=1px border-style=solid padding-right=10px
i get this Error:
[Fatal Error] test.xsl:24:40: The value of attribute width
associated with an element type fo:table-cell must not contain the
'' character.
thnx
Simo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: horizontal text adjustement with FOP
may be with reference-orientation? http://xmlgraphics.apache.org/fop/compliance.html#fo-property-reference-orientation 2007/8/20, Sidi Mohamed Idrissi Yaghir [EMAIL PROTECTED]: Hi mailing list, Sorry, i meant in my last mail the vertical text adjustment and the 90° rotation of texts? is this possible with fop? thnx Simo Quoting Sidi Mohamed Idrissi Yaghir [EMAIL PROTECTED]: Hi mailing list, does FOP support the horizontal adjustment of texts? thnx a lot! Simo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop cutting off lines - way to force wrap around?
Thanks for the reply Andreas - I had already considered option a but was hoping there was a way around having to parse the body since it'd be a headache but might have to grit my teeth and do it. Does anyone know if the wrap-option=wrap property put in an fo:block works in 0.93 or 0.92? I am currently using 0.25 (and wrap-option doesn't seem to work there - I put wrap-option=wrap and still get the same overflow errors and lines cutoff with japanese/korean/chinese documents), and know I will have to spend quite a bit of time reworking my code if I upgrade since a lot of the api has been changed from 0.25 and don't want to do that unless the wrap-option functions correctly (which would be worth the upgrade trouble as opposed to the parse body and insert break characters where appropriate method which seems to be the only other alternative unless I'm missing something). Thanks for any input. From: Andreas L Delmelle [EMAIL PROTECTED] Reply-To: fop-users@xmlgraphics.apache.org To: fop-users@xmlgraphics.apache.org Subject: Re: fop cutting off lines - way to force wrap around? Date: Wed, 18 Jul 2007 20:53:19 +0200 On Jul 18, 2007, at 18:45, ausj81 ausj81 wrote: Hi snip / The characters are encoded as entities in the xml so ampersand#x30a6;ampersand#x30a7;... and so on but they don't have spaces in them at all and so lines are always getting cutoff in the pdf when it runs out of space. Indeed. Maybe your particular case isn't covered by the implementation yet, but normally FOP supports Unicode compliant line- breaking. IOW: if Unicode says no break, then FOP says no break, unless XSL- FO specific properties force it otherwise. If the rules for the languages you are using are covered by FOP's implementation of UAX#14, then the only valid ways around it are: a) pre-process the text, and insert characters that generate legal break-opportunities b) use the XSL-FO wrap-option=wrap property on the surrounding fo:block Unfortunately, last I checked, b) was either unimplemented or broken in FOP 0.93 and the Trunk, so a) would be the only solution... but before you start working on that, I hope someone chimes in who can confirm with certainty that it is not merely a limitation in FOP's current implementation. Cheers Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Now you can see trouble before he arrives http://newlivehotmail.com/?ocid=TXT_TAGHM_migration_HM_viral_protection_0507 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
