On 3/5/07, Dave Pawson <[EMAIL PROTECTED]> wrote:

Hendy Irawan wrote:

> I agree that the stylesheet is fine and I have a lot of fun writing
books,
> but not designing stylesheets. I'm a web developer and I love to code
but I
> hate to deal with HTML/CSS/Photoshop (it's the designer's job, not
mine).
>
> I've just got O'Reilly's XSL-FO and unfortunately it doesn't contain as
> much
> information as I wanted it to.
Tell me where it's weak please.
I'm due an xsl-fo session for a second edition.


regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk


Wow!!

Never expected its author to be actually here... :-) [omg, this is the
DocBook official mailing list, how could I didn't think of that...?] ;-)

In short your book is much, much more enjoyable than XSL's W3C
recommendation. :-) And it's good great reviews and I should have added
positive review from me too.

Anyways, from the problem at hand, it's "not enough". I'm currently
troubleshooting how to put the chapter title on the top left with some
background. And although I've used the technique you described at the
near-end of the book (fo:block-container absolute-position=fixed top=20mm)
"it doesn't work". If I use block-container it vanishes. If I use block then
I can't position it. The only way I seem to be able to position a block is
using margin, which is pretty bad hack (but I think it'll use that as
desperate last effort).

I also wonder why something like block width=80% doesn't give me the
intended effect? (It still gives full width).

I'm using FOP 0.93 processor. Maybe this is an issue? I'm not planning to
move to XEP for something like this. I'm just a regular writer who wants to
publish free, good looking, tech e-books.

Anyways the current DocBook XSL stylesheet for FO/PDF seems to have a
"bug"... On glossary generation, if the glossterm is too long then it'll
"crash" with the gloss definition. Kinda ugly.

--
Hendy Irawan
Web: http://hendy.gauldong.net
Mobile: +62 856 24889899
Yahoo Messenger: ceefour666
LinkedIn: http://www.linkedin.com/in/ceefour

Reply via email to