FYI: Fop 0.19 JPEG-Patch
It appears to work with FOP 0.19 for people who are using older versions of FOP. Took my picture intensive PDF from 35MB to 4MB. Don __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Arved- I didn't get any reply that the patch was comitted, and I am stuck behind a firewall that doesn't allow IP tunneling. So, I don't have access to the CVS repository. Don --- Arved Sandstrom [EMAIL PROTECTED] wrote: Sure, absolutely, I'll help out as a resource. Did your patch get committed? If not I'll take care of it. Sorry I'm a bit scattered...work is intense right now. Regards, Arved At 09:03 AM 8/29/01 -0700, you wrote: Hi Arved- I submitted patches against 20.1 to do an effective keep-with-next on list-item-label and list-item-body, except I assumed an implied keep-with-next on list-item-label. I would be glad to work with bodo on this time permitting. It would probably be best, so that there are not two different pieces of code floating around doing nearly the same thing. Don --- Arved Sandstrom [EMAIL PROTECTED] wrote: Hi, Bodo I'd be very happy to help. I'm badly sidelined due to work pressure, but there is always some time I can pry loose...I'd rather spend that time getting new developers up to speed. I'll review the source this evening and give you a synopsis of what we are facing here. Regards, Arved Sandstrom At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote: hi, i tried to use the keep-with-next property on a multi column page with some text blocks that normally fits on one page with 4 columns. my text consists of this sequence of text blocks: every 2nd block is meant to be a headline and the the following block is the paragraph belonging to that headline. therefore i set the keep-with-next attribute on the headline blocks but still the column break occurred between the headline and the paragraph. looking in to the code i found that in org.apache.fop.fo.flow.Block.layout(Area) the line: this.keepWithNext = this.properties.get(keep-with-next).getEnum(); does not have any effect , since the getEnum() method always returns (0) because the org.apache.fop.fo.KeepProperty(Keep) does not overwrite the getEnum() method. so i patched this so that this.keepWithNext got the value=5 (just to see what will happen then ) but immediately i run in to another error: the headline appeared on the bottom of the old column, a wrong page break occurred (instead of a column break) and the same headline appeared on the top of the new page. if nobody else is currently working on this problems i would be willing to do this, if i (as a someone who just started to try to understand the fop source code) get some assistance from the fop gurus. would you appreciate this? bodo teichmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Bodo- First, I don't think I qualify as better overlooking FOP, since my one and only contribution is getting that list-item thing to do what I wanted. But, here are some things I found out during that process, and answered below: --- [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Don, Arved i would be greatfull to work with someone on a related problem, who better overlooks FOP then i do at the moment . right now i have some questions: 1. i do not fully understand about the numerical and symbolic values for the keep-* stuff. the standard says (in 4.8 Keeps and Breaks) that there is any interger value allowed which specify the strength, whereas higher number means more strength is imposed on the keep condition. in other words the bigger the values is the more the fo-processor should try to keep the stuff together, right? but there are in addition to symbolic values auto (which means no keep condition) and always (which means keep always ) . on the other hand in FOP always is mapped to 5 in fop and auto is mapped to 7. which would mean only the values 5,6 and 7 are meaningfull and moreover it looks as if the always should actually at least be greater then auto. could you help me reducing my confusion? Maybe it would be easiest to just start with binary, either attempt to keep-with-next, or don't attempt. That might be a simpler case than trying to figure out how to define the various levels of keepness. To me it seems that would be most cases because either you can keep-with-next, or you can't because the keeped parts would overflow the column or page. That is a bug in what I did because overflow would cause an infinite loop. 2. i'm unsure about the within-* (e.g. within-page) property refinement. if for example, i have a block with keep-with-next.within-page=always but keep-with-next.within-column=auto does this mean that i should make a page break before that block if normaly the pagebreak would occure after it. but i should not start new column before that block instead let occure the column break after this block as if no keep-with-next property would have been set, right? I was focused on the keep-with-next.within-page, so I am not really familiar with column handling. 3. i don't yet understand how the mechanics of the FONode.rollback() works. it seems it has something to do with undoing layout operations in order to redoing this part of the layout with eg. different column or page breaks (e.g. if a keep condition occured that could not be fulfilled). am i on the right trak here? do you any more details on that, or do i need just to look more deeply in to the source? I was looking at rollback, and it didn't seem to undo layouts. Instead I set up a Vector in FOnode to contain a list of areas that a node creates, then filled in FONode.removeAreas() to remove the areas using that list. Then, I changed block to add the area it creates to that list. Then, set the marker to a value that will cause areas to be recreated, but not do anything to IDs (couldn't figure out how to back out ID's so didn't worry about it). The algorithm I see for keep-with-next: A node layout returns keep-with-next Set flag active for keep-with-next(page or column) Attempt to layout next node If next node layout returns AREA_FULL_NONE determine if full area is a page or a column If full area match with-(page/column) remove areas created by previous node set marker to prior to layout of previous node (I think I have remove doing this.) Return AREA_FULL_SOME Seems fairly simple. Here are the gotchas. 1) Preventing infinite loops. If you have both areas combined overflow the column of page, then it is impossible to keep-with-next. 2) I think a marker needs to be enumerated for setup done no area created. Say AREAS_READY_TO_BE_CREATED = -42, or possibly 0, since block uses the marker to designate which subnodes have been created so far. Basically, I think the use of marker needs to be fomalized somewhat. 3) Does undoing areas cause problems with the ID code? If so, how do we undo IDs too? I hope that helps Bodo. Don Bodo __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Arved- I submitted patches against 20.1 to do an effective keep-with-next on list-item-label and list-item-body, except I assumed an implied keep-with-next on list-item-label. I would be glad to work with bodo on this time permitting. It would probably be best, so that there are not two different pieces of code floating around doing nearly the same thing. Don --- Arved Sandstrom [EMAIL PROTECTED] wrote: Hi, Bodo I'd be very happy to help. I'm badly sidelined due to work pressure, but there is always some time I can pry loose...I'd rather spend that time getting new developers up to speed. I'll review the source this evening and give you a synopsis of what we are facing here. Regards, Arved Sandstrom At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote: hi, i tried to use the keep-with-next property on a multi column page with some text blocks that normally fits on one page with 4 columns. my text consists of this sequence of text blocks: every 2nd block is meant to be a headline and the the following block is the paragraph belonging to that headline. therefore i set the keep-with-next attribute on the headline blocks but still the column break occurred between the headline and the paragraph. looking in to the code i found that in org.apache.fop.fo.flow.Block.layout(Area) the line: this.keepWithNext = this.properties.get(keep-with-next).getEnum(); does not have any effect , since the getEnum() method always returns (0) because the org.apache.fop.fo.KeepProperty(Keep) does not overwrite the getEnum() method. so i patched this so that this.keepWithNext got the value=5 (just to see what will happen then ) but immediately i run in to another error: the headline appeared on the bottom of the old column, a wrong page break occurred (instead of a column break) and the same headline appeared on the top of the new page. if nobody else is currently working on this problems i would be willing to do this, if i (as a someone who just started to try to understand the fop source code) get some assistance from the fop gurus. would you appreciate this? bodo teichmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
table-and-caption problem?
Hi- I think this is a bad precendent. In FOP 0.19 fo:table-and-caption produces a table. But, in FOP 0.20.1 fo:table-and-caption is reported as being unsupported in this version, and produces no output. Why? Is that really a good idea? Don __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Using FOP 0.19-CVS to create PDF
My firewall does not allow IP tunneling. Without that even WinCVS doesn't help. Don --- Alex McLintock [EMAIL PROTECTED] wrote: --- Don Wellington [EMAIL PROTECTED] wrote: Hi Arved- It is with FOP-0.19 not the latest CVS. I am stuck behind a firewall, so CVS is not really an option. I thought that too for some time but using WinCVS I managed to download the CVS version from CVS. You need to tell WinCVS about your firewall proxies. Alex = Alex McLintock[EMAIL PROTECTED]Open Source Consultancy in London OpenWeb Analysts Ltd, http://www.OWAL.co.uk/ SF and Computing Book News and Reviews: http://news.diversebooks.com/ Get Your XML T-Shirt t-shirt/ at http://www.inversity.co.uk/ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Newbie attempting to help
Hi-
Well, I am trying to make my first contribution to
FOP. By working on bug 2988 which I submitted. I
willingly accept any and all help.
I tried forcing the status return from
ListItemLabel.layout to keep-with-next in an attempt
to force other code to handle keeping the
list-item-label and list-item-body together. That
didn't work, but keep-with-next is broken anyways, so
that is probably not unexpected. My thought right
now is to change
the end of ListItemLabel.layout to:
if(status == Status.OK) {
status = new Status(Status.KEEP_WITH_NEXT);
}
return status;
At least temporally, until I figure how to get FOP to
obey the keep_with_next when there is an
external-graphics as the first element in the
list-item-body.
Anything wrong with that? Any pointers in the right
direction?
Don Wellington
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
