Last modified: 2012-08-14 11:42:08 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 2453 - [[Special:Allmessages]] should provide information about the type of the MediaWiki message
[[Special:Allmessages]] should provide information about the type of the Medi...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.5.x
All All
: Low enhancement with 7 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://test.leuksman.com/index.php?ti...
:
: 8521 (view as bug list)
Depends on:
Blocks: 18521
  Show dependency treegraph
 
Reported: 2005-06-19 08:03 UTC by lɛʁi לערי ריינהארט
Modified: 2012-08-14 11:42 UTC (History)
6 users (show)

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


Attachments

Description lɛʁi לערי ריינהארט 2005-06-19 08:03:37 UTC
Hallo!

I suppose thet
http://test.leuksman.com/index.php?title=Special:Validate&mode=manage is
restricted to sysops, stewards, developers.

Neither
<b>Never, <i>ever</i>, change something here without <i>explicit</i> community
consensus!</b>
nor
'''Never, ''ever'', change something here without ''explicit'' community
consensus!'''
generate bold / italic text.

But this is not the issue of this bug report.


During translation of the MediaWiki user interface I experienced that the
individual messages may have different atributes / may be of different type:
- some support wiki syntax
- some support only (X)HTML (?)
- some none of the two mentioned above

- some are active only for the content language as Monobook.css (?)
- some will overwrite the message from the content language

- other criterias (?)

These informations should dispay as abreviations in [[Special:Allmessages]]
"near" the title of the message.

Many titles indicate by their first characters to what feature / special page
they relate. Neither a "''used in''" (whis is a "nice to have") nor a
"dependency of configurations - feature activated or not) is required here.

Regards Reinhardt [[user:gangleri]]
Comment 1 lɛʁi לערי ריינהארט 2005-06-21 16:50:16 UTC
note from related bug 2475: Translations should not use localized namespaces in
links

regarding clasification:
add
some MediaWiki messages are titles but other are pages ([[MediaWiki:Mainpage]],
[[MediaWiki:Currentevents-url]] other "-url"s)
some are values of a selection "show" / "hide" [[MediaWiki:Show]] /
[[MediaWiki:Hide]]
some add explaing text to a particular selection [[MediaWiki:Showhideminor]]
others?
Comment 2 lɛʁi לערי ריינהארט 2005-12-02 08:28:05 UTC
addition regarding the "type of the MediaWiki message" classification:

some MediaWiki messages will be "preserved" if another user interface is 
selected trough preferences or uselang=xx as [[MediaWiki:Sidebar]],
[[MediaWiki:Monobook.js]] others *not*.
Comment 3 lɛʁi לערי ריינהארט 2005-12-02 09:30:56 UTC
*more details*
for the translation of the MediaWiki user interface it is important to know how
&#nnnn; will be handeled / rendered, if it generates
a) &#nnnn; (untranslated)
b) the corresponding Unicode character

example where much time is / was wasted:

1) attachment http://bugzilla.wikimedia.org/attachment.cgi?id=1124&action=view
from Bug 4114: RTL related issue with Mozilla Firefox and Netscape: text and
checkboxes get squeezed; implement workaround
2) Bug 4024: &foo;-style character conversion is blocked in MediaWiki messages
Comment 4 Niklas Laxström 2009-02-28 18:43:06 UTC
*** Bug 8521 has been marked as a duplicate of this bug. ***

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


Navigation
Links