Talk:MediaWiki Language Extension Bundle

Jump to navigation Jump to search

About this board


Create a self-installing Multilingual Mediawiki bundle

2001:B07:6443:2E8F:D1AF:CA79:4A5F:4089 (talkcontribs)

Instead of providing extensions into a bundle, could be interesting to have a ready to install complete version of updated Mediawiki with pre-installed extensions provided with an installer to make a clone of a Wikipedia multilingual site

Nikerabbit (talkcontribs)

This is not in scope of our work.

Reply to "Create a self-installing Multilingual Mediawiki bundle"

LocalisationUpdate - already part of 1.32?

AssetDenmark (talkcontribs)

When I tried to upload these it looks like LocalisationUpdate already exists? It is however not shown in the Specialpages:Version? Can anyone explain, do I need to add this in localsettings.php ?

wfLoadExtension( 'LocalisationUpdate' );

$wgLocalisationUpdateDirectory = "$IP/cache";

Nikerabbit (talkcontribs)

If you took the MediaWiki tarball, it includes some most often used extensions, including LocalisationUpdate. But it doesn't enable or configure them by default.

AssetDenmark (talkcontribs)

Thanks - I was just confused by this (thinking that I had broken everything), LocalisationUpdate does not appear in the special:version pages.

It would be kind of cool if there was an "unused" Extensions function? That could be done neatly, by using the version and gitinfo.json files. With a bit of work the Extension install process could be in a template and automated... if only I had the time!

Reply to "LocalisationUpdate - already part of 1.32?"

Page content language matching user prefs?

PatrikRoy (talkcontribs)

That bundle is really impressive, and all seems to work well on my wiki. Made some translations without problems.
My only concern is... the translated pages doesn't display by default in the language set by the user.
i.e. if a Russian user come on my english wiki, has set "Russian" in his language Preferences, and reads a page that has a translated subpage /ru, shouldn't the wiki displays that /ru page first for him?
Maybe I'm missing a parameter? Thanks for any advice.

Nikerabbit (talkcontribs)

Due to complicated reasons it is hard to automatically redirect users to their language. But you can use Special:MyLanguage/Pagename to create such links that will redirect to that version (if it exists).

Reply to "Page content language matching user prefs?"
Fanatikvoice (talkcontribs)

Hi, when I include parameter (" $ IP /extensions/Translate/Translate.php" ;) in LocalSettings.php, my Wiki is not working. Downloaded the latest version from 2018.10

Nikerabbit (talkcontribs)

Can you describe how it is not working? Error messages? Blank page? Make sure that those spaces inside "" are not actually there.

Kghbln (talkcontribs)

I find the TranslationNotifications pretty useful and I wonder why this is not included in MLEB. Well there is probably a reason, but ... ;) I personally find it more useful than e.g. CleanChanges. Not saying that the latter is less useful. However in the translation context...

Nikerabbit (talkcontribs)

No particular reason I suppose. Perhaps I thought that no other wiki has such amount of translators that it would be useful. I have to say though that the extension is not well maintained and has severe issues.

Thanks for reminding about CleanChanges... I should propose dropping it from the bundle.

Kghbln (talkcontribs)

Fair enough, though I think it is also very much useful if you have a wiki with little but irregular appearing translatable content or with irregular appearing translators.

"not well maintained and has severe issues". This scares me a bit now. If you think that it should not be used in production ...

Nikerabbit (talkcontribs)

It's probably fine for your wiki, have look at Phabricator. It has some issues sending notices to a lot of recipients.

Kghbln (talkcontribs)

Yeah, I have a maximum of about 10 translators. I am somewhat relieved now. Indeed this extension needs some love when looking at phabricator.

Reply to "Include TranslationNotifications?"

Possible confusing instructions for installation?

Summary by Nikerabbit
Djruess (talkcontribs)

Under "Add/update your LocalSettings.php" it states "Near the end, you have to place the configuration lines given above (pick from one of the two sections)..."

To what "configuration lines given above" are they referencing? It could just be user error, but I don't see what it's talking about. Please help?


Djruess (talkcontribs)

So think I realized what they are talking about. For those who are confused like me.

You can either copy the instructions from each extension into your LocalSettings.php file - so for example: when you are installing Babel, can go to Babel's instructions and copy wfLoadExtension( 'Babel' ); into your LocalSettings.php file . . . and do that for each of the extensions in the bundle. (Doing this is considered the first section that you could pick from, when it says "(pick from one of the two sections)").


You can simply copy the instructions they give under the "Add/update your LocalSettings.php" header - the instructions which includes all of the lines-of-code you need to put in your LocalSettings.php. (Doing this is considered the second section that you could pick from, when it says "(pick from one of the two sections)").

Nikerabbit (talkcontribs)

There used to be two ways to define $EXT, which is no longer needed with wfLoadExtension()

Saving the translation failed: This namespace is reserved for content page translations

Summary by Nikerabbit

Caused by an issue with job queue.

Vscheideck (talkcontribs)


Please help,

I am using Mediawiki 1.30

and Language Extension Bundle MediaWikiLanguageExtensionBundle-2018.01.tar.bz2

When I try to translate this page,

I get the following errors :

on the screen :

Saving the translation failed: This namespace is reserved for content page translations. The page you are trying to edit does not seem to correspond any page marked for translation.

In the javascript console :

Uncaught RangeError: Maximum call stack size exceeded

    at jQuery.fn.init.push (<anonymous>)

    at superMatcher (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:36)

    at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:38)

    at Function.Sizzle (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:12)

    at Function.jQuery.find (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:141)

    at jQuery.fn.init.find (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:41)

    at jQuery.fn.init (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:43)

    at new jQuery.fn.init (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:141)

    at jQuery (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:1)

    at MessageTable.resize (<anonymous>:90:664)

I've tried to disable all other extensions.

My LocalSettings.php :

wfLoadExtension( 'Babel' );

wfLoadExtension( 'cldr' );

wfLoadExtension( 'CleanChanges' );

$wgCCTrailerFilter = true;

$wgCCUserFilter = false;

$wgDefaultUserOptions['usenewrc'] = 1;

wfLoadExtension( 'LocalisationUpdate' );

$wgLocalisationUpdateDirectory = "$IP/cache";

require_once "$IP/extensions/Translate/Translate.php";

$wgGroupPermissions['user']['translate'] = true;

$wgGroupPermissions['user']['translate-messagereview'] = true;

$wgGroupPermissions['user']['translate-groupreview'] = true;

$wgGroupPermissions['user']['translate-import'] = true;

$wgGroupPermissions['sysop']['pagetranslation'] = true;

$wgGroupPermissions['sysop']['translate-manage'] = true;

$wgTranslateDocumentationLanguageCode = 'qqq';

$wgExtraLanguageNames['qqq'] = 'Message documentation'; # No linguistic content. Used for documenting messages

wfLoadExtension( 'UniversalLanguageSelector' );

Nikerabbit (talkcontribs)

These kind of issues are usually caused by JobQueue. Try running maintenance/runJobs.php or extensions/Translate/scripts/createMessageIndex.php manually to confirm.

Vscheideck (talkcontribs)

thanks but it did not solve the problem

Nikerabbit (talkcontribs)

Right now it says message group page-Test-translate is not found. Are you sure have marked the page for translation or did you remove it after posting?

Vscheideck (talkcontribs)
Nikerabbit (talkcontribs) (talkcontribs)

Yes, you were 100% right, the job was failing, it's corrected now, :D (talkcontribs)

thanks for your help

Nikerabbit (talkcontribs)

Good that you were able to figure it out :)

KarinJ77 (talkcontribs)

I have question reagarding the translation statsitics. I know I can see % translated messages and number of translated messages. But is there anyway that I can see the number of words translated by language in my wiki?

Nikerabbit (talkcontribs)
KarinJ77 (talkcontribs)

Ok, and there is no way in related db tables by sql just do some wordcount either, if you know where to look?

Nikerabbit (talkcontribs)
Reply to "number of words translated?"

Problems with $wgTranslateBlacklist = array();

Hutchy68 (talkcontribs)

Updated a MW 1.23 to 1.27, now using PHP 7.0.15. Updated all the extensions including this one to the latest release. Ran php update.php. Everything works, but $wgTranslateBlacklist = array(); seems to be getting ignored completely. There is no way to translate /en pages now if needed.

It I try to update the $wgTranslateBlacklist = array(); to the example and modify the message English is the source language of this page. to something else to test the array but it will not change the message. What is causing an issue is I need to modify en pages. Specifically, categories to a trailing /en so they don't appear in the none /en categories. There aren't too many translated pages so tweaking the categories on those pages isn't an issue.

Other languages, the extension is fast and works great. En and the page starts to load, but the message Translation of the wiki page Foo from English (en). changes to the top alphabetical page of message groups, Translation of the wiki page A-foo from English (en). There is no way to edit message groups in en at this point.

Hutchy68 (talk) 21:14, 27 January 2017 (UTC)

Nikerabbit (talkcontribs)

There has been an intentional change in the code that blocks updates to the source language by default. I was not aware that there exists an use case that would require enabling edits in the source language.

Hutchy68 (talkcontribs)

Thanks, I thought there might have been a coded change. The docs still show the old method. Anyway, I see there was an additional parameter added in the newer version.[[Category:Category Name{{#translation:}}]] adds the correct /lang to the end of the categories automatically based on the language subpage of the translation. Hutchy68 (talk) 15:00, 18 February 2017 (UTC)

Reply to "Problems with $wgTranslateBlacklist = array();"
This, that and the other (talkcontribs)

The page says "MLEB has a regular release schedule, so that you can easily stay on the cutting edge with the constantly improving language support." However, it doesn't say what that regular release schedule is. The Phabricator project description says it is released every three months, but that doesn't seem to be adhered to very well, judging from the release list.

Could this sentence be clarified?

GerardM (talkcontribs)

Hoi, I have no author of this.. I see acronyms like MLEB, it is however a WMF thing. There is no link to the project description. I have not been involved in its creation so I leave it to whoever to decide about its veracity. Thanks, GerardM (talk) 12:31, 1 January 2017 (UTC)

This, that and the other (talkcontribs)

Hi Gerard :) It sounds like you might have thought I posted on your talk page... this is in fact the talk page for MLEB itself :)

Nikerabbit (talkcontribs)

It used to be every month. Nowadays it is every three months, trying to adhere 1/4/7/10 schedule. I am not sure whether it matters to the reader whether it is every month or every three months (opposed to, providing outdated information before I changed it). That can easily be checked from the release list as you did.

Reply to ""Regular release schedule""