RE: [docbook-apps] Weird characters in generated HTML
David,
Thanks for the tip. I'll check the CSS for a bum style in the style
sheet. It is odd that simply swapping the XSLT processor generated such
different results.
Cheers,
Eric
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 7:16 PM
To: Johnson, Eric; Barton Wright
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
a id=foo/ shouldn't be a problem (my docs are full of them...I do
generate xhtml and stay out of quirks mode, but I don't think that
matters here) unless you do something like a{ color: blue;
text-decoration: underline;} in your css. Then everything after a a
id=foo/ until the next time a closing /a tag is reached will be
blue. Do a[href]{ color: red; text-decoration: underline;} instead.
David
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 5:18 PM
To: Barton Wright; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
As far as I can tell it is all of the anchors. Not just the olink
ones.
I'm calling Saxon, with Xerces, from ant using the java task:
java classname=com.icl.saxon.StyleSheet
classpathref=xslt-classpath fork=true
sysproperty
key=javax.xml.parsers.DocumentBuilderFactory
value=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl/
sysproperty key=javax.xml.parsers.SAXParserFactory
value=org.apache.xerces.jaxp.SAXParserFactoryImpl/
sysproperty
key=org.apache.xerces.xni.parser.XMLParserConfiguration
value=org.apache.xerces.parsers.XIncludeParserConfiguration/
arg value=-x /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-y /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-r/
arg
value=org.apache.xml.resolver.tools.CatalogResolver/
arg value=-o/
arg value=output/toc.html/
arg value=${ROOT}.xml /
arg
value=${env.DBCK_HOME}/custom/fuse-xhtml-chunk.xsl /
arg value=target.database.document=../site.xml /
arg value=current.docid=${DOCID}/
/java
and using version 1.73.1 of the style sheets.
-Original Message-
From: Barton Wright [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:42 PM
To: Johnson, Eric; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Hey Eric,
No, I definitely didn't customize anything about olinks when I was
there. :-)
We use Saxon and Xerces here, and olinks are generated normally in the
a id=foo/a format.
Can you be more explicit about which of your olinks are being
generated into the a id=foo / format? Is it all olinks or some? Is
it olinks and not links or xrefs?
BTW, expect Saxon processing to be significantly slower than xsltproc,
as little as 10% to 50% as fast as the equivalent xsltproc command.
But all the current development seems to be in the Saxon realm, and it
has better cross-platform support.
So there we are.
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:12 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
I found the problem...
It seams that the java processors generate a id=foo / for anchors
and xsltproc generates a id=foo/a. Firefox and
IE7 don't like a id=foo /. I'm pretty sure the guy who originally
did our customization layer didn't change the olink stuff, but I could
be wrong.
Where would I look to figure out how to make the Java XSLT processors
do the right thing?
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 3:01 PM
To: Johnson, Eric
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Check for an empty a href=/ element immediately before the
everything's a link stuff starts. Then trace back to your docbook
source (or your customization layer) to find where the emtpy a
href=/ is coming from.
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 1:30 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Thnaks, I should have seen that. That fixed the hatted A's, but I
still cannot figure out why all my content is being
rendered as links.
I haven't changed the source that I used when working with xsltproc.
On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote:
Take a look at
http://www.sagehill.net/docbookxsl/SpecialChars.html
(scroll down to Odd characters in HTML output).
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 11:04 AM
RE: [docbook-apps] Weird characters in generated HTML
David,
The change to the CSS did the trick!! Thanks.
Cheers,
Eric
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 7:16 PM
To: Johnson, Eric; Barton Wright
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
a id=foo/ shouldn't be a problem (my docs are full of them...I do
generate xhtml and stay out of quirks mode, but I don't think that
matters here) unless you do something like a{ color: blue;
text-decoration: underline;} in your css. Then everything after a a
id=foo/ until the next time a closing /a tag is reached will be
blue. Do a[href]{ color: red; text-decoration: underline;} instead.
David
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 5:18 PM
To: Barton Wright; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
As far as I can tell it is all of the anchors. Not just the olink
ones.
I'm calling Saxon, with Xerces, from ant using the java task:
java classname=com.icl.saxon.StyleSheet
classpathref=xslt-classpath fork=true
sysproperty
key=javax.xml.parsers.DocumentBuilderFactory
value=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl/
sysproperty key=javax.xml.parsers.SAXParserFactory
value=org.apache.xerces.jaxp.SAXParserFactoryImpl/
sysproperty
key=org.apache.xerces.xni.parser.XMLParserConfiguration
value=org.apache.xerces.parsers.XIncludeParserConfiguration/
arg value=-x /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-y /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-r/
arg
value=org.apache.xml.resolver.tools.CatalogResolver/
arg value=-o/
arg value=output/toc.html/
arg value=${ROOT}.xml /
arg
value=${env.DBCK_HOME}/custom/fuse-xhtml-chunk.xsl /
arg value=target.database.document=../site.xml /
arg value=current.docid=${DOCID}/
/java
and using version 1.73.1 of the style sheets.
-Original Message-
From: Barton Wright [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:42 PM
To: Johnson, Eric; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Hey Eric,
No, I definitely didn't customize anything about olinks when I was
there. :-)
We use Saxon and Xerces here, and olinks are generated normally in the
a id=foo/a format.
Can you be more explicit about which of your olinks are being
generated into the a id=foo / format? Is it all olinks or some? Is
it olinks and not links or xrefs?
BTW, expect Saxon processing to be significantly slower than xsltproc,
as little as 10% to 50% as fast as the equivalent xsltproc command.
But all the current development seems to be in the Saxon realm, and it
has better cross-platform support.
So there we are.
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:12 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
I found the problem...
It seams that the java processors generate a id=foo / for anchors
and xsltproc generates a id=foo/a. Firefox and
IE7 don't like a id=foo /. I'm pretty sure the guy who originally
did our customization layer didn't change the olink stuff, but I could
be wrong.
Where would I look to figure out how to make the Java XSLT processors
do the right thing?
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 3:01 PM
To: Johnson, Eric
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Check for an empty a href=/ element immediately before the
everything's a link stuff starts. Then trace back to your docbook
source (or your customization layer) to find where the emtpy a
href=/ is coming from.
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 1:30 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Thnaks, I should have seen that. That fixed the hatted A's, but I
still cannot figure out why all my content is being
rendered as links.
I haven't changed the source that I used when working with xsltproc.
On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote:
Take a look at
http://www.sagehill.net/docbookxsl/SpecialChars.html
(scroll down to Odd characters in HTML output).
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 11:04 AM
To: docbook-apps
Subject: [docbook-apps] Weird characters in generated HTML
Sorry
Re: [docbook-apps] Weird characters in generated HTML
Johnson, Eric wrote: As far as I can tell it is all of the anchors. Not just the olink ones. I'm calling Saxon, with Xerces, from ant using the java task: Since your questions focus on ant, java and xslt, why are you asking them on the docbook mailing lists? Try the ant list, the xslt list etc. regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
I think it's a fair question for the docbook-apps list. He's getting different behavior from the docbook xslts using different processors and using the xslt processor he was told is the preferred one (saxon), he's getting obiviously bad output (everything's a hyperlink). Other lists wouldn't know enough about how we put all the tools together. The xslt list would probably tell him there's no difference between a id=foo/ and a id=foo/a. I think he's actually got a poorly written css rule. David -Original Message- From: Dave Pawson [mailto:[EMAIL PROTECTED] Sent: Saturday, December 01, 2007 2:19 AM To: Johnson, Eric Cc: docbook-apps Subject: Re: [docbook-apps] Weird characters in generated HTML Johnson, Eric wrote: As far as I can tell it is all of the anchors. Not just the olink ones. I'm calling Saxon, with Xerces, from ant using the java task: Since your questions focus on ant, java and xslt, why are you asking them on the docbook mailing lists? Try the ant list, the xslt list etc. regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
As far as I can tell it is all of the anchors. Not just the olink ones.
I'm calling Saxon, with Xerces, from ant using the java task:
java classname=com.icl.saxon.StyleSheet
classpathref=xslt-classpath fork=true
sysproperty key=javax.xml.parsers.DocumentBuilderFactory
value=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl/
sysproperty key=javax.xml.parsers.SAXParserFactory
value=org.apache.xerces.jaxp.SAXParserFactoryImpl/
sysproperty
key=org.apache.xerces.xni.parser.XMLParserConfiguration
value=org.apache.xerces.parsers.XIncludeParserConfiguration/
arg value=-x /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-y /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-r/
arg value=org.apache.xml.resolver.tools.CatalogResolver/
arg value=-o/
arg value=output/toc.html/
arg value=${ROOT}.xml /
arg value=${env.DBCK_HOME}/custom/fuse-xhtml-chunk.xsl /
arg value=target.database.document=../site.xml /
arg value=current.docid=${DOCID}/
/java
and using version 1.73.1 of the style sheets.
-Original Message-
From: Barton Wright [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:42 PM
To: Johnson, Eric; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Hey Eric,
No, I definitely didn't customize anything about olinks when I was
there. :-)
We use Saxon and Xerces here, and olinks are generated normally in the
a id=foo/a format.
Can you be more explicit about which of your olinks are being generated
into the a id=foo / format? Is it all olinks or some? Is it olinks
and not links or xrefs?
BTW, expect Saxon processing to be significantly slower than xsltproc,
as little as 10% to 50% as fast as the equivalent xsltproc command. But
all the current development seems to be in the Saxon realm, and it has
better cross-platform support. So there we are.
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:12 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
I found the problem...
It seams that the java processors generate a id=foo / for anchors
and xsltproc generates a id=foo/a. Firefox and IE7 don't like a
id=foo /. I'm pretty sure the guy who originally did our
customization layer didn't change the olink stuff, but I could be wrong.
Where would I look to figure out how to make the Java XSLT processors do
the right thing?
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 3:01 PM
To: Johnson, Eric
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Check for an empty a href=/ element immediately before the
everything's a link stuff starts. Then trace back to your docbook
source (or your customization layer) to find where the emtpy a
href=/ is coming from.
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 1:30 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Thnaks, I should have seen that. That fixed the hatted A's, but I
still cannot figure out why all my content is being rendered as links.
I haven't changed the source that I used when working with xsltproc.
On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote:
Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html
(scroll down to Odd characters in HTML output).
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 11:04 AM
To: docbook-apps
Subject: [docbook-apps] Weird characters in generated HTML
Sorry for the stream of newby questions...
I got both Saxon and Xalan to work with XIncludes and
catalogs from
Ant.
However, all of my generated HTML, using either
processor, comes out
as a link
Using Xalan I also got a bunch of hatted A's (an A wearing a
^) where ever there is a hard space.
Using Saxon my target database file for olinks has a
space at the top.
Using xsltproc under Windows, with the same source and
customization
layer, this never happened.
Any ideas?
- To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
a id=foo/ shouldn't be a problem (my docs are full of them...I do
generate xhtml and stay out of quirks mode, but I don't think that
matters here) unless you do something like a{ color: blue;
text-decoration: underline;} in your css. Then everything after a a
id=foo/ until the next time a closing /a tag is reached will be
blue. Do a[href]{ color: red; text-decoration: underline;} instead.
David
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 5:18 PM
To: Barton Wright; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
As far as I can tell it is all of the anchors. Not just the
olink ones.
I'm calling Saxon, with Xerces, from ant using the java task:
java classname=com.icl.saxon.StyleSheet
classpathref=xslt-classpath fork=true
sysproperty
key=javax.xml.parsers.DocumentBuilderFactory
value=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl/
sysproperty key=javax.xml.parsers.SAXParserFactory
value=org.apache.xerces.jaxp.SAXParserFactoryImpl/
sysproperty
key=org.apache.xerces.xni.parser.XMLParserConfiguration
value=org.apache.xerces.parsers.XIncludeParserConfiguration/
arg value=-x /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-y /
arg
value=org.apache.xml.resolver.tools.ResolvingXMLReader/
arg value=-r/
arg
value=org.apache.xml.resolver.tools.CatalogResolver/
arg value=-o/
arg value=output/toc.html/
arg value=${ROOT}.xml /
arg
value=${env.DBCK_HOME}/custom/fuse-xhtml-chunk.xsl /
arg value=target.database.document=../site.xml /
arg value=current.docid=${DOCID}/
/java
and using version 1.73.1 of the style sheets.
-Original Message-
From: Barton Wright [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:42 PM
To: Johnson, Eric; David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Hey Eric,
No, I definitely didn't customize anything about olinks when
I was there. :-)
We use Saxon and Xerces here, and olinks are generated
normally in the a id=foo/a format.
Can you be more explicit about which of your olinks are being
generated into the a id=foo / format? Is it all olinks or
some? Is it olinks and not links or xrefs?
BTW, expect Saxon processing to be significantly slower than
xsltproc, as little as 10% to 50% as fast as the equivalent
xsltproc command. But all the current development seems to be
in the Saxon realm, and it has better cross-platform support.
So there we are.
-Original Message-
From: Johnson, Eric [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 4:12 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
I found the problem...
It seams that the java processors generate a id=foo / for
anchors and xsltproc generates a id=foo/a. Firefox and
IE7 don't like a id=foo /. I'm pretty sure the guy who
originally did our customization layer didn't change the
olink stuff, but I could be wrong.
Where would I look to figure out how to make the Java XSLT
processors do the right thing?
-Original Message-
From: David Cramer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 3:01 PM
To: Johnson, Eric
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Check for an empty a href=/ element immediately before
the everything's a link stuff starts. Then trace back to
your docbook source (or your customization layer) to find
where the emtpy a href=/ is coming from.
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 1:30 PM
To: David Cramer
Cc: docbook-apps
Subject: RE: [docbook-apps] Weird characters in generated HTML
Thnaks, I should have seen that. That fixed the hatted A's, but I
still cannot figure out why all my content is being
rendered as links.
I haven't changed the source that I used when working with xsltproc.
On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote:
Take a look at
http://www.sagehill.net/docbookxsl/SpecialChars.html
(scroll down to Odd characters in HTML output).
David
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 30, 2007 11:04 AM
To: docbook-apps
Subject: [docbook-apps] Weird characters in generated HTML
Sorry for the stream of newby questions...
I got both Saxon and Xalan to work with XIncludes and
catalogs from
Ant.
However, all of my generated HTML, using either
processor, comes out
as a link
Using Xalan I also got a bunch of hatted A's (an A wearing a
^) where
RE: [docbook-apps] Weird characters in generated HTML
Hey Eric, No, I definitely didn't customize anything about olinks when I was there. :-) We use Saxon and Xerces here, and olinks are generated normally in the a id=foo/a format. Can you be more explicit about which of your olinks are being generated into the a id=foo / format? Is it all olinks or some? Is it olinks and not links or xrefs? BTW, expect Saxon processing to be significantly slower than xsltproc, as little as 10% to 50% as fast as the equivalent xsltproc command. But all the current development seems to be in the Saxon realm, and it has better cross-platform support. So there we are. -Original Message- From: Johnson, Eric [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 4:12 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML I found the problem... It seams that the java processors generate a id=foo / for anchors and xsltproc generates a id=foo/a. Firefox and IE7 don't like a id=foo /. I'm pretty sure the guy who originally did our customization layer didn't change the olink stuff, but I could be wrong. Where would I look to figure out how to make the Java XSLT processors do the right thing? -Original Message- From: David Cramer [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 3:01 PM To: Johnson, Eric Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Check for an empty a href=/ element immediately before the everything's a link stuff starts. Then trace back to your docbook source (or your customization layer) to find where the emtpy a href=/ is coming from. David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 1:30 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Thnaks, I should have seen that. That fixed the hatted A's, but I still cannot figure out why all my content is being rendered as links. I haven't changed the source that I used when working with xsltproc. On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote: Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
I found the problem... It seams that the java processors generate a id=foo / for anchors and xsltproc generates a id=foo/a. Firefox and IE7 don't like a id=foo /. I'm pretty sure the guy who originally did our customization layer didn't change the olink stuff, but I could be wrong. Where would I look to figure out how to make the Java XSLT processors do the right thing? -Original Message- From: David Cramer [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 3:01 PM To: Johnson, Eric Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Check for an empty a href=/ element immediately before the everything's a link stuff starts. Then trace back to your docbook source (or your customization layer) to find where the emtpy a href=/ is coming from. David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 1:30 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Thnaks, I should have seen that. That fixed the hatted A's, but I still cannot figure out why all my content is being rendered as links. I haven't changed the source that I used when working with xsltproc. On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote: Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
Thnaks, I should have seen that. That fixed the hatted A's, but I still cannot figure out why all my content is being rendered as links. I haven't changed the source that I used when working with xsltproc. On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote: Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
Check for an empty a href=/ element immediately before the everything's a link stuff starts. Then trace back to your docbook source (or your customization layer) to find where the emtpy a href=/ is coming from. David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 1:30 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Thnaks, I should have seen that. That fixed the hatted A's, but I still cannot figure out why all my content is being rendered as links. I haven't changed the source that I used when working with xsltproc. On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote: Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] Weird characters in generated HTML
I suspect the bug's actually in your css. Try it without your css and see if the problem goes away. David -Original Message- From: Johnson, Eric [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 3:12 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML I found the problem... It seams that the java processors generate a id=foo / for anchors and xsltproc generates a id=foo/a. Firefox and IE7 don't like a id=foo /. I'm pretty sure the guy who originally did our customization layer didn't change the olink stuff, but I could be wrong. Where would I look to figure out how to make the Java XSLT processors do the right thing? -Original Message- From: David Cramer [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 3:01 PM To: Johnson, Eric Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Check for an empty a href=/ element immediately before the everything's a link stuff starts. Then trace back to your docbook source (or your customization layer) to find where the emtpy a href=/ is coming from. David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 1:30 PM To: David Cramer Cc: docbook-apps Subject: RE: [docbook-apps] Weird characters in generated HTML Thnaks, I should have seen that. That fixed the hatted A's, but I still cannot figure out why all my content is being rendered as links. I haven't changed the source that I used when working with xsltproc. On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote: Take a look at http://www.sagehill.net/docbookxsl/SpecialChars.html (scroll down to Odd characters in HTML output). David -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 11:04 AM To: docbook-apps Subject: [docbook-apps] Weird characters in generated HTML Sorry for the stream of newby questions... I got both Saxon and Xalan to work with XIncludes and catalogs from Ant. However, all of my generated HTML, using either processor, comes out as a link Using Xalan I also got a bunch of hatted A's (an A wearing a ^) where ever there is a hard space. Using Saxon my target database file for olinks has a space at the top. Using xsltproc under Windows, with the same source and customization layer, this never happened. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
