How Wide is wide?

As an exercise in display of my own ignorance, what controls how wide the text is in a page display of say the 'Monastery Gates' for instance. Today I dropped by only to notice that all paragraphs were 'un-wrapped' and reading required using the horizontal display button at the bottom of the browser (I'm using IE5.5). This seems to change from time to time but I haven't figured out either the pattern or the reason! I also notice that it isn't the same from 'location' to 'location'.

–hsm

"Never try to teach a pig to sing…it wastes your time and it annoys the pig."

Comment on How Wide is wide?

Replies are listed 'Best First'.
Re: How Wide is wide? by demerphq (Chancellor) on Feb 28, 2002 at 19:29 UTC
Some people use PRE tags with long line content. It screws up the rest of the geometery. (Arggh sp!) So then it requires an Editor or Janitor to sort it all out. But if you watch this section youll see a little proposal of mine to try to reduce the number of times it happens. Yves / DeMerphq -- When to use Prototypes? Advanced Sorting - GRT - Guttman Rosler Transform	[reply]
(tye)Re: How Wide is wide? by tye (Sage) on Feb 28, 2002 at 22:54 UTC
I think on rare occasions, someone front-pages a Craft node and this usually makes the gates display rather badly as how Craft nodes are displayed usually means they are pretty wide and can be very, very wide. I think Craft should be updated to wrap code lines now that we have the "d/l code" feature. But that won't make it to the top of my to-do list for quite a while. In the mean time, you can go to user settings and request that Craft not be displayed when you hit The Monastery Gates. Refraining from front-paging Craft nodes might also be a good idea for the next while. (: - tye (but my friends call me "Tye")	[reply]
Re: (tye)Re: How Wide is wide? by hsmyers (Canon) on Mar 01, 2002 at 05:13 UTC
A particularly good (bad) example is today's Removing blank lines from array... –hsm "Never try to teach a pig to sing…it wastes your time and it annoys the pig."	[reply]