Re: BIDI reordering routine
Rodolfo M. Raya wrote: Does anybody have a routine to reorder BIDI text? You can use java.text.Bidi from jdk1.4 and sun.awt.font.Bidi in jdk1.2/1.3, they provide basic BIDI facilities. The problem is that java.text.Bidi is since jdk1.4 and sun.awt.font.Bidi does not exist in jdk1.4. So I suggest you not to use BIDI implementation directly, but indirectly through java.awt.font.TextLayout and so on. I'm writing code to visually reorder BIDI text before generating XSL-FO files, but I don't want to reinvent the wheel. btw, that's not the solution actually. This way you do provide visually reordered text to FOP, but FOP as being BIDI-unaware will still layout text ltr-tb, so you'll end with rtl-bt layout: logical: RAC A SI SIHT visual: THIS IS A CAR One line is ok, but once line break occurs: IS A CAR THIS The solution is to make FOP BIDI-aware itself. I have experimented with it and actually I have BIDI-aware version of FOP 0.20.5rc or earlier, but the implementation is neither fast nor clean from design point of view, so I decided not to commit it to cvs, but instead to implement it in FOP1.0dev in a better way. You are welcome to help us with this. Lack of free time, unfortunately, you know, too many day works last time : -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logo Submission - 4 logos for Contest
Michael Schnuerle wrote: I've got 4 logos to submit to the logo contest. I found out about it last week, worked on them this weekend, and read today the deadline was Friday. Regardless, I hope they can be consided in the voting. They are all in .gif format. I have them in SVG, but each has a non-vector element that made their size too large (I can convert it later if needed). Added to the list. Thanks, Michael! Don't worry about deadline, we are going to prolong the contest for so some time probably till final 0.20.5 release. -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BIDI reordering routine
On Tue, 2003-03-04 at 08:20, Oleg Tkachenko wrote: Rodolfo M. Raya wrote: Does anybody have a routine to reorder BIDI text? You can use java.text.Bidi from jdk1.4 and sun.awt.font.Bidi in jdk1.2/1.3, they provide basic BIDI facilities. The problem is that java.text.Bidi is since jdk1.4 and sun.awt.font.Bidi does not exist in jdk1.4. So I suggest you not to use BIDI implementation directly, but indirectly through java.awt.font.TextLayout and so on. I can't use Sun's Bidi class directly because some users will be running jdk 1.3. I'll try with java.awt.font.TextLayout. I'm writing code to visually reorder BIDI text before generating XSL-FO files, but I don't want to reinvent the wheel. btw, that's not the solution actually. This way you do provide visually reordered text to FOP, but FOP as being BIDI-unaware will still layout text ltr-tb, so you'll end with rtl-bt layout: logical: RAC A SI SIHT visual: THIS IS A CAR One line is ok, but once line break occurs: IS A CAR THIS The solution is to make FOP BIDI-aware itself. I have experimented with it and actually I have BIDI-aware version of FOP 0.20.5rc or earlier, but the implementation is neither fast nor clean from design point of view, so I decided not to commit it to cvs, but instead to implement it in FOP1.0dev in a better way. You are welcome to help us with this. Lack of free time, unfortunately, you know, too many day works last time : Can you send me the code? I can try to clean it. My deadline is March 7th, so I have 2 days to play with it. Thanks and regards, Rodolfo -- Rodolfo M. Raya [EMAIL PROTECTED] Heartsome Holdings Pte. Ltd. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: keep-together / blind tables
Let's try this code (I did not test it): substitute: fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row through: xsl:for-each select=paragraph fo:table-row fo:table-cell fo:blockxsl:value-of select=././fo:block /fo:table-cell /fo:table-row /xsl:for-each -Ursprüngliche Nachricht- Von: Matthias Brunner [SMTP:[EMAIL PROTECTED] Gesendet am: Montag, 3. März 2003 19:25 An: [EMAIL PROTECTED] Betreff: keep-together / blind tables Hello, I know this is a FAQ but I did not find anything appropriate to my specific problem. I have paragraphs with a heading and, of course, I do not want the heading to be left alone on one page with the paragraphs being on the next one. ---excerpt--- xsl:template match=paragraphs fo:table table-layout=fixed width=100% fo:table-column column-width=proportional-column-width(1)/ fo:table-body fo:table-row keep-with-next=always fo:table-cell xsl:apply-templates select=heading/ /fo:table-cell /fo:table-row fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template ---excerpt--- keep-with-next works, the heading is never left alone. But even if a paragraph is half a page in size it is not seperated any more thus leaving ugly blank spots on the pages. (strange ASCII art example attached below :) What can I do to allow the separation of this paragraph? Thanks in advance, Matthias Example: p1 heading/ paragraph content content content /paragraph EMPTY EMPTY EMPTY EMPTY --- p2 heading/ paragraph content content content content content content content /paragraph INSTEAD OF: p1 heading/ paragraph content content content /paragraph heading/ paragraph content content- --- p2 content content content content content /paragraph EMPTY EMPTY EMPTY EMPTY - 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: replacing default fonts
I don't see a problem with having the userconfig.xml in the WAR. It's pretty read-only in there and it's only a one-liner in your code. If you absolutely want to change the default font setup you should have a look at org.apache.fop.render.pdf.FontSetup.java. This is where the default fonts get registered for the PDF renderer. It uses precompiled fonts that are generated in the codegen task in build.xml. You could also build such Font classes using the same mechanism. That's how font support used to be years ago. :-) Anyway, I advise against it. On 03.03.2003 15:14:28 Enoch Root wrote: It's not terribly necessary, I'd like just to know if it's possible. And the reason, as I explained below, I would like to avoid user configurable stuff (i.e. userconfig.xml within WAR) as much as possible. --- Oleg Tkachenko [EMAIL PROTECTED] wrote: Enoch Root wrote: I'd like to know if it's possible to replace default fonts supplied with FOP so that I won't have to read userconfig.xml in the servlet and supply fonts with my application? Or is it possible to add just the missing glyphs for a specific language? I don't think it's easy feasible. Why do you need it? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FIGURE TOP PAGE PLACEMENT
On 03.03.2003 10:55:10 H. krishna wrote: Hai Everybody, 1. I need the placement of FIGURE TABLE is top of page only. how to define in the fo file. The fo:float is not implemented (fop-0.20.5rc2). I am already post this problem. I'm not sure I get you right, but you can specify fo:block break-before=page [..my stuff on top of the page..] This tells FOP to start a new page and new content is started from the top. 2. Move the below one line to above line. how to define in the fo file. For Example: FOP Means Formatting Object Processor (to) FOP Means Formatting Object Processor If your XSL-FO code looks like this: fo:blockFOP Means Formatting Object Processor/fo:block ...and the width available is sufficient you'll get what you want. You may have to make your font smaller or check if you've got something odd with you linefeed treatment. I hope that helps. If your problem persists you could post a little snippet of your XSL-FO code so we can have a look at it. It's difficult to help with so little information. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FIGURE TOP PAGE PLACEMENT
Dear Jeremias Maerki, Thanks for your mail. i am used linefeed-treatment=preserve this is correct (or) not. I'm not sure I get you right, but you can specify fo:block break-before=page [..my stuff on top of the page..] This tells FOP to start a new page and new content is started from the top. But the content and figure is goes to next page. I need the placement of figure only. Not the content. This is possible. Sorry, my language. Regards, H. Balakrishnan __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output
Well.
1. Which FOP version are you using?
I'm using the 0.20.5rc2 version of FOP, since I had some problem with the
markers with the last official release 0.20.4, which ere corrected in this
candidate.
[white-space-collapse=false].
2. Don't use this.
Yep, you're right ! This tag was outputing some stranges spaces ... !
3. Use text-align=justify text-align-last=justify
Didn't know about the text-align-last attribute ! Thanks ! :)
[fo:leader attributes]
4. Don't use this this way. It's probably best to leave
the defaults (min=0, opt=6pt, max=100%)
You're right again, I'm now using it into a table with the default values,
it's working great !
5. What's wrong with fo:page-number-citation ref-id={SOUSTHEME}/?
Right right right ! ... I'm sometime so complicated.
Also, it is usually more informative to post FO snippets
rather than XSLT snippets. The best way is to post a small,
self-contained FO document.
I'll send the FO output next time. Thanks for your answers, they were very
effective, once again !
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: FIGURE TOP PAGE PLACEMENT
On 04.03.2003 15:30:33 H. krishna wrote: Thanks for your mail. i am used linefeed-treatment=preserve this is correct (or) not. Depends on your input XML. If there are linefeeds in there, these could be responsible for the linefeed. Try experimenting a bit. Change linefeed-treatment etc. I'm not sure I get you right, but you can specify fo:block break-before=page [..my stuff on top of the page..] This tells FOP to start a new page and new content is started from the top. But the content and figure is goes to next page. I need the placement of figure only. Not the content. This is possible. I'm still not sure I know what you want to do. Maybe fo:block-container with absolute positioning could help. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: embedded problem
Hi, I'm using Adobe 5.0 -Type 1 font -previous is 0.20.4 font metrics-file=/nas/web/fonts/ITCGaraBold.xml kerning=yes embed-file=/nas/web/fonts/GAB_.PFB font-triplet name=AGaramondBD style=normal weight=normal/ /font fop log see attachment Thanks Lucian Opris -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 10:06 AM To: [EMAIL PROTECTED] Subject: Re: embedded problem - Which program do you use to open the PDF? Acrobat Reader? Which version? - Is the Garamond font a TrueType or a Type 1 font? - Previous version: do you refer to 0.20.4? - What does the font element in userconfig.xml for Garamond look like? - What's FOP's log when you generate the PDF? From 0.20.4 to 0.20.5 there have been changes in font support but they should be backwards-compatible. The only thing that comes to my mind is the filenames/URLs referencing the font files. Handling has changed a bit. On 04.03.2003 15:23:58 Lucian Opris wrote: I'm getting errors when I'm trying to open up a pdf created by fop-20.5rc cannot extract embedded Garamond font. It was fine in previous version. I'm using the same userconfig.xml. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: /nas/web/tmp/filexImriL [DEBUG] xslt stylesheet: /nas/web/clients/sndv/style/sndv_company_pdf_fop.xsl [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: /nas/web/clients/demo/docs/pdf/3850.pdf [DEBUG] OPTIONS [DEBUG] user configuration file: /nas/web/fonts/config-fonts.xml [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] base directory: file:/nas/web/tmp/ [INFO] FOP 0.20.5rc2 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [WARNING] Sum of fixed column widths 364250 greater than maximum specified IPD 362551 [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 80787 greater than maximum specified IPD 80537 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 76533 greater than maximum specified IPD 75785 [WARNING] Sum of fixed column widths 178582 greater than maximum specified IPD 164409 [INFO] [2] [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any [WARNING] Sum of fixed column widths 436251 greater than maximum specified IPD 428251 [INFO] [3] [INFO] [4] [INFO] [5] [INFO] [6] [INFO] [7] [INFO] [8] [INFO] [9] [INFO] [10] [INFO] [11] [INFO] [12] [INFO] [13] [INFO] [14] [INFO] [15] [ERROR] Error while creating area : Error while recovering Image Informations (file:/nas/web/charts/clients/6317/out/table/.gif) : /nas/web/charts/clients/6317/out/table/.gif (No such file or directory) [INFO] [16] [DEBUG] Last page-sequence produced 16
Re: FIGURE TOP PAGE PLACEMENT
Dear Jeremias Maerki, I am attached my fo file. I like my pdf file is: Page 1: Paragraph 1 Paragraph 2 Paragraph 3 Paragraph 4 Not finished Page 2: Figure 1 Paragraph 4 continued text Paragraph 5 Paragraph 6 Paragraph 7 Paragraph 8 Page 3: Figure 2 Paragraph 9 Paragraph 10 Paragraph 11 Paragraph 12 Regards, H. Balakrishnan --- Jeremias Maerki [EMAIL PROTECTED] wrote: On 04.03.2003 15:30:33 H. krishna wrote: Thanks for your mail. i am used linefeed-treatment=preserve this is correct (or) not. Depends on your input XML. If there are linefeeds in there, these could be responsible for the linefeed. Try experimenting a bit. Change linefeed-treatment etc. I'm not sure I get you right, but you can specify fo:block break-before=page [..my stuff on top of the page..] This tells FOP to start a new page and new content is started from the top. But the content and figure is goes to next page. I need the placement of figure only. Not the content. This is possible. I'm still not sure I know what you want to do. Maybe fo:block-container with absolute positioning could help. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/?xml version=1.0 encoding=iso-8859-1? !DOCTYPE root [ !ENTITY nl '#x2028;' ] fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:xlink=http://www.w3.org/1999/xlink; xmlns:svg=http://www.w3.org/2000/svg; fo:layout-master-set fo:simple-page-master master-name=firstPage page-height=9.44in page-width=6.31in margin-top=0.40in margin-bottom=.5in margin-left=0.8in margin-right=0.8in fo:region-before extent=10mm region-name=firstPage-before/ fo:region-body margin-bottom=20mm margin-top=10mm/ fo:region-after extent=10mm region-name=xsl-region-after/ /fo:simple-page-master fo:simple-page-master master-name=otherPageOdd page-height=9.44in page-width=6.31in margin-top=0.67in margin-bottom=1in margin-left=0.8in margin-right=0.8in fo:region-before extent=10mm region-name=otherPageOdd-before/ fo:region-body margin-bottom=20mm margin-top=10mm/ fo:region-after extent=10mm region-name=xsl-region-after/ /fo:simple-page-master fo:simple-page-master master-name=otherPageEven page-height=9.44in page-width=6.31in margin-top=0.67in margin-bottom=1in margin-left=0.8in margin-right=0.8in fo:region-before extent=10mm region-name=otherPageEven-before/ fo:region-body margin-bottom=20mm margin-top=10mm/ fo:region-after extent=10mm region-name=xsl-region-after/ /fo:simple-page-master fo:page-sequence-master master-name=contents fo:repeatable-page-master-alternatives fo:conditional-page-master-reference master-reference=firstPage page-position=first/ fo:conditional-page-master-reference master-reference=otherPageOdd odd-or-even=odd page-position=any/ fo:conditional-page-master-reference master-reference=otherPageEven odd-or-even=even page-position=any/ /fo:repeatable-page-master-alternatives /fo:page-sequence-master /fo:layout-master-set fo:page-sequence master-reference=contents fo:static-content flow-name=xsl-region-after fo:block text-align=center font-size=8pt font-family=serif line-height=10pt /fo:block /fo:static-content fo:static-content flow-name=otherPageOdd-before fo:block text-align=right fo:page-number font-size=8pt font-family=serif line-height=10pt/ /fo:block /fo:static-content fo:static-content flow-name=otherPageEven-before fo:block text-align=left fo:page-number font-size=8pt font-family=serif line-height=10pt/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block linefeed-treatment=preserve language=en country=GB hyphenate=true hyphenation-push-character-count=2 hyphenation-remain-character-count=2 white-space-treatment=preserve font-size=10pt font-family=serif line-height=12pt text-align=justifyIn Europe there are two main areas of particular biological value for sweet chestnut (fo:inline font-style=italicCastanea sativa/fo:inline Mill.) genetic resources, Turkey and Iberian Peninsula, each of them showing peculiar characteristics (Villani et al. 1999). These two areas, together with Italy, are the leading European chestnut producers and collectively account for 55.3% of the 24 tons world's annual production. In Portugal, chestnut has a relevant place at the socioeconomic level, reaching an annual fruit production of 2 tons (INE 1997)./fo:block fo:block language=en country=GB hyphenate=true hyphenation-push-character-count=2 hyphenation-remain-character-count=2 white-space-treatment=preserve text-indent=12pt font-size=10pt font-family=serif line-height=12pt
Best way to uppercase text
Hi ! I would like to now your point of view on this subject : I want to use the text-transform=uppercase attribute in a fo:block tag, but I saw in the output console that it was not implemented yet (using 0.20.5rc2), so I am wondering on the best way to implement it with xsl... I thought about using the xsl translate(string,string,string) function, but I don't think that's the best solution and I'm sure there is a better way to do that. And I don't want to put the uppercase value in my XML... Any ideas ? Thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Best way to uppercase text
Hello Simon You can use the XSLT translate-function to change to upper-case. (See example below) xsl:call-template name=toUpperCase xsl:with-param name=wort select=name/ /xsl:call-template !-- = -- !-- Translates a String to Upper-Case -- !-- = -- xsl:template name=toUpperCase xsl:param name=word/ xsl:variable name=small select='abcdefghijklmnopqrstuvwxyzäöüèé'/ xsl:variable name=CAPS select='ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÜÈÉ'/ xsl:value-of select=translate($word, $small, $CAPS)/ /xsl:template /xsl:stylesheet Greets, Helmut -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 4. März 2003 18:05 An: [EMAIL PROTECTED] Betreff: Best way to uppercase text Hi ! I would like to now your point of view on this subject : I want to use the text-transform=uppercase attribute in a fo:block tag, but I saw in the output console that it was not implemented yet (using 0.20.5rc2), so I am wondering on the best way to implement it with xsl... I thought about using the xsl translate(string,string,string) function, but I don't think that's the best solution and I'm sure there is a better way to do that. And I don't want to put the uppercase value in my XML... Any ideas ? Thanks, Simon - 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: embedded problem
Your stuff works here on Windows XP with the latest FOP and using Acrobat Reader 5.05. The only thing I changed was using Windows-style filenames and weight=bold because it's a bold font. But the latter is probably insignificant. Try using URLs instead of filenames: file:/nas/web/fonts/ITCGaraBold.xml and file:/nas/web/fonts/GAB_.PFB I hope the following (from your log file) has nothing to do with it. You're planning to supply the italic font as well, aren't you? [ERROR] unknown font GaramondBook,italic,normal so defaulted font to any On 04.03.2003 16:34:21 Lucian Opris wrote: Hi, I'm using Adobe 5.0 -Type 1 font -previous is 0.20.4 font metrics-file=/nas/web/fonts/ITCGaraBold.xml kerning=yes embed-file=/nas/web/fonts/GAB_.PFB font-triplet name=AGaramondBD style=normal weight=normal/ /font fop log see attachment Thanks Lucian Opris -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 10:06 AM To: [EMAIL PROTECTED] Subject: Re: embedded problem - Which program do you use to open the PDF? Acrobat Reader? Which version? - Is the Garamond font a TrueType or a Type 1 font? - Previous version: do you refer to 0.20.4? - What does the font element in userconfig.xml for Garamond look like? - What's FOP's log when you generate the PDF? From 0.20.4 to 0.20.5 there have been changes in font support but they should be backwards-compatible. The only thing that comes to my mind is the filenames/URLs referencing the font files. Handling has changed a bit. On 04.03.2003 15:23:58 Lucian Opris wrote: I'm getting errors when I'm trying to open up a pdf created by fop-20.5rc cannot extract embedded Garamond font. It was fine in previous version. I'm using the same userconfig.xml. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FIGURE TOP PAGE PLACEMENT
Hmm, looks like you really need fo:float for this, which isn't implemented. You probably need to find a different layout. What you can do is counting lines and sort of do the page-breaks yourself. That has been discussed before on this list but it's difficult, pretty hacky and does not guarantee success. On 04.03.2003 16:45:46 H. krishna wrote: I am attached my fo file. I like my pdf file is: Page 1: Paragraph 1 Paragraph 2 Paragraph 3 Paragraph 4 Not finished Page 2: Figure 1 Paragraph 4 continued text Paragraph 5 Paragraph 6 Paragraph 7 Paragraph 8 Page 3: Figure 2 Paragraph 9 Paragraph 10 Paragraph 11 Paragraph 12 Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FOP output to TIFF
Thanks for the reply Oleg, Multithreaded access isn't a requirement, so we are in the clear there. The requirements are simple: 1. TIFFs must use comp group 3x or greater 2. Must be able to set (or even hardcode) the width and height. 3. Must be able to split each page of the XSL-FO doc into separate TIFF files. That's it. I've tried: 1. XSL-FO to SVG to TIFF using FOP and Batik. Meets requirements 2 and 3 nicely but not 1. The generated TIFF files are more than two meg at the required width and height. 2. XSL-FO to TIFF using your TIFFRenderer. Meets requirement 1, though still getting black backgrounds. Using Photoshop and QuickTime to view the output. This might be an easy thing to reverse if I knew which section of the code needed changing. If that were resolved, I would still need a solution for requirements 2 and 3. 3. XSL-FO to SVG to TIFF using FOP and Batik hacked to use your TIFFImageEncoder. Was really hoping this would get me the compression capabilities (requirement 1) while retaining the ability to do requirements 2 and 3. Unfortunately, it didn't work. It can generate uncompressed TIFFs just fine, but trying any compression generates invalid TIFF files about 2k in size. At this point, I'm not sure what direction to go next. It seems like your code is the simplest. If we could work out a solution between the two of us, I would be more than happy to code it up and contribute the code. Best regards, David Oleg Tkachenko olegt () multiconn ! com wrote: Hello! David Blevins david.blevins () visi ! com wrote: Now I have my first question, so here goes. What is the recommended approach to generate a TIFF output: using the SVGRenderer then transcoding to TIFF with batik; using the TIFFRenderer written by Oleg? Hard question. TIFFRenderer has some flaws: it is not thread-safe, because AWTRenderer isn't. Another its problem is that all generated page images are held in memory. Both issues I hope will be fixed in FOP 1.0dev. So may be SVGRenderer is a prefered approach at the moment. The TIFFRenderer works, however the outputted TIFF is white text on black background (should be the other way around). Maybe there is something I need to configure correctly. Well, which TIFF viewer are you using? AFAIK, there is a great mess amongst TIFF viewers what is white and what is black in b/w FAX compressed images, e.g. consider given black-and-white TIFF image, Adobe Photoshop and Windows Imaging will show it differently black on white or white on black. TIFFRenderer uses JAI encoder, which seems to be agree with Adobe in this question, so I always rely on Photoshop and Alternatiff plugin and never got inverted image. Actually I've been thinking about introducing such a parameter to TIFFRenderer to allow control over that. Ok, granted, will try this week. There also doesn't seem to any new versions of the TIFFRenderer. The latest I can find is 0.9 from May last year. Is this there an updated, unreleased version somewhere? Well, I just don't see how can I make it better, it's quite simple wrapper, which heavily rely on JAI encoder and AWTRenderer. Now, when I'm FOP committer I'd better be focused on how to make FOP itself better, TIFFRenderer will benefit from it also. -- Oleg Tkachenko Multiconn Technologies, Israel - 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: fo:leader weird output (again) ;o)
Simon,
I have found good success with using a table for my XSL-FO table of contents
output. It makes lining up the leader lines and page numbers much easier. It
is not wholly elegant, but it works great.
Mark Dudley
Xerox Corporation
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: fo:leader weird output (again) ;o)
I come again on this problem.
J.Pietschmann's advices helped me to use fo:leader (and the
page-number-citation) well,
but there is still a problem on using a non-proportionnal-font (Helvetica
here) with the fo:leader tag.
Here's an example of the output :
http://www.tatouage.fr/temp/fop_user_example.gif
Again, any ideas on a way to resolve this problem would be greatly
appreciated.
Please note that I don't want to use a proportionnal (like Courier) font
in my Table of Content, cause I have some graphical obligation.
Many thanks,
Simon
Well.
1. Which FOP version are you using?
I'm using the 0.20.5rc2 version of FOP, since I had some problem with the
markers with the last official release 0.20.4, which ere corrected in this
candidate.
[white-space-collapse=false].
2. Don't use this.
Yep, you're right ! This tag was outputing some stranges spaces ... !
3. Use text-align=justify text-align-last=justify
Didn't know about the text-align-last attribute ! Thanks ! :)
[fo:leader attributes]
4. Don't use this this way. It's probably best to leave
the defaults (min=0, opt=6pt, max=100%)
You're right again, I'm now using it into a table with the default values,
it's working great !
5. What's wrong with fo:page-number-citation ref-id={SOUSTHEME}/?
Right right right ! ... I'm sometime so complicated.
Also, it is usually more informative to post FO snippets
rather than XSLT snippets. The best way is to post a small,
self-contained FO document.
I'll send the FO output next time. Thanks for your answers, they were very
effective, once again !
Simon
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Réf. : AW: Best way to uppercase text
Thanks for your help Helmut. I haven't find better way to do it ! Cheers, Simon Hello Simon You can use the XSLT translate-function to change to upper-case. (See example below) xsl:call-template name=toUpperCase xsl:with-param name=wort select=name/ /xsl:call-template !-- = -- !-- Translates a String to Upper-Case -- !-- = -- xsl:template name=toUpperCase xsl:param name=word/ xsl:variable name=small select='abcdefghijklmnopqrstuvwxyzäöüèé'/ xsl:variable name=CAPS select='ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÜÈÉ'/ xsl:value-of select=translate($word, $small, $CAPS)/ /xsl:template /xsl:stylesheet Greets, Helmut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FOP output to TIFF
Title: RE: FOP output to TIFF David: I ran into many of the same issues you did rendering to TIFF. I used Oleg's TiffRenderer: The Black and White thing is really a Windows imaging issue. I got around this by using Alternatiff browser plug-in, or viewing my TIFF's on a non-windows based machine. (in my case a solaris box - image tool). I could never solve your issue 3, if you get an answer please let me know. I would be willing to help as much as I can. Rob -Original Message- From: David Blevins [mailto:[EMAIL PROTECTED]] Sent: March 4, 2003 1:46 PM To: [EMAIL PROTECTED] Subject: RE: FOP output to TIFF Thanks for the reply Oleg, Multithreaded access isn't a requirement, so we are in the clear there. The requirements are simple: 1. TIFFs must use comp group 3x or greater 2. Must be able to set (or even hardcode) the width and height. 3. Must be able to split each page of the XSL-FO doc into separate TIFF files. That's it. I've tried: 1. XSL-FO to SVG to TIFF using FOP and Batik. Meets requirements 2 and 3 nicely but not 1. The generated TIFF files are more than two meg at the required width and height. 2. XSL-FO to TIFF using your TIFFRenderer. Meets requirement 1, though still getting black backgrounds. Using Photoshop and QuickTime to view the output. This might be an easy thing to reverse if I knew which section of the code needed changing. If that were resolved, I would still need a solution for requirements 2 and 3. 3. XSL-FO to SVG to TIFF using FOP and Batik hacked to use your TIFFImageEncoder. Was really hoping this would get me the compression capabilities (requirement 1) while retaining the ability to do requirements 2 and 3. Unfortunately, it didn't work. It can generate uncompressed TIFFs just fine, but trying any compression generates invalid TIFF files about 2k in size. At this point, I'm not sure what direction to go next. It seems like your code is the simplest. If we could work out a solution between the two of us, I would be more than happy to code it up and contribute the code. Best regards, David Oleg Tkachenko olegt () multiconn ! com wrote: Hello! David Blevins david.blevins () visi ! com wrote: Now I have my first question, so here goes. What is the recommended approach to generate a TIFF output: using the SVGRenderer then transcoding to TIFF with batik; using the TIFFRenderer written by Oleg? Hard question. TIFFRenderer has some flaws: it is not thread-safe, because AWTRenderer isn't. Another its problem is that all generated page images are held in memory. Both issues I hope will be fixed in FOP 1.0dev. So may be SVGRenderer is a prefered approach at the moment. The TIFFRenderer works, however the outputted TIFF is white text on black background (should be the other way around). Maybe there is something I need to configure correctly. Well, which TIFF viewer are you using? AFAIK, there is a great mess amongst TIFF viewers what is white and what is black in b/w FAX compressed images, e.g. consider given black-and-white TIFF image, Adobe Photoshop and Windows Imaging will show it differently black on white or white on black. TIFFRenderer uses JAI encoder, which seems to be agree with Adobe in this question, so I always rely on Photoshop and Alternatiff plugin and never got inverted image. Actually I've been thinking about introducing such a parameter to TIFFRenderer to allow control over that. Ok, granted, will try this week. There also doesn't seem to any new versions of the TIFFRenderer. The latest I can find is 0.9 from May last year. Is this there an updated, unreleased version somewhere? Well, I just don't see how can I make it better, it's quite simple wrapper, which heavily rely on JAI encoder and AWTRenderer. Now, when I'm FOP committer I'd better be focused on how to make FOP itself better, TIFFRenderer will benefit from it also. -- Oleg Tkachenko Multiconn Technologies, Israel - 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 output to TIFF
Title: Message Thanks for the feedback. Unfortunately, the black vs. white things is not up to my interpretation. This is part of an already existing and heavily used document archival application (written in VB). So it's too late to change requirements. What workaround did you use for number 3? Thanks, David -Original Message-From: Rob Stote [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 12:23 PMTo: '[EMAIL PROTECTED]'Subject: RE: FOP output to TIFF David: I ran into many of the same issues you did rendering to TIFF. I used Oleg's TiffRenderer: The Black and White thing is really a Windows imaging issue. I got around this by using Alternatiff browser plug-in, or viewing my TIFF's on a non-windows based machine. (in my case a solaris box - image tool). I could never solve your issue 3, if you get an answer please let me know. I would be willing to help as much as I can. Rob -Original Message- From: David Blevins [mailto:[EMAIL PROTECTED]] Sent: March 4, 2003 1:46 PM To: [EMAIL PROTECTED] Subject: RE: FOP output to TIFF Thanks for the reply Oleg, Multithreaded access isn't a requirement, so we are in the clear there. The requirements are simple: 1. TIFFs must use comp group 3x or greater 2. Must be able to set (or even hardcode) the width and height. 3. Must be able to split each "page" of the XSL-FO doc into separate TIFF files. That's it. I've tried: 1. XSL-FO to SVG to TIFF using FOP and Batik. Meets requirements 2 and 3 nicely but not 1. The generated TIFF files are more than two meg at the required width and height. 2. XSL-FO to TIFF using your TIFFRenderer. Meets requirement 1, though still getting black backgrounds. Using Photoshop and QuickTime to view the output. This might be an easy thing to reverse if I knew which section of the code needed changing. If that were resolved, I would still need a solution for requirements 2 and 3. 3. XSL-FO to SVG to TIFF using FOP and Batik hacked to use your TIFFImageEncoder. Was really hoping this would get me the compression capabilities (requirement 1) while retaining the ability to do requirements 2 and 3. Unfortunately, it didn't work. It can generate uncompressed TIFFs just fine, but trying any compression generates invalid TIFF files about 2k in size. At this point, I'm not sure what direction to go next. It seems like your code is the simplest. If we could work out a solution between the two of us, I would be more than happy to code it up and contribute the code. Best regards, David Oleg Tkachenko olegt () multiconn ! com wrote: Hello! "David Blevins" david.blevins () visi ! com wrote: Now I have my first question, so here goes. What is the recommended approach to generate a TIFF output: using the SVGRenderer then transcoding to TIFF with batik; using the TIFFRenderer written by Oleg? Hard question. TIFFRenderer has some flaws: it is not thread-safe, because AWTRenderer isn't. Another its problem is that all generated page images are held in memory. Both issues I hope will be fixed in FOP 1.0dev. So may be SVGRenderer is a prefered approach at the moment.The TIFFRenderer works, however the outputted TIFF is white text on black background (should be the other way around). Maybe there is something I need to configure correctly. Well, which TIFF viewer are you using? AFAIK, there is a great mess amongst TIFF viewers what is white and what is black in b/w FAX compressed images, e.g. consider given black-and-white TIFF image, Adobe Photoshop and Windows Imaging will show it differently black on white or white on black. TIFFRenderer uses JAI encoder, which seems to be agree with Adobe in this question, so I always rely on Photoshop and Alternatiff plugin and never got inverted image. Actually I've been thinking about introducing such a parameter to TIFFRenderer to allow control over that. Ok, granted, will try this week. There also doesn't seem to any new versions of the TIFFRenderer. The latest I can find is 0.9 from May last year. Is this there an updated, unreleased version somewhere? Well, I just don't see how can I make it better, it's quite simple wrapper, which heavily rely on JAI encoder and AWTRenderer. Now, when I'm FOP committer I'd better be focused on how to make FOP itself better, TIFFRenderer will benefit from it also. -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
RE: FOP output to TIFF
Title: Message I really never solved this one sry Rob -Original Message-From: David Blevins [mailto:[EMAIL PROTECTED]Sent: March 4, 2003 2:59 PMTo: [EMAIL PROTECTED]Subject: RE: FOP output to TIFF Thanks for the feedback. Unfortunately, the black vs. white things is not up to my interpretation. This is part of an already existing and heavily used document archival application (written in VB). So it's too late to change requirements. What workaround did you use for number 3? Thanks, David -Original Message-From: Rob Stote [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 12:23 PMTo: '[EMAIL PROTECTED]'Subject: RE: FOP output to TIFF David: I ran into many of the same issues you did rendering to TIFF. I used Oleg's TiffRenderer: The Black and White thing is really a Windows imaging issue. I got around this by using Alternatiff browser plug-in, or viewing my TIFF's on a non-windows based machine. (in my case a solaris box - image tool). I could never solve your issue 3, if you get an answer please let me know. I would be willing to help as much as I can. Rob -Original Message- From: David Blevins [mailto:[EMAIL PROTECTED]] Sent: March 4, 2003 1:46 PM To: [EMAIL PROTECTED] Subject: RE: FOP output to TIFF Thanks for the reply Oleg, Multithreaded access isn't a requirement, so we are in the clear there. The requirements are simple: 1. TIFFs must use comp group 3x or greater 2. Must be able to set (or even hardcode) the width and height. 3. Must be able to split each "page" of the XSL-FO doc into separate TIFF files. That's it. I've tried: 1. XSL-FO to SVG to TIFF using FOP and Batik. Meets requirements 2 and 3 nicely but not 1. The generated TIFF files are more than two meg at the required width and height. 2. XSL-FO to TIFF using your TIFFRenderer. Meets requirement 1, though still getting black backgrounds. Using Photoshop and QuickTime to view the output. This might be an easy thing to reverse if I knew which section of the code needed changing. If that were resolved, I would still need a solution for requirements 2 and 3. 3. XSL-FO to SVG to TIFF using FOP and Batik hacked to use your TIFFImageEncoder. Was really hoping this would get me the compression capabilities (requirement 1) while retaining the ability to do requirements 2 and 3. Unfortunately, it didn't work. It can generate uncompressed TIFFs just fine, but trying any compression generates invalid TIFF files about 2k in size. At this point, I'm not sure what direction to go next. It seems like your code is the simplest. If we could work out a solution between the two of us, I would be more than happy to code it up and contribute the code. Best regards, David Oleg Tkachenko olegt () multiconn ! com wrote: Hello! "David Blevins" david.blevins () visi ! com wrote: Now I have my first question, so here goes. What is the recommended approach to generate a TIFF output: using the SVGRenderer then transcoding to TIFF with batik; using the TIFFRenderer written by Oleg? Hard question. TIFFRenderer has some flaws: it is not thread-safe, because AWTRenderer isn't. Another its problem is that all generated page images are held in memory. Both issues I hope will be fixed in FOP 1.0dev. So may be SVGRenderer is a prefered approach at the moment. The TIFFRenderer works, however the outputted TIFF is white text on black background (should be the other way around). Maybe there is something I need to configure correctly. Well, which TIFF viewer are you using? AFAIK, there is a great mess amongst TIFF viewers what is white and what is black in b/w FAX compressed images, e.g. consider given black-and-white TIFF image, Adobe Photoshop and Windows Imaging will show it differently black on white or white on black. TIFFRenderer uses JAI encoder, which seems to be agree with Adobe in this question, so I always rely on Photoshop and Alternatiff plugin and never got inverted image. Actually I've been thinking about introducing such a parameter to TIFFRenderer to allow control over that. Ok, granted, will try this week.There also doesn't seem to any new versions of the TIFFRenderer. The latest I can find is 0.9 from May last year. Is this there an updated, unreleased version somewhere? Well, I just don't see how can I make it better, it's quite simple wrapper, which heavily rely on JAI encoder and AWTRenderer. Now, when I'm FOP committer I'd better be focused on how to make FOP itself better, TIFFRenderer will
Re: Best way to uppercase text
[EMAIL PROTECTED] wrote: I want to use the text-transform=uppercase attribute... I thought about using the xsl translate(string,string,string) function, but I don't think that's the best solution and I'm sure there is a better way to do that. There is *no* better way to do this until locale aware string functions arrive with XPath 2.0. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
[EMAIL PROTECTED] wrote: Please note that I don't want to use a proportionnal (like Courier) font in my Table of Content, cause I have some graphical obligation. The problem is not caused by the font, it is caused by the problem that FOP has to reserve space for the page numbers at a time when the numbers are not yet known (Bug #1130). This is already fixed in CVS. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
J.Pietschmann wrote: [EMAIL PROTECTED] wrote: Please note that I don't want to use a proportionnal (like Courier) font in my Table of Content, cause I have some graphical obligation. The problem is not caused by the font, it is caused by the problem that FOP has to reserve space for the page numbers at a time when the numbers are not yet known (Bug #1130). This is already fixed in CVS. J.Pietschmann When you say this bug is fixed in CVS do you mean that it's fixed in the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3 version) or what I understand is the re-design version (i.e. the not-so-soon-to-be-released-but-depends-on-definition-of-soon 1.0 version)? Or am I missing something, and there's a-version-being-talked-about-and-I-just-don't-have-a-clue version? ;-) -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Empty page before break-before=page
Consider this FO snippet: fo:page-sequence master-reference=CoverPage force-page-count=odd [...Cover page...] /fo:page-sequence fo:page-sequence master-reference=ContentPage initial-page-number=1 fo:flow flow-name=xsl-region-body fo:block font-size=22pt break-before=page border-after-style=solid Chapter Title /fo:block Now my problem is that FOP inserts an empty page (of type ContentPage) before the Chapter Title block, because of the break-before attribute. This is a bug IMHO, because it should take into account that a new page sequence means a page break. I tried it with XEP, and it works as it should, ie. without the bogus page. The thing also happens in this situation: fo:block fo:external-graphic src=url(fig/ucase.svg) / /fo:block fo:block font-size=22pt break-before=page border-after-style=solid BlaBla /fo:block The SVG ends at the end of the page, still a new empty page is inserted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:leader weird output (again) ;o)
Clay Leeds wrote: When you say this bug is fixed in CVS do you mean that it's fixed in the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3 version) Yes. There is a CHANGES and an archive for the commit messages at http://marc.theaimsgroup.com/?l=fop-cvs J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
