h a l f b a k e r yReformatted to fit your screen.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
In the idea and annotation textareas, have a single carriage
return act as a < br > tag, so that no html is necessary to
achieve a linebreak.
XHTML
http://www.w3.org/MarkUp/#recommendations
Why everyone should be using <br />. [jvonr, Oct 17 2004]
Benefits of XHTML
http://www.nypl.org...xhtml/benefits.html
[po, Oct 17 2004]
[link]
|
| |
Ah... saving people from themselves? I hadn't thought of
that. Is doing your own linewrapping in textareas a
widespread practice? I suppose no one would really know
that information. |
|
| |
I do it because some text boxes don't, so you end up with a ten paragraph message on ten lines. Jutta programmed well, so that it automagically wraps as necessary, which allows it to fit into whatever size column it ends up in. |
|
| |
Fair enough. It seemed to me that people regularly (not
often, just regularly) had to be told to "use < br > tags for
a line break." I hadn't considered the other issue though. |
|
| |
This idea will probably implode fairly soon, unless any
really good deep thoughts about the subject are added. |
|
| |
It would be useful if there was an explicit list of what HTML tags are permitted. I know Jutta supports [br], but I don't know what else, if anything. She does not seem to support «entities»--not even < and >, so there's no way to show what a [br] really looks like. |
|
| |
In general, I don't mind that most tags are unavailable since they would detract from the appearance of the page and they'd get ludicrously overused. The [i] tag might not be too bad--CERTAINLY NO WORSE THAN ALLCAPS. And entities should not detract from page appearance in any bothersome way. |
|
| |
I am a proponent of the <i> tag myself. But that's about as far as it goes. I once wanted the but no longer. |
|
| |
• A few oddball things are supported, though. |
|
| |
Supercat: Why not just use '<>'? Works fine for me. I use them as parenthesis out of long habit. |
|
| |
Besides, if it can't be said in plain text, putting it in blinking orange Flyspeck-3 on a lime green background won't help. |
|
| |
Surprised this hasn't sparked discussion about how to do this... In PHP:
$annotation = eregi_replace("
", "< br >", $annotation); // replace carriage returns with line breaks
Obviously I used a < br > in place of a carriage return or this wouldn't have worked, but you get the idea. $annotation would be the annotation variable. |
|
| |
See the XHTML links I've posted. |
|
| |