Strange. I'm using the zlatkovic Windows port of xmllint (version 20630), and I get these results when I run it in a Windows command window:

xmllint --xinclude -o option.out test.xml [option.out has no 
 characters]

xmllint --xinclude test.xml >  stdout.out  [stdout.out has 
 characters]

I cannot explain why you get different results. Perhaps someone else could try it as well.

Bob Stayton
Sagehill Enterprises
[email protected]


----- Original Message ----- From: "Boris Schäling" <[email protected]>
To: "'Bob Stayton'" <[email protected]>; <[email protected]>
Sent: Saturday, January 23, 2010 5:23 AM
Subject: RE: [docbook] \r\n becomes &#13; when generating XHTML (for ePub)




-----Original Message-----
From: Bob Stayton [mailto:[email protected]]
Sent: Friday, January 22, 2010 6:28 PM
To: Boris Schäling; [email protected]
Subject: Re: [docbook] \r\n becomes when generating XHTML (for ePub)

Hi Bob,

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

yes, I use -o:

xmllint.exe --xinclude -o test2.xml test.xml

I tried redirecting to standard output but also got &#13; characters.

I'm using the latest version of the Windows port from
ftp://ftp.zlatkovic.com/libxml/. When I change the file and use Unix end
line markers I don't get &#13; characters (just to make sure that it's
indeed a problem with end line markers).

Do you use the Unix or Linux version of xmllint that you don't get &#13;
characters with -o? Or do you know if there is a trick to use "xsltproc
--xinclude" without a style sheet (as xsltproc doesn't generate &#13;
characters)?

Boris

[...]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to