-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Extension messages can now be translated. To add localized messages to
an extension, add a second parameter to the call to
MessageCache::addMessages, which includes the language code (the default
value is 'en').
For example, old style:
$wgMessageCache->addMessages( array( 'custom' => 'custom message' ) );
New style:
$wgMessageCache->addMessages( array( 'custom' => 'custom message' ), 'en' );
etc.
You are welcome to translate each extension, especially those which are
used in Wikimedia sites (a list is available in Special:Version), into
your language.
- --
#define Name RotemLiss
#define Mail mailSTRUDELrotemlissDOTcom
#define Site www.rotemliss.com
#define KeyFingerPrint 4AFD 8579 A449 4267 BED9 38E5 6EF8 5B1F EBDE 7AC0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEpZGHbvhbH+veesARAvtZAJwOnSudlV3kfzXzAHTuI6LF89OnrgCffk5E
HexWVAhExOZpjtKnWtRILts=
=Ad/c
-----END PGP SIGNATURE-----
Dear all,
I have written a proposal that is online at
http://nike.users.idler.fi/betawiki/User:Siebrand#Use_case_descriptions. It
is also copied here, but because of the many links in it, I recommend
reading it from the link. As far as I can assess, the scope of this proposal
currently does not go outside BetaWiki, as the methods used are not
supported elsewhere.
Feedback is very welcome.
Cheers!
Siebrand
Use case descriptions
=====================
In few, but important, cases during the translation of MediaWiki messages
from English to Dutch I was wondering: where does this message appear? I am
not able to make a proper translating without having seen the context of
this message.
To solve this problem I have setup a working prototype to assist in
* requesting documentation for a MediaWiki message
* documenting a MediaWiki message
* announcing availability of documentation for a MediaWiki message
* grouping available documentation of MediaWiki messages
* centralised talk on documentation for MediaWiki messages
Please read the proposal below and leave feedback.
Siebrand 15 July 2006, 12.45 (EEST)
Requesting documentation
------------------------
A system has been put in place earlier to facilitatie messages being place
on top of each localised page within the MediaWiki namespace. This can be
done by adding text to [[MediaWiki talk:Messagename/info]] I.e. text on this
page will be displayed on top of [[MediaWiki:Messagename/en]],
[[MediaWiki:Messagename/nl]] and all other languages.
Documentation for a use case can be requested by placing the following text
in [[MediaWiki talk:Messagename/info]]: {{Usecaseneeded|Messagename}}.
An example page of a use case request not filled, can be viewed at
[[MediaWiki:Sunday]].
Documenting a message
---------------------
Once the template Usecaseneeded has been placed, a message appears on top of
all localisations of that particular message stating: "A use case is
requested for this message. Please document it if you can." A link points to
[[Betawiki:UsecaseMessagename]].
On this page, the template {{Usecase|Messagename}} should be placed, to mark
the page as a use case. This adds a message on top of the description page
and categorises the page in [[Category:Use cases]].
An example page of a use case description can be viewed at
[[Betawiki:UsecaseMonday]].
Announce a use case
-------------------
Once a use case description has been created, the request for a use case is
no longer required. Template [[Template:Usecaseavailable]] has been created
to replace [[Template:Usecaseneeded]] at that time.
Use: {{Usecaseavailable|Messagename}}.
Example: [[MediaWiki_talk:Monday/info]]
Categorisation
--------------
Each use case description page should contain [[Template:Usecase]]. This
automatically adds the page it is used on to [[Category:Use cases]]. This
establishes overview, so that a contributor interested in looking at or
editing use cases has easy access.
Use: {{usecase|Messagename}}.
Example: [[Betawiki:UsecaseMonday]]
Centralised discussion
----------------------
A discussion page has been instated on [[Betawiki:Usecase]] for facilitating
centralised discussion.
Pages involved
--------------
Below is a list of all pages involved on BetaWiki in this proposal. In case
the proposal would not be accepted, these pages should be deleted to remove
all impact of the demonstration.
* BetaWiki:Usecase
* MediaWiki talk:Monday/info
* MediaWiki talk:Sunday/info
* Template:Usecase
* Template:Usecaseavailable
* Template:Usecaseneeded
Hallo!
php syntax allows both the usage of
'foo' => '...'
*and*
'bar' => "..."
However only o few messages are using 'bar' => "...".
These are:
'alreadyloggedin' => "...",
'anoneditwarning' => "...",
'anontalkpagetext' => "...",
'blockededitsource' => "...",
'blockedoriginalsource' => "...",
'clearyourcache' => "...",
'editinginterface' => "...",
'loginsuccess' => "...",
'missingsummary' => "...",
'userinvalidcssjstitle' => "...",
'welcomecreation' => "...",
At some point in time tools for computer aided translations will / might be
used. The automatic validation of translations could be simplified if only one
of syntax versions would be used.
I suggest to use the only the
'foo' => '...'
syntax.
Are there any arguments against this?
best regards reinhardt [[user:gangleri]]
New Messages from SVN trunk in r15482
Modified: trunk/phase3/languages/Messages.php
+'cantcreateaccounttitle' => 'Can\'t create account',
+'cantcreateaccounttext' => 'Account creation from this IP address
(<b>$1</b>) has been blocked.
+This is probably due to persistent vandalism from your school or
Internet service
+provider. ',
+'ipbanononly' => 'Block anonymous users only',
+'ipbcreateaccount' => 'Prevent account creation',
+'anononlyblock' => 'anon. only',
+'createaccountblock' => 'account creation blocked',
+'ipb_already_blocked' => '"$1" is already blocked',
+'ipb_cant_unblock' => 'Error: Block ID $1 not found. It may have been
unblocked already.',
Suisui
suisui(a)gmail.com
Hi!
I think next messages should use plural:
'watchlistcount' => 'You have {{PLURAL:$1|item|items}} on your
watchlist, including talk pages.'
'watchlistcleardone' => 'Your watchlist has been cleared.
{{PLURAL:$1|item was removed|items were removed}}.'
'watchdetails' => '* {{PLURAL:$1|page|pages}} watched not counting talk pages
* [[Special:Watchlist/edit|Show and edit complete watchlist]]
* [[Special:Watchlist/clear|Remove all pages]]'
'watchlistcontains' => "Your watchlist contains {{PLURAL:$1|page|pages}}."
I tried to translate last one but PLURAL didn't work correctly.
With best regards,
Eugene.
SVN trunk r14845 renames the "revisionasofwithlink" message to
"oldrevisionnavigation" and alters the format, adding a new parameter
and making the arrangement a little saner given the new information
available to the message.
Rob Church
Undeletedfiles ($1 file(s) restored) and undeletedrevisions ($1
revisions restored) (both Messages.php) seems as candidates as well.
Sorry for not spotting this in time to send it all in one mail.
/Susanna Björverud (Sannab)
Should not Undeletedrevisions-files (Messages.php) take advantage of
{{plural}}? Current text: $1 revisions and $2 file(s) restored
/Susanna Björverud (Sannab)
New message in SVN trunk, r15310:
"viewpagelogs" => "View logs for this page"
Links to the Special:Logs view for the relevant page, appears in the
subtitle on page histories.
Rob Church