https://bugzilla.wikimedia.org/show_bug.cgi?id=414


Brion Vibber <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]




--- Comment #21 from Brion Vibber <[email protected]>  2008-12-30 18:21:01 
UTC ---
Going back to the original issue... :)

One difficulty with forcing line wrapping in the display when dealing with code
or configuration examples is that frequently line breaks are semantically
important.

Take this example from
http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps :

<source lang="php">
$wgScriptPath = '/w';         # Path to the actual files. This should already
be there
$wgArticlePath = '/wiki/$1';  # Virtual path. This directory MUST be different
from the one used in $wgScriptPath
$wgUsePathInfo = true;
</source>

A wrap to 80 columns would display as:

$wgScriptPath = '/w';         # Path to the actual files. This should already
be there
$wgArticlePath = '/wiki/$1';  # Virtual path. This directory MUST be different
from the one used in $wgScriptPath
$wgUsePathInfo = true;

which, if typed as it looks into an Apache config file would result in a big
fat syntax error.

(Cut-and-paste will *hopefully* preserve the original, but it may not be
obvious to a reader who isn't cut-n-pasting in all cases.)

Automatic soft wrapping also produces horribly ugly results for heavily
indented code.

Manual wrapping for comments and long lines can provide output which is both
more attractive *and* works if copied as it looks; indentation, line
continuations ("\" at end of line in many syntaxes), proper formatting of
comments, etc all have to be done with knowledge of the syntax if they're to be
done.

So I do tend to recommend that <pre> or <source> sections be written targeting
a relatively modest screen width.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to