WWN 214 contains some sample code and in my browser I see: There are two things that are wrong:
- The #include statements are incomplete. That's because the HTML looks
like this:
Yeah, that's just a problem with the server side stuff. Newman - do you happen to know why? Seems like an XML parser thing.
'<br></br>' results in two line feeds eventhough that may be a bug in
There should not be a <br></br>... the real tag is <br /> which is both XML and HTML compliant. <pre> is an evil tag if you use CSS, it should never be used on WineHQ.
This does bring up a good point, <code> displays weird on WineHQ, compare it to how Zack does it: http://www.kerneltraffic.org/wine/wn20040312_214.html
I think the problem is for two reasons:
1) There's no CSS definition for BR. There should be and maybe it should look something like: { margin-bottom: 3px; margin-top: 3px } Likewise, I tend to use <ul> for doing indenting and it needs to have less whitespace above and below. Or, maybe <dl> could be changed and I can abuse that instead.
2) That particular instance has some markup problems, I put in a couple of extra <br /> tags in a few places. Corollary to Linus' feelings on backups: Proofreading is for wimps. Real men publish their writing to a news site and have everyone else spellcheck it.
(Although, you'll notice since Newman set me up with CVS acces I do tend to do a quick once over after committing it and then fix obvious mistakes. If you have any scripts that automate this I should be able to easily automate it into the existing publishing system I have. XML doesn't lend itself to spellchecking too easily, so I've never pursued it.)
--------------- Brian Vincent Copper Mountain Telecom vincentb@coppercolorado.com
I have fixed the issues in the parser with using code in the XML.
1.) > and < will no longer appear to be stripped as the parser was converting them to < and >, which the browser would think was a tag.
2.) <br> tags will no longer be doubled.
3.) for code samples, use <pre width="72"></pre> this will display the code as is, but wrap at 72 chars. keeping the width from getting to long.
On Wed, 2004-03-24 at 11:07, Brian Vincent (C) wrote:
WWN 214 contains some sample code and in my browser I see: There are two things that are wrong:
- The #include statements are incomplete. That's because the HTML
looks
like this:
Yeah, that's just a problem with the server side stuff. Newman - do you happen to know why? Seems like an XML parser thing.
'<br></br>' results in two line feeds eventhough that may be a bug
in
There should not be a <br></br>... the real tag is <br /> which is both XML and HTML compliant. <pre> is an evil tag if you use CSS, it should never be used on WineHQ.
This does bring up a good point, <code> displays weird on WineHQ, compare it to how Zack does it: http://www.kerneltraffic.org/wine/wn20040312_214.html
I think the problem is for two reasons:
- There's no CSS definition for BR. There should be and maybe it
should look something like: { margin-bottom: 3px; margin-top: 3px } Likewise, I tend to use <ul> for doing indenting and it needs to have less whitespace above and below. Or, maybe <dl> could be changed and I can abuse that instead.
- That particular instance has some markup problems, I put in a
couple of extra <br /> tags in a few places. Corollary to Linus' feelings on backups: Proofreading is for wimps. Real men publish their writing to a news site and have everyone else spellcheck it.
(Although, you'll notice since Newman set me up with CVS acces I do tend to do a quick once over after committing it and then fix obvious mistakes. If you have any scripts that automate this I should be able to easily automate it into the existing publishing system I have. XML doesn't lend itself to spellchecking too easily, so I've never pursued it.)
Brian Vincent Copper Mountain Telecom
vincentb@coppercolorado.com
-
Brian Vincent (C) -
Jeremy Newman