Last modified: 2014-02-24 19:17:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4913 - {{msgnw:foo}} should preserve new lines
{{msgnw:foo}} should preserve new lines
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
: newparser
Depends on:
  Show dependency treegraph
Reported: 2006-02-08 04:00 UTC by lɛʁi לערי ריינהארט
Modified: 2014-02-24 19:17 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description lɛʁi לערי ריינהארט 2006-02-08 04:00:43 UTC

Opening this bug because bug 47 (found with search msgnw) seams to relate to
somthing else.

Wiki syntax specifies topics which depend on "beginning of lines" (as list
syntax, table syntax).

However {{msgnw:foo}} does not preserve lines. This will force users to edit
'foo' in order to identify these syntax errors.

best regards reinhardt [[user:gangleri]]
Comment 1 lɛʁi לערי ריינהארט 2006-02-10 20:02:13 UTC
Some MediaWiki messages are very difficult to "understand" to "debug". This is
why the source code of the page is written over more lines:

Keeping this as it is is the request from
Bug 4356: keep ignoring new lines in [[MediaWiki:Ipboptions]]

is more difficult to understand.

As described in bug 4946 comment 5 {{msgnw:}} can be used for documentation. It
would be very usefull to see the same content *line by line* as seen in edit
especially if the browsers bidirectional algorithm would change the word order
because BiDi rendering over more lines is *not* the same as BiDi rendering of
single lines.

best regards reinhardt [[user:gangleri]]
Comment 2 lɛʁi לערי ריינהארט 2006-04-23 10:16:25 UTC

neither {{msgnw:foo}} nor <pre> ... </pre> preserves the "source" in respect to
character encoding using &:
&ndash; renders as "–" and the coding of the "source" is visible only with edit
/ view source.

&#160; will not be visible because this is &nbsp; &#xa0; Unicode Character

I would consider it as an improuvement if both {{msgnw:foo}} and <pre> ...
</pre> would "escape" such characters. It would make writing documentation much
more easy and consistent.
Comment 3 Andre Klapper 2014-02-24 19:17:59 UTC
Still valid, see e.g. for an example.

For the records: says:
{{msgnw:Name}} includes the template in a form that displays it as raw wiki syntax (the way <nowiki> does) when the page containing it is fetched.

Note You need to log in before you can comment on or make changes to this bug.