Trial history file; CSS problem
[I sent something like this on Saturday, but no one responded. So I'm resending in case it got rejected.] Instead of a mail attachment, the file is now in the Sandbox. Look under its "BOOST_ROOT/more/version_history.html" and pretend it's at the same relative spot in the main CVS. I'm surprised that a full-blown version history file wasn't added a long time ago. I raided the CVS history of the main "index.htm" file for the details. Any ancient-timers know the history of 1.11.0 and earlier? The header looks funny; I was wondering how to replicate the current look by mutating what's given with CSS. (I was thinking of the headers seen at <http://www.mozilla.org>.) I processed what I wrote through HTML-Tidy, adding indentation and line wrap. I kept getting weird spacing with the function descriptions at the Spirit section of 1.30.1 and the Lambda block-quote at 1.28.0. I worked-around the problem by undoing the line-breaks Tidy added at those points. After being bewildered for a long while about the weird spacing, I saw the problem when looking in the CSS file: CODE { FONT-FAMILY: Courier; white-space: pre; } This last (non-brace) line says that multiple white-space characters are _not_ collapsed into a single space. This lets CODE acts as an in-line variant of PRE, but it violates what CODE usually does! I need the default space-collapsing behavior of CODE. If no one can give me a justification for that attribute, I'm going to erase it. Even if you can justify it, do this instead: CODE.my_special { FONT-FAMILY: Courier; white-space: pre; } Then call it like so: <p>Blah blah, please <code class="my_special">keep all of my spaces</code> blah blah.</p> That way people who need the default space-collapsing attribute of CODE don't get screwed. (Right now it's optimizing the [IMO] <1% wacky case and forcing extra work to get the usual semantics [that should take 99+% of the cases].) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com
Daryle Walker <darylew@hotmail.com> writes:
[I sent something like this on Saturday, but no one responded. So I'm resending in case it got rejected.]
Nobody's moderating your posts, so it wasn't rejected. You can always check the message archive if you want to verify that a message showed up. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
On 10/13/04 4:18 PM, "David Abrahams" <dave@boost-consulting.com> wrote:
Daryle Walker <darylew@hotmail.com> writes:
[I sent something like this on Saturday, but no one responded. So I'm resending in case it got rejected.]
Nobody's moderating your posts, so it wasn't rejected. You can always check the message archive if you want to verify that a message showed up.
I did a quick search under my name, and Gmane didn¹t show that post. I had an attachment (~18KB), so I thought the mail server dumped the message without telling me (too large?). -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com
On 10/13/04 1:41 AM, "Daryle Walker" <darylew@hotmail.com> wrote: [SNIP]
CODE { FONT-FAMILY: Courier; white-space: pre; }
This last (non-brace) line says that multiple white-space characters are _not_ collapsed into a single space. This lets CODE acts as an in-line variant of PRE, but it violates what CODE usually does! I need the default space-collapsing behavior of CODE. If no one can give me a justification for that attribute, I'm going to erase it.
Even if you can justify it, do this instead:
CODE.my_special { FONT-FAMILY: Courier; white-space: pre; }
Then call it like so:
<p>Blah blah, please <code class="my_special">keep all of my spaces</code> blah blah.</p>
That way people who need the default space-collapsing attribute of CODE don't get screwed. (Right now it's optimizing the [IMO] <1% wacky case and forcing extra work to get the usual semantics [that should take 99+% of the cases].)
As promised, I got rid of the "bad" settings. Specifically, I replaced: CODE { FONT-FAMILY: Courier, monospace; white-space: pre; } with: CODE { FONT-FAMILY: Courier, monospace; } CODE.as_pre { white-space: pre; } This way, anyone that assumes the default spacing behavior gets it. But it means that now any files that required the strange spacing are forced to change their HTML code. (In other words, I possibly broke existing code for better purity. Of course, I thought the existing solution was broken from the start.) If no one complains or changes their code, I guess that means that no one needs the weird spacing (anymore). In that case, the new setting can be eventually removed. (If that happens, the default setting can also be removed, since it wouldn't really differ from browser defaults.) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com
participants (2)
-
Daryle Walker -
David Abrahams