Last modified: 2009-08-02 18:17:31 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 12920 - add URL-friendly function as a complement of {{ns:namespace}}
add URL-friendly function as a complement of {{ns:namespace}}
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy, need-parsertest
Depends on:
  Show dependency treegraph
Reported: 2008-02-05 12:28 UTC by Anon Sricharoenchai
Modified: 2009-08-02 18:17 UTC (History)
3 users (show)

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


Description Anon Sricharoenchai 2008-02-05 12:28:18 UTC
Should add a new function {{nss:namespace name}}, so that,
{{nss:user_talk}} will yield "User_talk" (the URL-friendly percent encoded like {{NAMESPACEE}}, especially, when the namespace name is in UTF-8)

According to its complement function,
then {{ns:user_talk}} should yield "User talk" (rather than "User_talk").
Comment 1 Danny B. 2008-02-05 13:38:22 UTC
Suggesting {{nse:...}} since -e suffix is used to mark _e_ncoded.
Comment 2 Anon Sricharoenchai 2008-02-05 14:49:50 UTC
I prefer {{ns:user_talk}} to be "User talk" (no underscore),
so {{nse:...}} is introduced for the case that underscore is really needed.

Another reason for this is that, the current behavior of {{ns:...}} is inconsistent with either {{NAMESPACE}} or {{NAMESPACEE}}.
* {{NAMESPACE}}: no underscore, no % encoded
* {{NAMESPACEE}}: has underscore, has % encoded
* {{ns:...}}: has underscore, but no % encoded
so, theoretically, {{ns:...}} cannot be used in the either the context that {{NAMESPACE}} or {{NAMESPACEE}} can be used.
Comment 3 Anon Sricharoenchai 2008-02-05 14:59:51 UTC
So, theoretically, {{ns:...}} cannot be used in either the context that {{NAMESPACE}} or {{NAMESPACEE}} can be used.

(fix typo in previous comment)
Comment 4 Church of emacs 2009-08-02 18:17:31 UTC
Done in r54220

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