Re: Web Maestro chicken?

[Clay Leeds]

Hehehe...
On Jun 17, 2004, at 7:22 PM, Glen Mazza wrote:
Clay,
Still too timid with the publish button?  Go
ahead--don't worry about the breadcrumb problem right
now--it's OK if it doesn't work for a few days.  More
important is to get you and Simon up on the committers
list.
Actually, I'm pretty sure I clicked the 'PUBLISH' button. I was still 
waiting for it to show up (I saw it in  viewcvs)... I just tried 
publishing again, but it appears to have timed out (it didn't time out 
last week). In fact, I just clicked the PUBLISH button again, and it 
timed out again. I'm launching Firefox 0.9 and seeing if things work 
differently...

However, after publishing, to fix the breadcrumb
problem:
c:\cvs checkout xml-site
hunt down the breadcrumb.js file under a "fop"
directory somewhere within the files just checked out.
modify it with an earlier "good" version (viewcvs can
help here)
cvs commit again (no subsequent publish needed).
Glen
Thanks for the heads up on this process. It makes sense (I guess I knew 
how to do this part), but it is nice to have the steps...

Hopefully the next time we 'see' each other, we'll have an updated TEAM 
page!

Web Maestro Clay

DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output

[bugzilla]

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_bug.cgi?id=26163

margin-left in nested fo:block not used in PDF output

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Priority|Other   |Medium



--- Additional Comments From [EMAIL PROTECTED]  2004-06-18 13:20 ---
I am seeing a bug that is probably related to this one. It suggests to me that
inheritance is not operating properly for list-blocks, at least for spacing and
possibly in general.

The scenario I am seeing is as follows:

Given



...



The fo:block will indent as expected -- that is, it will appear at the
indentation position that is expected of the list-item-body.

If, however, a start-indent is specified for the fo:block:



...



then the fo-block is indented **relative to the indentation of the containing


I have not tried it, but it would be interesting to see what the effect would be
of specifying .

I haven't looked at the code, but my suspicion is that either (a) the
start-indent inheritance processing within FOP has a bug of some sort, or (b)
the XSL-FO specification got the inheritance specification wrong. At the moment,
I'm leaning toward FOP as the culprit.

BTW, this problem is not in any way docbook specific. It's purely a fop issue.

RE: Offline

[Peter Porjes]

Return Receipt
   
Your  RE: Offline  
document   
:  
   
was   Peter Porjes/DSI/AT  
received   
by:
   
at:   18.06.2004 10:34:35