New stuff to check

New stuff to check

Edited by another user.
Last edit: 18:52, 28 August 2012
Thread summary:[Link to] [Edit]
CLOSED This issue is closed by siebrand
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/BiblioPlus/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Carp/.git/ NO: Directory is still empty
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/CommentPages/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/ConfirmAccount/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Diagnosis/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Diff/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/ExtTab/.git/ NO: non standard i18n system.
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Genderize/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/GoogleCustomWikiSearch/.git/ NO: Directory is still empty
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/GlobalUserGroups/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/LightweightRDFa/.git/ NO: Directory is still empty
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/MathSearch/.git/ NO: No valid i18n file yet
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Mpdf/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Poll/.git/
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/SemanticPageMaker/.git/ NO: non standard i18n system.
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/SemanticTitle/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/StickToThatLanguage/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/SubpageSortkey/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/Tabber/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/WhiteSpace/.git/ Done Done
  • Initialized empty Git repository in /resources/projects/mediawiki-extensions/extensions/WikiObjectModel/.git/ Done Done
Nike (talk)‎10:45, 23 July 2012

Also mediawiki/extensions/FacebookOpenGraph , previously FBConnect on SVN, where it's been inactive for a while (because it had actually moved to GitHub), dev interested in TWN support.

Nemo (talk)‎23:24, 31 July 2012

It would be nice to have support for the following extensions:

In addition to the above, please feel free to drop support for regexBlock and spamRegex — they are and have been bitrotting for a while and the same functionality (and lots more!) will be provided by Phalanx in the near future.

Jack Phoenix (Contact)‎13:35, 17 August 2012
Edited by another user.
Last edit: 22:32, 18 August 2012

Many of these extensions have missing message documentation and major i18n issues. I've made you aware of these in the past, and you've chosen another route. If the issues are resolved, we'll gladly add support for the extensions. See mw:i18n for more details. As you indicate to be a native Finnish speaker, I'm sure you'll appreciate many of the recommendations made in that page.

We've also started to more closely review patch sets in Gerrit and connecting consequences (not supporting L10n for code here) to non-compliance.

Siebrand‎10:38, 18 August 2012

"Missing message documentation" isn't technically correct, as many things are documented (see, for example, mw:Extension:Comments#Internationalization, mw:Extension:NewSignupPage#Interface messages, mw:Nimbus skin#Internationalization...), they just aren't documented in the format preferred by TWN.

Just like in the past, I still disagree with the location and the format of message documentation; obviously having documentation is useful, and that's something I've never been denying. Internationalization files can get pretty large for an extension that has many (say, over 50) messages. I feel that we should keep only linguistic content in i18n files and not make 'em a strange mess of translations and documentation. You also can't include images on the i18n file in the same way you can include them on wiki pages. (Well, you could base64-encode them as data: URIs, like how the ResourceLoader does for images...but you get the idea. When you have something like [[File:Foo.jpg|something goes here]] without any more specific context in an i18n file, you don't really know what Foo.jpg is, where it is stored, etc.)

Just what do you mean by "major i18n issues" and can you provide specific links to these? I'm not aware of any such issues. In fact, I've gone to great lenghts in making these extensions translatable, at least if you compare them to their original state, in which many of them had hard-coded English and/or misleading UI messages, etc.

Also, what is the "problem" with Phalanx? Like I wrote earlier, it is already supported as a Wikia extension, so why cannot it be supported as a normal MediaWiki extension? Or are the standards different for Wikia extensions? I would like to invite you to compare the files SpecialPhalanx.body.php and SpecialPhalanxStats.php between upstream and Wikia; upstream SpecialPhalanx.body.php, Wikia SpecialPhalanx.body.php, upstream SpecialPhalanxStats.php and Wikia SpecialPhalanxStats.php. Please pay specific attention to the functions PhalanxPager::formatRow (in SpecialPhalanx.body.php), PhalanxStats::block_stats/PhalanxStats::blockStats and PhalanxStats::showForms() (in SpecialPhalanxStats.body.php).

Finally, it's worth noting that supporting an extension in TWN — whether it has the documentation or not and whether said docs are in the format preferred and accepted by TWN or not — is useful for everyone. I'm not going to lose my night's sleep over these kind of things, but it does make life harder for the average end-user who would like to have i18n available on their site. History has shown that people will find a way around this political limitation — but the question is should they focus on that or something more productive.
I don't see message documentation as a major deal-breaker, and I don't understand why it would be for someone. For years, things worked just fine without. Sure, having it is a nice additional bonus, but it shouldn't be the main focus.

Jack Phoenix (Contact)‎20:55, 20 August 2012

If you're ok with managing message documentation and submission of translations by yourself in your own way that's fine, it just won't be thrown on TWN translators who are used to higher standards. This is not worth discussing, I think.

Nemo (talk)‎21:07, 20 August 2012
 

Our translators need good message documentation to make good translations. Often it is unclear - because out of context - if a message is a noun or a verb, if it is a label or a button text etc etc.

I know that you do not like the qqq section inside the i18n file, but they do not really hurt. Really big extensions like FlaggedRevs withs hundreds of messages works on WMF without any problems with the qqq section. You are free to do your own message documentions on mediawiki.org. Thats great. But TWN needs the message documetation shown up in the translation process directy, not on mw.org.

Images/screenshots can be uploaded to Wikimedia Commons and included in the message doc. TWN is using InstantCommons for this.

As the one - besides Siebrand - who adds (new) extension I say clearly: I will not add an extension without proper message doc.

Oh I forgot one option: Feel free to invent a complete new message doc system which is better, for you and us :-)

Raymond‎08:34, 21 August 2012

Raymond, thank you for this well thought-out and polite reply. :-)

I have plenty of projects on my plate, but I'll definitely need to look into writing an awesomer message documentation system in the future.

But until that...can we now fulfill my request?

Jack Phoenix (Contact)‎17:12, 21 August 2012
Edited by author.
Last edit: 13:51, 22 August 2012

Thanks for adding the message doc, looks offhand OK. But I wonder why I don't see these commits on Gerrit? These are Gitweb links only. It's impossible for me to track changes in those files if they are not going through Gerrit. Is bypassing Gerrit still possible for extensions not used by WMF?

Raymond‎06:58, 22 August 2012

It still appears to be possible. I've made Chad aware of it multiple times.

Siebrand‎13:16, 22 August 2012
 

Looks like within 2 weeks or so pushing directly to master will no longer be possible in gerrit repos.

Siebrand‎13:19, 22 August 2012
 
Edited by 2 users.
Last edit: 09:29, 8 September 2012

Progress:

  • Done Done LinkFilter
  • Done Done SiteMetrics
  • Done Done Phalanx
  • Done Done VoteNY
  • Done Done Comments

Not done yet:

  • NewSignupPage: 2 messages are prefixed with 'shout-', 1 w/o any prefix. Please change them to 'newsignuppage-'-
Raymond‎07:39, 24 August 2012
 
 
 
 
 
 
 
Retrieved from "https://translatewiki.net/wiki/Thread:Support/New_stuff_to_check#New_stuff_to_check_26627"