I've taken a look through the e-mail archives, and I've tried
googling, but I'm unable to find an answer to why I can't do something
that should be quite simple. :( I've found documentation for how to
do it using Docbook 4.x (and had no luck using it with Docbook 5), but
it *seems* like a good
.
Dick Hamilton
[EMAIL PROTECTED]
-Original Message-
From: Kells Kearney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 6:13 PM
To: docbook@lists.oasis-open.org
Subject: [docbook] docbook5 and adding elements (long)
I've taken a look through the e-mail archives, and I've
15 years ago! :), but there a number of compelling
advantages (IMO) to using Docbook. (I think! :)
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: Kells Kearney [EMAIL PROTECTED]
To: docbook@lists.oasis-open.org
Sent: Tuesday, March 13
I have to apologize to both Dave and Bob, but they've given me far
too much credit for understanding. :) I'm hoping that I can impose
on your patience for just a little longer.
On 3/17/07, Dave Pawson [EMAIL PROTECTED] wrote:
Bob Stayton wrote:
Do you know of a good step-by-step
On 3/17/07, Chris Chiasson [EMAIL PROTECTED] wrote:
snip
I hate the reading, especially when I don't know exactly what I need to find.
Experience: What you get after you needed it.
/snip
Oh boy, did this experience ever hurt. :(
After a fair amount of reading and experimentation, I
This might be a little late, but it was an interesting problem that
I had to delay until I could get around to looking at it again.
Taking a little bit of time to learn SVG helped, too. :)
This example definitely needs some work to get your text exactly
right, and it's very crude in the
Here's a quick perl solution that doesn't read everything into
memory and seems to handle some of the edge cases. Try it out on a
few things to verify that everything is okay before completely
trusting it, though. :)
Copy the lines between '' into a file (say
On 4/2/07, Mykone Saunders [EMAIL PROTECTED] wrote:
Hello List. I have releaseinfoRELEASE INFO/releaseinfo under
book\bookinfo but it's not showing up in PDF. Am I doing something wrong?
Just to clarify: you want the releaseinfo elements to show up on
the page just after the the very first
:
I am using Docbook XSL 1.69.1 with Docbook XML 4.4
On Mon, 2007-04-02 at 15:42 -0600, Kells Kearney wrote:
On 4/2/07, Mykone Saunders [EMAIL PROTECTED] wrote:
Hello List. I have releaseinfoRELEASE INFO/releaseinfo under
book\bookinfo but it's not showing up in PDF. Am I doing something
to work.
If the simple test does generate something with the release info,
then you'll have to add content until you get to the point where
things stop working and figure things out from there. :)
kells
On Mon, 2007-04-02 at 15:47 -0600, Kells Kearney wrote:
Okay, then two follow-up questions
I've got a Windows Docbook5 setup with xsltproc, XSL1.7.2 and fop
0.9.3 and things work okay for me -- at least with JPEGs, PNGs and
GIFs. That's with both:
graphic fileref=Graphics/niagara.jpg width=4.747in
contentwidth=4.747in align=center /
and
mediaobject
imageobject
11 matches
Mail list logo
