XMLmind is happy to announce the version 4.4.1 of XMLmind XSL-FO Converter.
v4.4.1 (September 23, 2010):
XMLmind XSL-FO Converter is now available integrated in XMLmind XSL
Server, a powerful, production-quality, Servlet which leverages the XSL
Wow, this is interesting information.
I'd be curious about how you suppress an HTML tag with xsl. I know how
to insert HTML code, but not to remove it.. Anyone have a simple
example?
(Fortunately, a need for that hasn't come up yet for me).
(The only thing I could dig out of the archives
Sam Fischmann wrote:
Can anybody explain why these two if statements aren't in a
xsl:choose block?
Legacy code which has been refactored many times, matter of writing
style, ...
If the result string has any characters in it at
all, the element is included, so it makes no difference if the
Robert,
You hit on an interesting point. Hacking the DocBook stylesheets to not wrap
the contents of a listitem would be, as far as I can tell, difficult, and
require a lot of nasty hacking.
Also, since it's a hack to overcome what I would call a bug in one output
device, I wouldn't want to
Hi,
The solutions to this problem that I'm aware of all involve a
customization layer on top of the EPUB stylesheets rather than a
post-processing step. Other customizations include:
* Keeping the XHTML TOC (required by Kindle but typically a mistake for EPUB)
* Changing the toc.list*.types to
Hi.
Wednesday 08 September 2010
[...]
Actually OpenSuse internally also uses DocBook for documentation, but I
think that they use TeX for doing final typesetting of PDF version.
The TeX toolchain was long gone. We use a XSL-FO toolchain now. :)
Tom
On 9/24/2010 1:15 PM, Thomas Schraitle wrote:
Actually OpenSuse internally also uses DocBook for documentation, but I
think that they use TeX for doing final typesetting of PDF version.
The TeX toolchain was long gone. We use a XSL-FO toolchain now. :)
I don't know what toolchain that was,
I never tried that but I was wondering what was the best way to sort an index
after translation of the file set ? Especially in the case of languages that do
not use the same character set (for ex English vs Japanese) ?
What would be the best way to establish an easy to translate index ?
Typically you just translate the indexterms in place in the document and let
the xslts generate a new index. For Japanese, you add sortas attributes to your
primary, secondary, and tertiary elements with the term transliterated into a
phonetic script (katakana or hiragana).
Another problem is
