/ Khalid Khidhir <[EMAIL PROTECTED]> was heard to say:
| Hi,
| I am trying to display a list or reviewers on the cover page of
| a book, I would like to use a table, is that possible?
| if not what should I use instead?
One possibility is , but you'll have to
tweak the stylesheets to get the pres
/ [EMAIL PROTECTED] was heard to say:
| separate META tags. All sites I have seen (and docs I
| have read on search engine HOWTO sites) suggest using
| a single META tag, name="keywords" (note plural),
| content="".
Works for me. Thanks.
Be seeing you,
/ Rune Enggaard Jensen <[EMAIL PROTECTED]> was heard to say:
| Hi all!
|
| I would like to customize the filename element such that
| if the path attribute is not empty, it is printed before
| the filename. Example:
|
| ddlhdl.h
|
| should render as
|
| bas/ddlhdl.h
|
| How can I do this?
/ madhu <[EMAIL PROTECTED]> was heard to say:
| and is an empty element , the default behaviour now is the
| title of the page is the title for navigation. using this element
| can i change the title for navigation. if yes how?
I don't think I've provided support for that, but I need to do anoth
Can you send me a small test case that demonstrates this bug?
Setting navto='no' works for me...
/ madhu <[EMAIL PROTECTED]> was heard to say:
| Hello,
|
| with Website DTD the attribute list of has this as one of
| the attribute
| navto yes|no "yes"
|
| this is default for the link to app
/ Bob McIlvride <[EMAIL PROTECTED]> was heard to say:
| > What backend are you using? With RTF, this works fine.
|
| We're using pdfjadetex (jadetex 2.20) to convert .tex files to .pdf. Is
| this a problem for Sebastian?
I think so.
Be seeing you,
/ Claus Rasmussen <[EMAIL PROTECTED]> was heard to say:
| Aaah, this is probably the root of my problem. We just have
| inside a and haven't thought much about it since it gets parsed fine
| with dsssl style sheets.
It did? I don't think that's ever been legal. And DSSSL should always
validat
/ [EMAIL PROTECTED] was heard to say:
| Could you add support for adding a DOCTYPE to HTML
| output pages? Just a small that we could override would be fine,
| or you could provide a default DOCTYPE:
You can't do that with a template, you should do that in your own
customization layer with xsl:
/ [EMAIL PROTECTED] was heard to say:
| "admon.graphics.extension" parameter, so I had to
| override the entire admon.graphic template to change
| the hard-coded file extensions. Could this be a
| parameter instead?
Sure thing.
Be seeing you,
/ [EMAIL PROTECTED] was heard to say:
| I'm having a problem generating META tags for my
| . I traced the problem to head.content,
| which takes $node from "*" mode="process.root" and
Yeah, there's some subtlety here that I always have trouble wrapping
my head around, but I think I've fixed it.
/ [EMAIL PROTECTED] was heard to say:
| I am packaging the DocBook XSL stylesheets and was wondering why there
| is no catalog file in that distribution while there is one in the DSSSL
| version?
Because I don't know of any XSLT processors that use an entity resolver
when loading URIs from xsl:im
/ [EMAIL PROTECTED] was heard to say:
| Hum, sufficient reason.
| But aren't we supposed to encourage the use of catalog files?
Yes. Please tell the implementors of the XSLT engines that you use
that you need this feature.
Be seeing you,
Bob McIlvride writes:
>
> > What backend are you using? With RTF, this works fine.
>
> We're using pdfjadetex (jadetex 2.20) to convert .tex files to .pdf. Is
> this a problem for Sebastian?
you'd better hope not. i have enough jadetex work backed up already.
sebastian
--- Beth Fischi <[EMAIL PROTECTED]> wrote:
> Would you say that what you
> suggested is the
> standard way to "style" documentation (i.e., set
> fonts, font size, color,
> etc.) that uses this particular setup? Send it
> through a stylesheet for
> basic HTML formatting and then add a CSS to handle
> What backend are you using? With RTF, this works fine.
We're using pdfjadetex (jadetex 2.20) to convert .tex files to .pdf. Is
this a problem for Sebastian?
Cheerio!
Bob
Robert McIlvride ([EMAIL PROTECTED]), Cogent Real-Time Systems
(www.cogent.ca)
If you pass a document that doesn't contain a doctype declaration (or
one that has an inaccessible location specified for the DTD) to an
XSLT processor, it doesn't get any information about ID attributes in
the document.
Subsequently, all of the cross-referencing in the stylesheets fails.
Debugg
/ Stéphane Bline <[EMAIL PROTECTED]> was heard to say:
| I suspect that there are some structural problems with Norm's stylesheets (I
| should be lynched for suggesting that ;) ).
Hardly. But a small test case would be appreciated.
FWIW, I'm using PassiveTeX mostly these days with quite reasonab
/ Jirka Kosek <[EMAIL PROTECTED]> was heard to say:
| I tryed to format DocBook documents converted from XML to FO with XSL
| Stylesheets (1.27) using latest versions of FOP (0.16) and XEP (2.01).
| Both processors crashed on FO files produced by stylesheets. Do anyone
| sucessfuly used these tool
/ Beth Fischi <[EMAIL PROTECTED]> was heard to say:
|
|
|
|
Try here, that might work better.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | The stone fell on the pitcher? Woe
htt
/ Stéphane Bline <[EMAIL PROTECTED]> was heard to say:
| I'm using DocBook XSL stylesheets v1.18 and somehow it does not seem to
| generate a TOC with the fo stylesheets ?
| Is there a paremeter to set ?
Nope, that was just a bug. Fixed in the latest experimental release.
| Also, I can't seem to
/ Bob McIlvride <[EMAIL PROTECTED]> was heard to say:
| Our print output for puts the in a block below the
| . We want the title and body of the formal paragraph to be in
| the same block, as in HTML output. For example:
What backend are you using? With RTF, this works fine.
/ madhu <[EMAIL PROTECTED]> was heard to say:
| a) CSS supports use of ID and CLASS to fine tune the out put (HTML) but whereas
| both these atributes are used as internal mechanism by DocBook. That is both
| these are used for procesing mechanism and doesn't get used in the out put HTML.
| ID for
> Thank you, Bob and Mark. That worked. One more question -- I'm new to XML,
> XSL, DocBook, and so on.
> Would you say that what you suggested is the
> standard way to "style" documentation (i.e., set fonts, font size, color,
> etc.) that uses this particular setup? Send it through a stylesheet
Title: RE: DOCBOOK-APPS: Unexpected HTML output using customization of HTML DocBook styles heet
>> I would instead
>> go for a CSS stylesheet for the HTML
>> element rather than the tag.
>I agree with Bob, and I would also suggest that you ditch
>the "colname" attributes on the s.
Th
> I would instead
> go for a CSS stylesheet for the HTML
> element rather than the tag.
I agree with Bob, and I would also suggest that you ditch
the "colname" attributes on the s.
Here's what the tdg has to say about the colname attribute:
- Entrys cannot be given out of order, the column
Jirka,
Same here. But I found out that FOP 0.16 correctly processes the fo files
produced by the 1.18 stylesheets.
So I tweaked the 1.18 stylesheets to add some 1.27 functionnalities
(especially autoTOC generation that did not work in 1.18, for me at least).
No matter how hard I tried I could not
Hi,
I tryed to format DocBook documents converted from XML to FO with XSL
Stylesheets (1.27) using latest versions of FOP (0.16) and XEP (2.01).
Both processors crashed on FO files produced by stylesheets. Do anyone
sucessfuly used these tools on DocBook documents?
I know that few months ago the
27 matches
Mail list logo
