Re: Collapsing borders: FOTree stage -- progress update

On Sat, 27 Aug 2005 02:07 am, Andreas L Delmelle wrote: > Hi all, > > * The first step I took was moving much of the logic that is > currently in CollapsingBorderModelEyeCatching (in the layout package) > to CommonBorderPaddingBackground. I must admit I know very little about collapsing borders.

Re: Collapsing borders: FOTree stage -- progress update

On 27.08.2005 23:19:40 Andreas L Delmelle wrote: > BTW: since it is my intention to facilitate the job of the layout > package in this matter, I'm considering adding BorderInfo instances > (although I'm not sure where exactly) that keep the resolved info to > use precisely in these layout-spec

DO NOT REPLY [Bug 36391] - [PATCH] reference-orientation and negative values

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Collapsing borders: FOTree stage -- progress update

On Aug 27, 2005, at 22:22, Jeremias Maerki wrote: On 27.08.2005 21:33:44 Andreas L Delmelle wrote: I'm wondering, for instance, whether the table's before-border specs are only relevant for the first page that is spanned by the table. For example: in case the table has a header (and omit-head

Re: Collapsing borders: FOTree stage -- progress update

On 27.08.2005 21:33:44 Andreas L Delmelle wrote: > On Aug 27, 2005, at 09:09, Jeremias Maerki wrote: > > > Ok, the shock is gone. Thank you for reassuring me that you know what > > you do. That was my biggest concern. I'm happy that you can reuse some > > of my code. Finally, someone can use some

Re: Collapsing borders: FOTree stage -- progress update

On Aug 27, 2005, at 09:09, Jeremias Maerki wrote: Ok, the shock is gone. Thank you for reassuring me that you know what you do. That was my biggest concern. I'm happy that you can reuse some of my code. Finally, someone can use something I wrote to make better progress. Normally, it's the other

Re: Relative font weights and font selection

Victor Mote a écrit : As I understand the spec, this works differently from font-weight and can be resolved in the FO Tree: just select the next expanded value for "wider" or next condensed for "narrower". The font selection would be performed only after, when it is time to decide e.g. which f

DO NOT REPLY [Bug 36396] - [PATCH] Testcases for relative positioned background images

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36396] New: - [PATCH] Testcases for relative positioned background images

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36395] - Common Border and Background Properties not supported on all required objects

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36395] New: - Common Border and Background Properties not supported on all required objects

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36394] - fo:character generates invalid PDF

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36394] - fo:character generates invalid PDF

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: FOP website, release preparations: refactoring necessary

Perfect, I will be working towards something like that. Patrick Paul Jeremias Maerki wrote: Sorry, I got the wrong impression. Since it's a CMS I thought you suggested we use that. But you're right. The tab structure like Lenya has it is exactly what we need. I think we'll end up with the foll

Re: FOP website, release preparations: refactoring necessary

Sorry, I got the wrong impression. Since it's a CMS I thought you suggested we use that. But you're right. The tab structure like Lenya has it is exactly what we need. I think we'll end up with the following tabs: - Home - 0.20.5 - 1.0dev - Development (It's probably best to collapse "Development

Re: FOP website, release preparations: refactoring necessary

On Sat, 27 Aug 2005 09:57 pm, Patrick Paul wrote: > I was talking about their website (with the two tabs for the > different versions) , not their product. > > Patrick > > Jeremias Maerki wrote: > >Uh, oh. Sorry, but I don't think we'll do that. We don't even have > > the infrastructure for a Lenya

Re: FOP website, release preparations: refactoring necessary

Answers below Jeremias Maerki wrote: Have you seen this page? http://xmlgraphics.apache.org/fop/dev/doc.html Yes I have seen the page, I was just too tired last night to go on. This should give you everything you need to build the docs. But you will need to ignore the section about Forre

Re: FOP website, release preparations: refactoring necessary

Thanks you very much for your help. Patrick Manuel Mall wrote: Patrick, assuming you have forrest installed you build by simply typing forrest in the directory you checked the sources out from subversion, that is the directory where the forrest.properties file is in. The generated site is

Re: FOP website, release preparations: refactoring necessary

I was talking about their website (with the two tabs for the different versions) , not their product. Patrick Jeremias Maerki wrote: Uh, oh. Sorry, but I don't think we'll do that. We don't even have the infrastructure for a Lenya installation and I wouldn't want to rewrite our whole website

DO NOT REPLY [Bug 36394] New: - fo:character generates invalid PDF

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: Relative font weights and font selection

Manuel Mall wrote: > I am with Vincent on this one. Here is the text for "wider" > from the spec ("smaller" is defined the same way): > The relative keyword "wider" sets the value to the next > expanded value above the inherited value (while not > increasing it above "ultra-expanded"). > > No

RE: Relative font weights and font selection

Vincent Hennebert wrote: > Victor Mote a écrit : > > I am ignoring font-stretch for now. I am unclear whether it works > > similarly to font-weight, or whether it is totally > resolvable in the FO Tree. > > Interestingly, CSS 2.1 (the only version of CSS 2 still > available at > > W3C) removes

Re: FOP website, release preparations: refactoring necessary

Patrick, assuming you have forrest installed you build by simply typing forrest in the directory you checked the sources out from subversion, that is the directory where the forrest.properties file is in. The generated site is then in build/site. For delivering changes the following procedure

Re: FOP website, release preparations: refactoring necessary

Have you seen this page? http://xmlgraphics.apache.org/fop/dev/doc.html This should give you everything you need to build the docs. But you will need to ignore the section about ForrestBot since that only works for committers. Just use local Forrest by calling "forrest run" after you've unpacked F

Re: FOP website, release preparations: refactoring necessary

Uh, oh. Sorry, but I don't think we'll do that. We don't even have the infrastructure for a Lenya installation and I wouldn't want to rewrite our whole website just now. That would distract me too much at this stage of development. Even the Lenya project uses Forrest for their website. :-) On 27.0

Re: Collapsing borders: FOTree stage -- progress update

Ok, the shock is gone. Thank you for reassuring me that you know what you do. That was my biggest concern. I'm happy that you can reuse some of my code. Finally, someone can use something I wrote to make better progress. Normally, it's the other way around. :-) So I'm wishing you the best of luck a