RE: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
-Message d'origine- De : Daniel Noll [mailto:[EMAIL PROTECTED] Envoyé : mardi 20 février 2007 01:23 József Németh wrote: Excuse the buttler butting in but what the spec says is: Font family names containing whitespace should be quoted. If quoting is omitted, any whitespace characters before and after the font name are ignored and any sequence of whitespace characters inside the font name is converted to a single space. To me it means that even if not quoted font-family=Arial Unicode MS still ferers to a single font not to the sequece Arial, Unicode, MS. You're right, but didn't someone say very recently that they had a fix for this bug? Daniel Yes, it was on TRUNK by Andrea D. Pascal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Identifying a page break
Hi all, Is it possible to identify that a page break has occurred when processing XSL:FO? I wish to output some text continued ... at the bottom of the page when a page break occurs in the current block of data being output. i.e. the current block is not complete. We are currently using soft page breaks on fop ver .92b e.g. fo:block-container width=100% height=3cm fo:block/ /fo:block-container fo:block space-before=-3cm ... .. Cheers, Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
0.93: Multi-page table Corrupted
I've upgraded our doc build process from 0.25 to 0.93. In PDF output with 0.25, a table could span multiple pages, with the table header appearing on each page. However, with 0.93, the table stops on one page; subsequent rows aren't printed. Also, the bottom of the table is corrupted. Just two examples: the table title appears in the middle of a row, and the table overwrites the page footer. The following image of the page illustrates better than I can describe: http://img183.imageshack.us/img183/5849/corrupttableia3.png Does anyone know why I would be getting this result? Thanks in advance, -pm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 0.93: Multi-page table Corrupted
Hi Paul, Can you give a short XSL-FO file that shows the problem, please? Pascal -Message d'origine- De : Paul Moloney [mailto:[EMAIL PROTECTED] Envoyé : mardi 20 février 2007 13:18 I've upgraded our doc build process from 0.25 to 0.93. In PDF output with 0.25, a table could span multiple pages, with the table header appearing on each page. However, with 0.93, the table stops on one page; subsequent rows aren't printed. Also, the bottom of the table is corrupted. Just two examples: the table title appears in the middle of a row, and the table overwrites the page footer. The following image of the page illustrates better than I can describe: http://img183.imageshack.us/img183/5849/corrupttableia3.png Does anyone know why I would be getting this result? Thanks in advance, -pm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [SPAM] 0.93: Multi-page table Corrupted
I had the same issue. You have to set the keep-together to auto. I don't know exactly why... -Ursprüngliche Nachricht- Von: Paul Moloney [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Februar 2007 13:18 An: FOP Users List Betreff: [SPAM] 0.93: Multi-page table Corrupted I've upgraded our doc build process from 0.25 to 0.93. In PDF output with 0.25, a table could span multiple pages, with the table header appearing on each page. However, with 0.93, the table stops on one page; subsequent rows aren't printed. Also, the bottom of the table is corrupted. Just two examples: the table title appears in the middle of a row, and the table overwrites the page footer. The following image of the page illustrates better than I can describe: http://img183.imageshack.us/img183/5849/corrupttableia3.png Does anyone know why I would be getting this result? Thanks in advance, -pm - 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: Identifying a page break
Hi, read the Chris Bowditch's answer in archives at http://marc.theaimsgroup.com/?l=fop-userm=114829247129634w=2 HTH, Pascal -Message d'origine- De : Richard King [mailto:[EMAIL PROTECTED] Envoyé : mardi 20 février 2007 13:10 À : fop-users@xmlgraphics.apache.org Objet : Identifying a page break Hi all, Is it possible to identify that a page break has occurred when processing XSL:FO? I wish to output some text continued ... at the bottom of the page when a page break occurs in the current block of data being output. i.e. the current block is not complete. We are currently using soft page breaks on fop ver .92b e.g. fo:block-container width=100% height=3cm fo:block/ /fo:block-container fo:block space-before=-3cm ... .. Cheers, Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
No, they didn't! My error report was cosed with the remark that
in FOP the workaround is quoting. Yeah, but that's not the
answer I would expect (ord accept) for such a
(technically) minor bug.
I've changed my opinion on this issue. The CSS spec on 'font-family' gives
this example in section 5.2.2 of the Level 1 spec, 11-JAN-1999:
Font names containing whitespace should be quoted:
BODY { font-family: new century schoolbook, serif }
BODY STYLE=font-family: 'My own font', fantasy
To me, this cannot be labeled a workaround in FOP, it is compliance with
the spec. Frankly, I've never seen single quotes within an attribute, and I
would have bet money otherwise, but it's clear as can be in the CSS spec.
The level 2 spec contains the same example of single quoting font names that
contain spaces.
As an aside, Altova StyleVision currently ships with FOP .25, and it does
not single quote fonts containing spaces, which causes the integrated FO
support to fail when identifying fonts by font-family. It's unfortunate, but
it looks to me like this is a bug in StyleVision that should be corrected by
Altova. Although, I have to admit that it would be nice if FOP were
forgiving of this, since I plan to roll out StyleVision to several
developers as our primary FO GUI to use with the latest Apache FOP version.
Jeff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: 0.93: Multi-page table Corrupted
Pascal Sancho wrote: Hi Paul, Can you give a short XSL-FO file that shows the problem, please? Hi Pascal, An excerpt from the fo file showing just the table is here: http://utils.eurion.net/pastebin/index.php?13546 The entire FO file, if you need to see the table in context, is here (there's only 1 table in this slimmed-down version and it's at the end): http://utils.eurion.net/pastebin/index.php?58342 Regards, P. -- View this message in context: http://www.nabble.com/0.93%3A-Multi-page-table-Corrupted-tf3260166.html#a9063647 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: 0.93: Multi-page table Corrupted
paul_moloney wrote: Hi Pascal, An excerpt from the fo file showing just the table is here: http://utils.eurion.net/pastebin/index.php?13546 The entire FO file, if you need to see the table in context, is here (there's only 1 table in this slimmed-down version and it's at the end): http://utils.eurion.net/pastebin/index.php?58342 Unfortunately its difficult to use this FO file because paste bin has escaped all the quotes, so I would have to write a process to unescape them! Or do it by hand - ouch. One thing I noticed about your table is that it has border-collapse=collapse specified but this is not currently supported. In fact, specifying may activate an incomplete implementation which because its not finished may cause the strange affects that you've seen. For further analysis please attached the file to an e-mail or upload it to a site which doesn't manipulate the file in some way. Thanks, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] 0.93: Multi-page table Corrupted
cbowditch wrote: Unfortunately its difficult to use this FO file because paste bin has escaped all the quotes, so I would have to write a process to unescape them! Or do it by hand - ouch. Sorry about that; here they are again, this time using a different pastebin: http://www.pasteserver.net/187 (excerpt) http://www.pasteserver.net/186 (whole) Regards, P. -- View this message in context: http://www.nabble.com/0.93%3A-Multi-page-table-Corrupted-tf3260166.html#a9064650 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with alignment in page footer/header
Hi there! I have document with header and footer on every page. The header is expanded on page width. The footer has a little color square (10x15mm) with page number aligned inside this square. I need different alignment in footer and header for odd and even page. E.g. on odd page header text and page number square should be at right side of page and on even page - at left side of page. But I have not idea how to do this... Help please. I done next: fo:layout-master-set fo:simple-page-master master-name=odd_page page-width=215.9mm page-height=276.23mm margin-top=0mm margin-bottom=0mm margin-left=0mm margin-right=0mm fo:region-body margin-top=20mm margin-bottom=20mm margin-left=16mm margin-right=81.9mm/ fo:region-before precedence=true extent=20mm/ fo:region-after precedence=true extent=10mm/ /fo:simple-page-master fo:simple-page-master master-name=even_page page-width=215.9mm page-height=276.23mm margin-top=0mm margin-bottom=0mm margin-left=0mm margin-right=0mm fo:region-body margin-top=20mm margin-bottom=20mm margin-left=81.9mm margin-right=16mm/ fo:region-before precedence=true extent=20mm/ fo:region-after precedence=true extent=10mm/ /fo:simple-page-master fo:page-sequence-master master-name=run fo:repeatable-page-master-alternatives fo:conditional-page-master-reference master-reference=odd_page odd-or-even=odd / fo:conditional-page-master-reference master-reference=even_page odd-or-even=even / /fo:repeatable-page-master-alternatives /fo:page-sequence-master /fo:layout-master-set fo:page-sequence master-reference=run fo:static-content flow-name=xsl-region-before fo:block font-size=11pt font-family=sans-serif font-weight=bold background-color=#781d7e color=#e6ddeb line-height=16pt xsl:value-of select=upper-case(section/@name)/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block text-align=end font-size=10pt font-family=sans-serif background-color=#781d7e color=white line-height=26pt fo:page-number/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body xsl:apply-templates select=section/ /fo:flow /fo:page-sequence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 12:01, József Németh wrote: No, they didn't! Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) 0.93 won't be patched, that much is true... If you really, really need this feature, then you're welcome to checkout the source w/ Subversion and build-it-yourself. Later, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) Excellent! This means that my Altova StyleVision should work either way with the new rev. Is there a way to know when the next rev will be released? Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 19:49, Jeff Vannest wrote:
Yes, we did! :)
It was fixed in FOP /Trunk/ (= fix will be in the next release)
Excellent! This means that my Altova StyleVision should work either
way with
the new rev.
Indeed.
Is there a way to know when the next rev will be released?
Unfortunately, we don't have a timeline for this :(
(read: we're all volunteers, so it depends on whether any of us have
the time and motivation)
OTOH, if you have Subversion and Ant at your disposal, then it is a
piece of cake to build, though...
1) checkout the trunk from the repository
2) navigate to FOP's root directory, and type 'ant' ('ant package' to
save some time and only build the fop.jar).
That's all there is to it.
Cheers,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 14:20, Jeff Vannest wrote:
Hi Jeff,
I've changed my opinion on this issue. The CSS spec on 'font-
family' gives
this example in section 5.2.2 of the Level 1 spec, 11-JAN-1999:
Font names containing whitespace should be quoted:
BODY { font-family: new century schoolbook, serif }
BODY STYLE=font-family: 'My own font', fantasy
To me, this cannot be labeled a workaround in FOP, it is
compliance with
the spec. Frankly, I've never seen single quotes within an
attribute, and I
would have bet money otherwise, but it's clear as can be in the CSS
spec.
Interesting info! Thanks for looking this up and sharing.
OTOH, now I'm wondering...
If you've never seen single quotes within an attribute, I bet you
haven't looked too closely, or you just missed them --or you've never
written stylesheets...? ;P
In XSLT these could turn out to appear far more often than you think:
xsl:if test=contains(., 'literal')
I've even seen double quotes inside single quoted attributes, because
that is equally valid XML
xsl:if test='contains(., literal)'
Cheers,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) 0.93 won't be patched, that much is true... If you really, really need this feature, then you're welcome to checkout the source w/ Subversion and build-it-yourself. Later, Andreas Andreas, I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. Let me take your answer: I wonder, how should I have known about the fix. I specifically looked a the answers to my error report before I sent my reply and had not found any indication of it there. As a user I am equiped with the necessary environment to keep the softwares I am routinely using current. In this case using toroiseSVN I have checked out the complete FOP trunk just to find that, just as you suggest, if I want to use it I should build it myself. I didn't. (To state it slightly I wasn't in the right mood.) [In fact I had already installed a different workaround before I submitted the bug report.] On the FOP Download page I found this: Fixme (jeremias) Reenable the link to the SVN snapshots once they are available. Now, what the heck it's supposed to mean?!. Can you tell me a valid reason why there are no daily (or at least weekly) snapshot builds of the trunk available at least on the main FOP server? Anyway, why should I be at the bleeding edge with FOP Trunk if I only need a small, safe and fully tested fix in the 0.93 branch that I can easily update if there is a new build available. And finally knowing the history of FOP your mentioning of a new release is not too promising either. Please, do no take all this as an offence I have not meant it to be. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9070526 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: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 22:16, József Németh wrote: Hey Joe, Let me start off by saying that I was very tempted to let your posting pass and not give you any more attention, but I just couldn't help myself, so here we go... I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. Apologies if it irritates you. That is certainly the opposite of what is intended. Yes, the style may be 'downright amateurish', as you call it, because Open Source --as I understand it-- is not governed by the same laws as your everyday professional commercial software development company. There is no such thing as a 'strict deadline' here. No contracts, no customers... Keep in mind that all FOP devs started out where you are right now: a FOP user. We too saw features missing, and tried to help out where we could, up to the point of diving into the code and implementing them ourselves. Let me take your answer: I wonder, how should I have known about the fix. It would have sufficed to read the first line of the message you got from Bugzilla, although I do realize now I forgot to paste the link to the revision that fixed the bug. Sorry. I specifically looked at the answers to my error report before I sent my reply and had not found any indication of it there. As a user I am equiped with the necessary environment to keep the softwares I am routinely using current. In this case using toroiseSVN I have checked out the complete FOP trunk just to find that, just as you suggest, if I want to use it I should build it myself. I didn't. (To state it slightly I wasn't in the right mood.) [In fact I had already installed a different workaround before I submitted the bug report.] OK, so that means that you can easily synchronize the fop.jar in your project with a scheduled Subversion checkout, followed by a build and deployment... What are you complaining about? On the FOP Download page I found this: Fixme (jeremias) Reenable the link to the SVN snapshots once they are available. Now, what the heck it's supposed to mean?!. Can you tell me a valid reason why there are no daily (or at least weekly) snapshot builds of the trunk available at least on the main FOP server? Because someone needs to allocate time to set that up, and the demand is not nearly high enough to make this a pressing matter. I follow both fop-dev@ and fop-users@ almost on a daily basis, and I can't even remember how long ago it was that someone asked for these nightly builds. Probably those that thought they needed it, finally came upon a brilliant idea: Why don't I do the build myself, and synchronize my local sandbox with the repository? As I indicated, this is Open Source. We are not professionals when we are here. We all monitor this list, respond to postings (even when they're strictly speaking off-topic), take a shot at fixing long- standing but annoying bugs... Why? All /because we like to/ Whether, if or when new features get implemented, bugs fixed, releases done... this all depends on small human factors, such as a fop-dev working for a customer: if that customer absolutely needs features implemented, there you will suddenly see some things improved in a short time. Anyway, why should I be at the bleeding edge with FOP Trunk if I only need a small, safe and fully tested fix in the 0.93 branch that I can easily update if there is a new build available. Indeed, why should you even have a complete build? If you could download only the altered class, and replace that in your fop.jar... Again, schedule an 'svn up' of your local sandbox, rebuild and deploy. Why waste Apache's bandwidth on downloading much larger precompiled binaries? And finally knowing the history of FOP your mentioning of a new release is not too promising either. Please, do no take all this as an offence I have not meant it to be. Undoubtedly. You were just having a bit of fun, weren't you? ;P Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP -Printing specified number of pages
Hi, I am using Appache FOP 0.93 to create PDF output and print outs from XML and XLS-FO file. I am invoking the FOP through the provided FOB.bat file passing the command line arguements for xml file, xsl file and the -print option. I would like to know how to provide the From Page and To Page options to the FOP to print the specified number of pages. FOP.bat -xml Data.xml -xsl FO_Template.xsl -print how to specify the -Dstart=2 and -Dend=4 The following statement does not work FOP.bat -xml Data.xml -xsl FO_Template.xsl -print -Dstart=2 -Dend=4 Please provide inputs on this. Thanks, Ram
