Re^4: newbies, <code> tags and recognizing perl (adjunct)

in reply to Re^3: newbies, <code> tags and recognizing perl
in thread newbies, <code> tags and recognizing perl

hmmm...i used <pre> tags to preserve the <code> in what appears to be in <code>...i had presumed that the caveat against this was in place because download is a product of <code> and not <pre>; but if you say my last post looked screwed up to you then either:

you are borderline illiterate

our browsers (me=linux/mozilla) are producing different output and i should never have used <pre>

As for my post being a re-iteration of BrowserUK's post, i agree -- vote for BrowserUk!

Regarding the preview button: I use it to death, but w/r/t a newbie poster i think the "in textarea" statement would be even more "intuitive" (if we can attribute intuition to newbies and knowlege to the practiced)

Comment on Re^4: newbies, <code> tags and recognizing perl (adjunct)

Replies are listed 'Best First'.
Re^5: newbies, <code> tags and recognizing perl (adjunct) by ww (Archbishop) on Mar 21, 2008 at 15:31 UTC
Generally (though it did not work as expected here, probably due to neurons misfiring or somesuch) to show `<code>...</code>` tags, place them inside <c>...</c> tags and vice versa. Use of `<pre>...</pre>` may be discouraged because it doesn't produce a download tag, but a more significant problem is the fact that long lines don't break, possibly producing a display wider than the user's normal browser window. Both these facts are discussed in the various documents on markup. And, BTW, even as a joke (if that's what it is) suggesting any poster, Monk or annonymonk, is "illiterate" falls into the "personal attack" range. As for browsers, as you may wish to explore, they don't all render the same .html and/or css in the same way, but following the Monastery-standard markup suggested in the docs tends to allow you to avoid problematic constructs. For the record, I too like BrowserUk's (note, lc "k") suggestion, but if all you really wanted to do in the post to which my previous reply was directed, was to endorse that, why not just do so?	[reply]

Replies are listed 'Best First'.

Re^5: newbies, <code> tags and recognizing perl (adjunct)
by ww (Archbishop) on Mar 21, 2008 at 15:31 UTC

Generally (though it did not work as expected here, probably due to neurons misfiring or somesuch) to show <code>...</code> tags, place them inside <c>...</c> tags and vice versa.

Use of <pre>...</pre> may be discouraged because it doesn't produce a download tag, but a more significant problem is the fact that long lines don't break, possibly producing a display wider than the user's normal browser window.

Both these facts are discussed in the various documents on markup.

And, BTW, even as a joke (if that's what it is) suggesting any poster, Monk or annonymonk, is "illiterate" falls into the "personal attack" range. As for browsers, as you may wish to explore, they don't all render the same .html and/or css in the same way, but following the Monastery-standard markup suggested in the docs tends to allow you to avoid problematic constructs.

For the record, I too like BrowserUk's (note, lc "k") suggestion, but if all you really wanted to do in the post to which my previous reply was directed, was to endorse that, why not just do so?

[reply]

In Section Perl Monks Discussion