Re: break-before in list-item-body: missing following content
Hello Vincent, I think my testcase can be related with an existing bugzilla entry: https://issues.apache.org/bugzilla/show_bug.cgi?id=43416 Perhap's I should attach this file to the entry ? Patrice - Mail Original - De: Vincent Hennebert [EMAIL PROTECTED] À: fop-users@xmlgraphics.apache.org Envoyé: Lundi 1 Septembre 2008 17:11:19 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: break-before in list-item-body: missing following content Hi Patrice, patrice rosnet wrote: Hello I have a problem with a break-before in a list-item-body: content following this attribute inside the list-item-body has disappeared continue2/2 end It’s a bug in the code dealing with lists (for curious people: the element list for the content of the list-item-body is split at each forced break, but the list only retrieves the first part). Hopefully the list code will be revamped in the next release, but meanwhile you better use tables. You can achieve the same result with something like the following: fo:table width=100% table-layout=fixed fo:table-column column-width=3cm/ fo:table-column column-width=100% - 3cm/ fo:table-body fo:table-row fo:table-cellfo:blocklabel/fo:block/fo:table-cell fo:table-cell fo:block fo:blockbody1/fo:block fo:blockcontinue1/2/fo:block fo:block break-before=columncontinue2/2/fo:block fo:blockend/fo:block /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table HTH, Vincent - 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: I need fo:retrieve-table-marker example or how to implement continued label in FOP-95?
Andreas Delmelle a écrit : I've set up a simple test case and, going through the stack trace, I guess it could be a simple bug fix, something like a bad or insufficient test in TablePart.java Oh, rest assured, it's going to take a bit more thought and effort... ;-) Yes, I've seen late in the evening that implementing the context attributes as defined in the W3C recommendation is probably going to be a tough task. I've got a more serious question but I'll ask in another post. Thanks for the moral support ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Links in SVGs included into PDFs
Hi all, I am very new to fop, I'm really coming from docbook (which I'm relatively new to also ;-) ). I have a question regarding links (svg:a tags) in graphics included into fo documents via fo:external-graphic. When rendering to PDF, I don't seem to get the links. While googling around, I got the impression, that fop supports SVG links. Hoewver, I could not find a concrete working example from which to start. My question is: How do I get this to work? I know, this is a very general question but it's hard for me to be more specific since I'm so new to the subject. I would be very grateful for any pointer, stefan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fontforge says Type1 is restricted to ANSI Re: Type 1 font encoding problems?
I solved the problem by embedding a TrueType-Font that has the glyph (DejaVuSans). The Type1-font that I had wanted to use initially had been converted with fontforge from OTF, and when I converted it again, fontforge told me that Type1-fonts are restricted to ANSI. Converting the OTF font to TTF instead, and embedding that using FOP seems to work well. Joerg von Frantzius wrote: Hi, I can't get FOP to render #x25B6; correctly in PDF (see e.g. http://en.wikipedia.org/wiki/Unicode_Geometric_Shapes). It should show up in font Courier. I checked the PDF generated, and Courier is substituted with the Type 1 font CourierStd on my system, telling from Acrobat Reader properties for the PDF file. I verified using kfontview that indeed CourierStd has that glyph (in Unicode block Geometric Shapes). The font's encoding is reported as Ansi, though, and I guess that's where the problem is. In some related bug (https://issues.apache.org/bugzilla/show_bug.cgi?id=6237) it was recommended to use a Unicode user font. Now I wonder how I can get FOP to use or embed a Type 1 font with Unicode encoding? Bug https://issues.apache.org/bugzilla/show_bug.cgi?id=17828 lets me think that embedding a TrueType Font could solve the problem, as it seems TTF is treated as Unicode. Here is a simple self-contained example to show the glyph in question: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=only fo:region-body region-name=xsl-region-body margin=0.7in / fo:region-before region-name=xsl-region-before extent=0.7in / fo:region-after region-name=xsl-region-after extent=0.7in / /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=only fo:flow flow-name=xsl-region-body fo:blockThis should be a black arrow right/fo:block fo:block Courier: fo:inline font-family=Courier font-style=normal font-weight=normal#x25B6; /fo:inline /fo:block /fo:flow /fo:page-sequence /fo:root Thanks for any hints, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- artnology GmbH - Milastraße 4 - 10437 Berlin - Germany Geschäftsführer: Ekkehard Blome (CEO), Felix Kuschnick (CCO) Registergericht: Amtsgericht Berlin Charlottenburg HRB 76376 UST-Id. DE 217652550 begin:vcard fn;quoted-printable:J=C3=B6rg von Frantzius n;quoted-printable:von Frantzius;J=C3=B6rg org:artnology GmbH adr:;;Milastr. 4;Berlin;;10437;Germany email;internet:[EMAIL PROTECTED] title:Software Architect tel;work:+49 (30) 443 50 99 26 tel;fax:+49 (30) 443 50 99 99 x-mozilla-html:TRUE version:2.1 end:vcard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Links in SVGs included into PDFs
Links in SVG are supported but only to external destinations, i.e. external URLs. Support for internal destinations from SVG back into the parent FO document hasn't been implemented, yet. To implement this, I think a special PDFAElementBridge would be needed which is aware of the FO IDs and their location. This would have to be plugged into the PDFSVGHandler. Not sure how difficult this would be to implement, but it can't be that hard. Want to try? I can probably give you a few more pointers if you want. On 02.09.2008 11:02:48 Stefan Bund wrote: Hi all, I am very new to fop, I'm really coming from docbook (which I'm relatively new to also ;-) ). I have a question regarding links (svg:a tags) in graphics included into fo documents via fo:external-graphic. When rendering to PDF, I don't seem to get the links. While googling around, I got the impression, that fop supports SVG links. Hoewver, I could not find a concrete working example from which to start. My question is: How do I get this to work? I know, this is a very general question but it's hard for me to be more specific since I'm so new to the subject. I would be very grateful for any pointer, stefan. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
compatibility between fop 094, commons-logging 1.0.3, avalon-framework4.1.x
Hi I use fop 0.94 on a platform hosting - commons-logging 1.0.3 - avalon-framework4.1.x As fop 0.94 uses the following library, I would like to make sure there will not by compatibility problems - commons-logging 1.0.4 - avalon-framework4.2.0 Thank you in advance Pascal
Re: compatibility between fop 094, commons-logging 1.0.3, avalon-framework4.1.x
Both should be fully backwards-compatible. It should be safe to upgrade to the newer versions. 0.94 will probably also work with the old versions of these two libraries (I didn't test, though). On 02.09.2008 15:15:29 Pascal P wrote: Hi I use fop 0.94 on a platform hosting - commons-logging 1.0.3 - avalon-framework4.1.x As fop 0.94 uses the following library, I would like to make sure there will not by compatibility problems - commons-logging 1.0.4 - avalon-framework4.2.0 Thank you in advance Pascal Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Links in SVGs included into PDFs
Jeremias Maerki [EMAIL PROTECTED] writes: Links in SVG are supported but only to external destinations, i.e. external URLs. Support for internal destinations from SVG back into the parent FO document hasn't been implemented, yet. I had problems even with internal URL's until I found out I wasn't running the current stable of fop (which I had installed into my home dir) but the system version (which is ancient) ... duh ... To implement this, I think a special PDFAElementBridge would be needed which is aware of the FO IDs and their location. This would have to be plugged into the PDFSVGHandler. Not sure how difficult this would be to implement, but it can't be that hard. Want to try? I can probably give you a few more pointers if you want. I'd love to try but at the moment I shouldn't take the time for this. However, a workflow which allows to produce nice PDF's with embedded graphics which support links is exactly what I need at the moment. So maybe I will take a look .. I'm crazy enough to be interested ;-). I'll check out the source and try to grok something :-) The Problem is, that I really have no idea, how FO really works. On the other hand, I probably don't need to. Since external URL's are already implemented, it really should not be very difficult since internal links are also implemented albeit not for SVG. So I probably could take that code and somehow adapt it to work with SVG's ... at least I could try. So if you can give me a pointer, I'll listen. I can't promise to be able to contribute something though. stefan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: # characters for Base-14 fonts
On Sep 1, 2008, at 01:06, Ryan Lortie wrote: snip / When you don't use character then FOP makes its decision about the height of the line based solely on the first listed font family (ignoring all of the others, irrespective of if they are used for font substitution in that line). Having taken a quick, closer look at the related code, it goes in this direction indeed. Technically, the story is that, without fo:character or fo:inline a combined text-area is generated for each separate 'word' (in the sense of: uninterrupted sequence of non-white-space characters, regardless of whether they can be rendered in the same font). Those areas are currently all based on a single alignment-context (which seems to correspond to the first font-family in the list; this explains why we get a different result when putting the Symbol font first). AFAICT, it does not seem like a real tough problem to solve... I do seem to remember Max pointing out this issue at some time while implementing font-selection (?) If we place the characters in an fo:inline or an fo:character, the only big difference is that a new alignment-context is created automatically, which later on triggers correct baseline alignment of the two pieces. If you want, you can open a Bugzilla(*) entry for this, so that the issue is tracked. Thanks Andreas (*) https://issues.apache.org/bugzilla - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Links in SVGs included into PDFs
Replying to my own post since I have gotten a little bit further. Implementing internal links seems to be more complicated than I had expected. As far as I understand, internal links are resolved within the area tree before the tree is rendered. An (external) SVG image resource howvever is only parsed at the render stage. However, I could get further if I could access the AreaTreeManager (and thereby its IdTracker) from the PDFANode. However, I could not find any way to get there (I have the PDFGraphics2D object and I can get the PDFDocument or RendererContext but I could not find a reference to the AreaTreeManager anywhere). I know, this is probably not the correct way to do this (I would need to somehow create a LinkResolver for every link in the SVG file while creating the area tree but at the moment that is way over my head). I hope, I can resolve the id's by just querying the IdTracker. This will possibly only work when the id is referenced from some other place, but it would be a start. Any pointer how to proceed? And maybe I got everything completely wrong. If so, could someone please set me right? stefan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I need fo:retrieve-table-marker example or how to implement continued label in FOP-95?
It's nice that some Europeans are willing to work for free! What incentives are you getting anyways? -Gennady Jean-François El Fouly wrote: Andreas Delmelle a écrit : I've set up a simple test case and, going through the stack trace, I guess it could be a simple bug fix, something like a bad or insufficient test in TablePart.java Oh, rest assured, it's going to take a bit more thought and effort... ;-) Yes, I've seen late in the evening that implementing the context attributes as defined in the W3C recommendation is probably going to be a tough task. I've got a more serious question but I'll ask in another post. Thanks for the moral support ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/I-need-fo%3Aretrieve-table-marker-example-or-how-to-implement-continued-label-in-FOP-95--tp19150429p19279169.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error when using XSL with French Characters
My Friends, Fop-0.95 My style sheet has been working perfectly. However, the user submitted some text in French. In the text was a letter e with an accent above it. That character caused the following error: Invalid byte 1 of 1-byte UTF-8 sequence. My .xml looks fine. The e with the accent above it is perfect. First line in my XML: ?xml version=1.0 encoding=UTF-8? Here is the first line of my XSL: ?xml version=1.0 encoding=UTF-8? I am confused over why the UTF-8 for the XML understands the character but the UTF-8 in the XSL does not? I found an article that suggests that the problem would be solved with: ?xml version=1.0 encoding=8859-1? Would this be a viable/recommended solution? Do you have a better idea? Jeff Steffanina FOSSE Development, Bethesda, MD (301)380-2047 [EMAIL PROTECTED] This communication contains information from Marriott International, Inc. that may be confidential. Except for personal use by the intended recipient, or as expressly authorized by the sender, any person who receives this information is prohibited from disclosing, copying, distributing, and/or using it. If you have received this communication in error, please immediately delete it and all copies, and promptly notify the sender. Nothing in this communication is intended as an electronic signature under applicable law.
RE: Error when using XSL with French Characters
I am suspicious that although you declare the XML file as being in UTF-8 it actually isn't. How do you produce the XML file? Manuel _ From: Steffanina, Jeff [mailto:[EMAIL PROTECTED] Sent: Wednesday, 3 September 2008 10:23 AM To: fop-users@xmlgraphics.apache.org Subject: Error when using XSL with French Characters My Friends, Fop-0.95 My style sheet has been working perfectly. However, the user submitted some text in French. In the text was a letter e with an accent above it. That character caused the following error: Invalid byte 1 of 1-byte UTF-8 sequence. My .xml looks fine. The e with the accent above it is perfect. First line in my XML: ?xml version=1.0 encoding=UTF-8? Here is the first line of my XSL: ?xml version=1.0 encoding=UTF-8? I am confused over why the UTF-8 for the XML understands the character but the UTF-8 in the XSL does not? I found an article that suggests that the problem would be solved with: ?xml version=1.0 encoding=8859-1? Would this be a viable/recommended solution? Do you have a better idea? Jeff Steffanina FOSSE Development, Bethesda, MD (301)380-2047 [EMAIL PROTECTED] This communication contains information from Marriott International, Inc. that may be confidential. Except for personal use by the intended recipient, or as expressly authorized by the sender, any person who receives this information is prohibited from disclosing, copying, distributing, and/or using it. If you have received this communication in error, please immediately delete it and all copies, and promptly notify the sender. Nothing in this communication is intended as an electronic signature under applicable law.
