Re: [docbook] \r\n becomes 
 when generating XHTML (for ePub)

["Bob Stayton" <bobs@sagehill.net>]

Hi Boris,
Are you using the -o option with xmllint or writing to standard output?   If 
you use the -o option, you won't get the 
 characters.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


----- Original Message ----- 
From: "Boris Schäling" <boris@highscore.de>
To: <docbook@lists.oasis-open.org>
Sent: Thursday, January 21, 2010 3:38 PM
Subject: RE: [docbook] \r\n becomes &#13; when generating XHTML (for ePub)




> -----Original Message-----
> From: Boris Schäling [mailto:boris@highscore.de]
> Sent: Tuesday, January 19, 2010 10:16 PM
> To: docbook@lists.oasis-open.org
> Subject: [docbook] \r\n becomes when generating XHTML (for ePub)
>
> I'm including Windows text files with \r\n end line markers. When I
> generate
> XHTML (for ePub) all lines end with a &#13;. When I generate HTML no
> &#13;
> is inserted. I don't know if the output is different because the
> stylesheets
> are different or because the tools I use (xsltproc for HTML vs. the
> ePub
> converter which invokes xmllint).

As it turns out the problem is caused by the tools: "xsltproc --xinclude"
does not insert &#13; when it sees \r\n while "xmllint --xinclude" does. I
don't know why there is a difference as they are both coming from the
libxml2 project. As I couldn't find a command line option which I could set
for xmllint to ignore the \r I probably have to use another trick.

Boris



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-help@lists.oasis-open.org