On Mon, Aug 30, 2010 at 2:08 PM, Daniel Leidert
daniel.leidert.s...@gmx.net wrote:
Sorry for not answering earlier. I contributed a few bug-fixes
(8895,8898-8900) from the Debian project during the last days and I
would like to see them too in the next release (if possible).
I was going to
Hi,
A release candidate for DocBook-XSL 1.76.0 is ready for you to test.
Please review the release notes (below) and give it a whirl and let me
know if we should release it on Friday, 3 Sept 2010.
Files: http://kfahlgren.com/docbook-xsl/
Reminder:
titleAbout dot-zero releases/title
Would you mind elaborating on the SVG/FO point because it seems to be
working fine right now.
On 8/31/2010 2:56 AM, Keith Fahlgren wrote:
Hi,
A release candidate for DocBook-XSL 1.76.0 is ready for you to test.
Please review the release notes (below) and give it a whirl and let me
know if we
Hi Keith,
Please also mention the addition of webhelp as a newly supported output format
in the release notes :-)
Thanks,
David
-Original Message-
From: Keith Fahlgren [mailto:abdela...@gmail.com]
Sent: Tuesday, August 31, 2010 2:56 AM
To: docbook-developers
Cc: Docbook Apps
Subject:
Bob Stayton wrote:
The tricky part is determining which letters actually have entries in
the current index, so you don't create bookmark links to non-existant
index sections. I don't have a quick solution for that one.
I think that code from autoidx.xsl can be reused, namely from
Ok. I'll ad something to look for that in the notes. Would you please
provide the text?
--
Typed with thumbs
On Aug 31, 2010, at 6:07 AM, Cramer, David W (David) dcra...@motive.com
wrote:
Hi Keith,
Please also mention the addition of webhelp as a newly supported
output format in the
Sure thing:
Webhelp
A new browser-based, cross-platform help format with full-text search and other
features typically found in help systems. See webhelp/docs/content/ch01.html
for more information and a demo.
Thanks,
David
-Original Message-
From: Keith Fahlgren
Thanks Bob,
It occurs to me that I preprocess before generating straight DocBook too, so I
should be ok interoperability-wise if I just strip the link text in my
preprocess.xsl.
My thinking in doing it this way is that generally I want olinks to behave like
xrefs so the link text is always
Hello Everyone,
I am investigating possibilities of the DB tables export into the given
proprietary format. Now I am stuck with the demand to specify the location
for every table entry in the form column:row.
My test data follows:
table frame=none
titletable/title
tgroup cols=3
On Tue, Aug 31, 2010 at 1:36 PM, Bob Stayton b...@sagehill.net wrote:
You are entitled to your opinion on b and i for XHTML, but they are
valid elements in XHTML Strict 1.0. We can't just turn them off from the
xhtml stylesheet set unless some alternative is put in place, because it
would
Leaving aside the issue of the highlighting stylesheets, here are the
uses of i in the html/ stylesheets:
biblio-iso690.xsl:3
biblio.xsl:3
component.xsl:1
division.xsl:1
synop.xsl:1
xref.xsl:1
simlarly, b:
autotoc.xsl:2
block.xsl:10
ebnf.xsl:1
formal.xsl:1
lists.xsl:1
qandaset.xsl:3
I wonder if anyone is using b and i in selectors in CSS? Such selectors would have to
be enhanced to include the new element names.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -
From: Keith Fahlgren abdela...@gmail.com
To: DocBook Apps ML
Keith Fahlgren wrote:
Looking at every single instance above, I don't see a single one that
should remain a b or i instead of being either removed or changed
to strong or em. Does anyone want to argue why b and i should
be preserved for 1.76.1?
Maybe I have missed some previous discussion,
As you've argued in the past, we don't have HTML5 stylsheets at this
time. As for b i, their use is discouraged in favor of style
sheets. We already use strong and em for emphasis, so the remaining
font elements are purely presentational and make it more difficult to
style DocBook (X)HTML
It has taken me a week of running experiments to get the proper handle on this.
When I am producing unchunked HTML output, it does indeed work as you have
described.
Unless I am misconstructing a chunked HTML output customization, chunking does
not work.
?xml version=1.0?
xsl:stylesheet
15 matches
Mail list logo
