gmane.org.wikimedia.mediawiki.i18n

Re: removing messages from core

S Page — 2013-06-20T00:35:02

(Premature clicking)

https://gerrit.wikimedia.org/r/#/c/67233/ remotes the old-style login and
create account forms from core. The new forms have different messages, e.g.
no more colons in English labels and there's no more use of the  combined
"Log in / create account".  So I removed the old messages from
MessagesEn.php, MessagesQqq.php and messages.inc.

Raimond Spekking pointed out

 'userlogin' message is still used by the OpenID extension.
Good point, 'userlogin' is also used by MobileFrontEnd and some
unmaintained signup extensions.  I will prepare a patch that restores it.

I searched for message keys in single quotes and it seems the other
messages I removed (yourname yourpasswordagain userlogin userloginnocreate
nologin nologinlink gotaccount gotaccountlink userlogin-resetlink
createaccountreason ) are unused by the the extensions in 1.22wmf7.

* Should I restore those other messages as well?
* Is there a process for deprecated or obsoleting a message in core?
* Should I put something in MessagesQq

removing messages from core

S Page — 2013-06-20T00:22:15

https://gerrit.wikimedia.org/r/#/c/67233/ remotes the old-style login and
create account forms from core. The new forms have different messages, e.g.
no more colons in English labels and there's no more use of the  combined
"Log in / create account".  So I removed the old messages from
MessagesEn.php, MessagesQqq.php and messages.inc.

Raimond pointed out that the

 'userlogin' message is still used by the OpenID extension.

Maybe more of these very old messages are used by other extensions.Needs
investigation, partly revert recommended in the meantime.



Good point, it's also used by MobileFrontEnd (!), I'll submit a patch
restoring this message and ask on the i18n mailing list for guidance.

FWIW mw.org's I18n page and Manual:System_message#Creating_new_messages
don't say anything about extensions reusing core messages. I think they
should caution extension writers about relying on messages in core, and
instead define their own messages with a {{same}} template in Qqq. Or we
need to somehow identify "reli

Re: Why why /** Message documentation (Messagedocumentation)?

Niklas Laxström — 2013-06-17T20:42:46

Usually people add themselves to 'en' and 'qqq' if they bother at all.
The tool will add user names from translatewiki.net automatically and
retain existing < at >author tags.


Awesome.

  -Niklas

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Why why /** Message documentation (Messagedocumentation)?

S Page — 2013-06-14T21:11:37

On Tue, Jun 11, 2013 at 11:53 PM, Niklas Laxström
<niklas.laxstrom< at >gmail.com> wrote:


Ahh, so it more or less doesn't matter what's in the i18n.php section
headings since the tools rebuild the file. I expanded this step in
<https://www.mediawiki.org/wiki/Localisation#Update_of_localisation>.
I'm not sure it's worth telling people not to worry about something
they may never notice  :-) .

Another question: I add my name in < at >author comments to the 'en' and
'qqq' section headings.  Should I instead just put it in the doc
comments at the top of the file? (I authored the file so obviously I
did those sections.)  Presumably "the tools" add other names when they
generate from translatewiki.

Thanks, it's a huge piece of infrastructure that works so well we
don't think about it.

--
=S Page  software engineer on E3

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Language Engineering office hour on 2013-06-12at 17:00 UTC/10:00 PDT

Siebrand Mazeland (WMF — 2013-06-12T15:43:10

Reminder: This office hour will be in a little over an hour from the time
of sending.


On Thu, Jun 6, 2013 at 5:05 PM, Siebrand Mazeland (WMF) <
smazeland< at >wikimedia.org> wrote:

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Why why /** Message documentation (Messagedocumentation)?

Niklas Laxström — 2013-06-12T06:53:13

You are on the right track. English language sections are not managed
by translatewiki.net (Translate extension) so they retain the original
formatting.

For all other languages the tools regenerates the sections from
scratch which makes them all use consistent format. I don't see the
little repeating a worth of special casing it.


Not there as far as I know, but Translate extension is picky about the
formatting of the i18n files. But the language names are ignored on
reading, only the language code matters.

  -Niklas

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Why why /** Message documentation (Messagedocumentation)?

S Page — 2013-06-12T04:03:34

Almost every extension's i18n.php file has

/** Message documentation (Message documentation)
 * < at >author Some Person
 */
$messages['qqq'] = array(
    ...

Why repeat it?

Is it because the header for each language section is "/** French
(français)" , so Qqq is being consistent? But the English header is just
/** English.

Does some undocumented tool in maintenance/language rely on the format of
these headings?

Thanks for any insight.

Pre-releasing translatewiki.net iOS App

Or Sagi — 2013-06-11T14:51:13

Hi Everyone,

We are working on a mobile application for translatewiki.net, as a part of
our BSc final project in the Tel-Aviv Uni. We try to do our best effort to
make the perfectly handy, simple and professional way to use
translatewiki.net on the go.

We are super close to launch it publicly to the iOS app store.
If you have an iOS device (iphone, iPod or iPad), you are invited to be
among the first to see and test it, via "TestFlight". click this
invitation<http://tflig.ht/17EJVFz> and
you'll be approved.

You can also find our project on
Github<https://github.com/orsa/TranslateWikiApp-iOS>
.

Please send us your feedback.

Thanks,

Tomer T.
Or S.
_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Language Engineering office hour on 2013-06-12 at17:00 UTC/10:00 PDT

Siebrand Mazeland (WMF — 2013-06-06T15:05:35

Event Details

# Date: 2013-06-12
# Time: 1700-1800 UTC, 1000-1100 PDT
#IRC channel: #wikimedia-office on irc.freenode.net

The Wikimedia Language Engineering team [1] invites everyone to join the
team’s monthly office hour on June 12, 2013 (Wednesday) at 1700 UTC/1000
PDT in #wikimedia-office. During this session we would be talking about
some our recent activities and updates from the ongoing projects. The
provisional agenda is outlined below.

See you all at the IRC office hour!

Siebrand Mazeland
Product Manager Language Engineering
Wikimedia Foundation


Agenda

# Introductions
# Universal Language Selector - Phase 1 deployment was on Tuesday
2013-06-11 [2,3,4]
# Universal Language Selector - Phase 2 and later
# Q/A - We shall be taking questions during the session. Questions can also
be sent to "siebrand at wikimedia dot org" before the event, and will be
addressed during the office hour.

[1] http://wikimediafoundation.org/wiki/Language_Engineering_team
[2] https://www.mediawiki.org/wiki/Universal_L

MediaWiki Language Extension Bundle 2013.05 release‏

Amir E. Aharoni — 2013-05-29T15:22:18

Hallo,

I would like to announce the release of MediaWiki language extension
bundle 2013.05

* https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.05.tar.bz2
* sha256sum: 9aea5b1dac2b38e44284373c849241fc694c78caff1d3ca3b4e6e72d66f2ab12

Quick links:
* Installation instructions are at https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
  https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to https://bugzilla.wikimedia.org
* Talk with us at #mediawiki-i18n < at > freenode

Release notes for each extension are below.

    Amir E. Aharoni

== Babel ==
Only localization updates.

== cldr ==
CLDR was updated to version 23.1.

== CleanChanges ==
Only localization updates.

== LocalisationUpdate ==
No changes.

== Translate ==
The new translation editor in Translate is now considered stable. The
last month saw mostly polishing and bug fixes, changes in internals of
the extension and terminology was made more consistent.

Other notabl

Re: Fwd: Problem with translated templates

Federico Leva (Nemo — 2013-05-27T20:13:18

Niklas Laxström, 27/05/2013 21:59:

He fixed it by rewriting {{TNT}} with a Lua module.

Nemo

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Fwd: Problem with translated templates

Niklas Laxström — 2013-05-27T19:59:11

Did you get any new info or help in IRC, or does still need
investigation to find out the cause?

  -Niklas

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

[Language Engineering] Bug triage on Wednesday, May 29, 2013 at 1700 UTC/1000 PDT

Runa Bhattacharjee — 2013-05-27T05:49:17

What: Internationalization bug triage
Date: May 29, 2013
Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://hexm.de/r0)
Channel: #mediawiki-i18n (Freenode)
Etherpad: http://etherpad.wikimedia.org/BugTriage-i18n-2013-05
Questions can be sent to: runa at wikimedia dot org

Hello,

The Language Engineering team would like to invite everyone for the
upcoming bug triage session on Wednesday, May 29, 2013 at 1700 UTC
(1000 PDT).  During this 1 hour session we will be using the etherpad
listed above to collaborate. We have already listed some bugs, but
please feel free to add more bugs, comments and any other related
issues that you’d like to see addressed during the session. You can
send questions directly to me on email or IRC (nick: arrbee). Please
see above for event details.

Thank you.

regards
Runa

Fwd: Problem with translated templates

Guillaume Paumier — 2013-05-23T13:02:21

Hi,

I'm having an issue with translated templates, and I'm not sure if
it's a bug or just me being thick, so I'm hoping the i18n wizard can
help me :)

I've set up the following template for translation:
https://meta.wikimedia.org/wiki/Template:Tech_header

FuzzyBot has copied the source strings to the appropriate subpages,
for example https://meta.wikimedia.org/wiki/Translations:Template:Tech_header/3/en

However, https://meta.wikimedia.org/wiki/Template:Tech_header/en
hasn't been created. This causes {{Translatable navigation template}}
to fail and display a red link to [[Template:Tech_header/en]], which
means I can't call the translated template.

The same problem happens with
https://meta.wikimedia.org/wiki/Template:Tech_news_nav

I've temporarily reverted my edits to both templates because the
problem was breaking pages (I couldn't use {{TNT}} because the /en
subpage didsn't exist, but I couldn't use the normal template call
either because it showed <translate> tags, so I reverted).

Can anyone tell me

Re: Assigning tags to extension messages

Nick White — 2013-05-22T09:53:30

That's awesome and looks very useful, thanks S Page!

Nick

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Assigning tags to extension messages

S Page — 2013-05-21T19:01:25

I added a section "Messages that should not be translated" to
https://www.mediawiki.org/wiki/Localisation#Message_documentation , with
this information, plus the standard comments people appened to En, the
{{optional}} in Qqq, the system messageTypes.inc file, etc.

These are my observations of the conventions in use, so fix any mistakes!


On Tue, May 21, 2013 at 9:37 AM, Niklas Laxström
<niklas.laxstrom< at >gmail.com>wrote:

Re: Assigning tags to extension messages

Nick White — 2013-05-21T17:26:49

Thanks for the information. I am not particularly knowledgable about
how translatewiki.net works, so I didn't realise that
mediawiki-defines.txt file worked for extensions there too. It should
do exactly what I need, thanks a lot for the prompt reply.

Nick

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: Assigning tags to extension messages

Niklas Laxström — 2013-05-21T16:37:29

If your extension/skin is translated at translatewiki.net, you can
submit a patch against [1]. It has examples of that (search for
ignored). If you are talking about translating somewhere else, it
depends how you have configured the message group.

[1] https://git.wikimedia.org/blob/translatewiki.git/HEAD/groups%2FMediaWiki%2Fmediawiki-defines.txt

  -Niklas


--
Niklas Laxström

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Assigning tags to extension messages

Nick White — 2013-05-21T11:13:40

Hi,

I have an extension (a skin, actually, but functionally it's exactly
the same) which makes use of system messages to allow administrators
to add extra content to some areas of wiki pages. So by default the
messages are empty, and should never be translated.

You can see this in the Erudite.i18n.php change at
https://gerrit.wikimedia.org/r/#/c/62623/

I would like to mark these messages as not to be translated.
It looks like one can do this within the mediawiki core using tags;
http://www.mediawiki.org/wiki/Help:Extension:Translate/Group_configuration#TAGS

But I can't see an equivalent method for extensions. Does such a
thing exist? I plan to mention in the 'qqq' entries that they
shouldn't be translated, but it would be nice if they could be
tagged so they weren't shown in the translation interface at all.

If no such mechanism exists, what would be the best way of adding
it? Using message documentation templates, or adding the possibility
of something like a local mediawiki-defines.txt file for extens

Re: [Commons-l] Enabling the Translate and UniversalLanguageSelector extensions on Commons

Jean-Frédéric — 2013-05-10T17:13:24


Oh, I see. Thanks to them then - though I am indeed eager to hear more
about it...




It is from <
https://commons.wikimedia.org/wiki/Template:Centralized_discussion> and was
mentionned on the Village Pump.




Well, it is not in the sense I was not looking yet for the shower of
Support/Oppose. I thought we needed to have it fleshed out a bit using the
input of the i18n folks - but this was just how I saw the all thing, I am
probably mistaken.




I was actually planning a SiteNotice ^____^
_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n

Re: [Commons-l] Enabling the Translate and UniversalLanguageSelector extensions on Commons

Federico Leva (Nemo — 2013-05-10T17:00:39

Jean-Frédéric, 10/05/2013 18:37:

Noo it's just the ULS deployment plan by the WMF Language engineering 
team (we'll hear about it very soon).


The RfC s not even linked from 
<https://commons.wikimedia.org/wiki/Commons:Requests_for_comment>, I 
thought it wasn't officially open? It should just be advertised a 
little, with watchlist notices if needed.

Nemo

_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n