DO NOT REPLY [Bug 14039] New: - Last fo:page-number-citation not printed with break-before=page.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14039 Last fo:page-number-citation not printed with break-before=page. Summary: Last fo:page-number-citation not printed with break- before=page. Product: Fop Version: 0.20.4 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The fo:page-number-citation has a bug when used with break-before=page. In the following example, the last fo:page-number-citation is never printed. This is not linked to the size of the document or the number of page number. It is fixed when replacing break-before=page by break-after=page. ?xml version=1.0 encoding=ASCII? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-right=2.5cm margin-left=2.5cm margin- bottom=2cm margin-top=1cm page-width=21cm page-height=29.7cm master- name=simple fo:region-body margin-top=1.5cm/ fo:region-before extent=3cm/ fo:region-after extent=1.5cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence initial-page-number=1 master-reference=simple fo:static-content flow-name=xsl-region-before /fo:static-content fo:flow flow-name=xsl-region-body fo:blockfo:basic-link internal-destination=doc1 color=blueDocument 1/fo:basic-linkfo:page-number-citation ref-id=doc1//fo:block fo:blockfo:basic-link internal-destination=doc2 color=blueDocument 2/fo:basic-linkfo:page-number-citation ref-id=doc2//fo:block fo:blockfo:basic-link internal-destination=doc3 color=blueDocument 3/fo:basic-linkfo:page-number-citation ref-id=doc3//fo:block fo:blockfo:basic-link internal-destination=doc4 color=blueDocument 4/fo:basic-linkfo:page-number-citation ref-id=doc4//fo:block fo:blockfo:basic-link internal-destination=doc5 color=blueDocument 5/fo:basic-linkfo:page-number-citation ref-id=doc5//fo:block fo:block break-before=page id=doc1Document 1/fo:block fo:block break-before=page id=doc2Document 2/fo:block fo:block break-before=page id=doc3Document 3/fo:block fo:block break-before=page id=doc4Document 4/fo:block fo:block break-before=page id=doc5Document 5/fo:block /fo:flow /fo:page-sequence /fo:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fopping 1-12 to Jan-Dec
First, a thank youz to Jarno, his code worked. I managed to figure out I needed to add number() so that October (10) did not come out as January. Jeni Tennison's code worked too. XSLT Goddess Jeni Tennison emailed me: [updated for my XML DB] [Kay's pg 95 code], as it describes, that code will only work if you're using XSLT 1.1 (or XSLT 2.0 actually) because it silently converts a result tree fragment into a node tree. You will have to use an extension node-set() function, e.g.: xsl:variable name=months-rtf January/February/March/April/May/June/July/ August/September/October/November/December/ /xsl:variable xsl:variable name=months select=xalan:nodeset($months-rtf)/* / xsl:template match=Product/ProductStatus xsl:variable name=mmselect=substring(@statusDateTime,6,2) / xsl:value-of select=name($months[position()=$mm])/ xsl:text /xsl:text xsl:value-of select=number(substring(@statusDateTime,9,2))/ xsl:text, /xsl:text xsl:value-of select=substring(@statusDateTime, 1, 4)/ /xsl:template Result: October 18, 2002 I've posted my thesis that FOP error message reporting should not use dump tracebacks. Now I'd like to say: Please upgrade the Xalan in FOP to be the latest, because it includes EXSLT. Not having EXSLT available during a FOP is like not having CPAN available for PERL. Wheel... http://xml.apache.org/xalan-j/index.html # # Xalan-Java version 2.4.0 also introduces # support for EXSLT extensions. Although I am running FOP from the command-line during development, production use is on the TomCat server I setup. That uses FopServlet.java to run the FOP. I don't know Java to rewrite FopServlet to run a new Xalan (to have EXSLT) then a pure FOP, and so far the only recommendation from this list on plugging a new Xalan into FOP is Don't go there. As for EXSLT, the sooner it's in FOP the better. It's going to happen anyway, right? How about now? (Java style) Regular expressions, etc., in EXSLT. Not to mention the 1-12 month name conversion. Common tasks, needed again and again. We're not writing books here, but processing financial reports on companies into PDFs of several pages from an XML delivery from the clients. EXSLT.org # #Modules # #Dates and Times # #Dynamic # #Common # #Functions # #Math # #Regular Expressions # #Sets # #Strings - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
justifying text
I'm writing a text into a fo:block. There's too much text, with many paragraphs. The problem is that I dont want that the last line of a paragraph was justified like is being: (suppose that the symbol "|" is the left rigth margin.) NOW |this is the text of the document| |this is the text of the document||and say goodbye| | | |this is the text of the document| |this is the text of the document||and say goodbye| | ||this is the text of the document| |andsaygoodbye | I WANT: |this is the text of the document| |this is the text of the document||and saygoodbye | | | |this is the text of the document| |this is the text of the document||and saygoodbye | | ||this is the text of the document| |andsay goodbye | the text is written into a fo:block like: fo:block text-align='justify' text-align-last='start' line-height='12pt' font-size='8pt' space-before.optimum='1.5pt' space-after.optimum='1.5pt' keep-together='always' color='gray' fo:inline white-space-collapse='false'this is the text of the document this is the text of the document andsaygoodbye this is the text of the document this is the text of the document andsaygoodbye this is the text of the document andsaygoodbye/fo:inline/fo:block Any idea will be welcome... Sergio.
Re: justifying text
Don't use text-align=justify Try text-align=left Sergio shernand@ipsolucTo: [EMAIL PROTECTED] iones.com cc: Subject: justifying text 10/29/2002 11:42 AM Please respond to fop-dev I'm writing a text into a fo:block. There's too much text, with many paragraphs. The problem is that I dont want that the last line of a paragraph was justified like is being: (suppose that the symbol | is the left rigth margin.) NOW |this is the text of the document| |this is the text of the document| |and say goodbye| | | |this is the text of the document| |this is the text of the document| |and say goodbye| | | |this is the text of the document| |and say goodbye| I WANT: |this is the text of the document| |this is the text of the document| |and say goodbye| | | |this is the text of the document| |this is the text of the document| |and say goodbye| | | |this is the text of the document| |and say goodbye| the text is written into a fo:block like: fo:block text-align='justify' text-align-last='start' line-height='12pt' font-size='8pt' space-before.optimum='1.5pt' space-after.optimum='1.5pt' keep-together='always' color='gray' fo:inline white-space-collapse='false'this is the text of the document this is the text of the document and say goodbye this is the text of the document this is the text of the document and say goodbye this is the text of the document and say goodbye/fo:inline/fo:block Any idea will be welcome... Sergio. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: justifying text
The problem, is that i'm rendering the pdf dinamicaly. I can't modify this text, because it's returned by a field of a sql server database. In other case, there will be no problem. Sergio. - Original Message - From: Patrick Dean Rusk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 6:09 PM Subject: RE: justifying text Sergio, Is there any chance that you're trying to put the returns directly in the text, rather than delineating each paragraph as its own block? That might cause the problems you see. Patrick Rusk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: justifying text
Sergio wrote: I'm writing a text into a fo:block. There's too much text, with many paragraphs. There is no notion of paragraph is xsl, and your fo snippet looks like exactly 1 block area, so it has only 1 last line area. If you belive you have many paragraphs, you have to mark them up using fo:block tag. Then having many blocks you can align last line area within each one. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14057] New: - [PATCH] implement text-transform
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14057. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14057 [PATCH] implement text-transform Summary: [PATCH] implement text-transform Product: Fop Version: 0.20.4 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This patch implements the text-transform property. It correctly handles every English-language nuance that I have been able to think of. It adds fields to each FOText object that point to previous next FOText objects within the same Block, so that the text in related FOText objects can be considered for needed context. It then transforms the text as part of the FOText Constructor. Some of the fields and methods added may be useful for other parts of FOP as well. This code assumes that words do not span multiple blocks. Caveat: I cannot think of any, but if there are cases (now or in the future) where FOText objects do not have ancestor Block objects, text-transform will not be able to consider other FOText objects for context. This can be fixed by storing the Block-like ancestor instead. Caveat: The definition of word for purposes of this property is ambiguous. It may need to be tweaked over time, especially for scripts other than Latin. I have tried to build an infrastructure that will allow such modifications to be pretty easily implemented. Victor Mote ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14057] - [PATCH] implement text-transform
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14057. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14057 [PATCH] implement text-transform --- Additional Comments From [EMAIL PROTECTED] 2002-10-29 18:37 --- Created an attachment (id=3651) xsl-fo document for testing features of text-transform - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Background and border information in the area tree
Hi! I was trying to figure out why FOP always prints a solid line (in PDF) even if I wrote DOTTED or DASHED in the xslfo. I looked in the area tree output from FOP but I cannot find any information in this file about background colours, lines, borders etc. Where are these informations stored? -- Morten Isaksen [EMAIL PROTECTED] - http://www.aub.dk/~misak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14013] - Performance tuning
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14013. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14013 Performance tuning --- Additional Comments From [EMAIL PROTECTED] 2002-10-30 07:23 --- Created an attachment (id=3658) performanceTuning.patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14013] - Performance tuning
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14013. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14013 Performance tuning [EMAIL PROTECTED] changed: What|Removed |Added URL|http://nohardcore.tripod.com| |/fop/performanceTuning.zip | - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Background and border information in the area tree
Hello, According to what a previous post reads, FOP handles only solid borders : http://marc.theaimsgroup.com/?l=fop-userm=102948462018944w=2 Regards -- Sébastien Foucault [EMAIL PROTECTED] Morten Isaksen [EMAIL PROTECTED] 30/10/2002 02:15 Please respond to fop-dev To: [EMAIL PROTECTED] cc: Subject:Background and border information in the area tree Hi! I was trying to figure out why FOP always prints a solid line (in PDF) even if I wrote DOTTED or DASHED in the xslfo. I looked in the area tree output from FOP but I cannot find any information in this file about background colours, lines, borders etc. Where are these informations stored? -- Morten Isaksen [EMAIL PROTECTED] - http://www.aub.dk/~misak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
