Extension talk:Translate

Jump to navigation Jump to search

About this board

Archive.


Disabling fancy proofreading effects

5
Summary by Nikerabbit
if ( $( document.body ).is( '.mw-special-Translate' ) ) { $.fx.off = true; }
Kranix (talkcontribs)

Is it possible to disable the 'smooth' downward scrolling each time a proofreading is saved? Proofreading can be done rather quickly if most translations are correct, so the time waiting for this effect to finish is not insignificant.

Nikerabbit (talkcontribs)

The scrolling event is very fast and non-disturbing for me (it takes longer to download the message documentation which I usually want to see). Is this not the case for you?


Without scrolling the window would eventually go out of viewport, and without any smoothness it can be confusing that a scroll actually happened.

Kranix (talkcontribs)

It is quite fast, perhaps 0.3 seconds or so. It's not much, but does add up when proofreading many short items. The documentation loads instantaneously for me. I can see quite easily when a scroll has happened, so I'd just like an option to turn it off. A bit of CSS would probably accomplish it, but I don't know CSS.

Nikerabbit (talkcontribs)

You could add something like the following to your common.js to disable all animations on the page.

if ( $( document.body ).is( '.mw-special-Translate' ) ) { $.fx.off = true; }
Kranix (talkcontribs)

Thank you. This works.

Fanatikvoice (talkcontribs)

Hi, i installed MediaWiki_Language_Extension_Bundle, add in config default settings, and i not translate page.

I make page special tag <translate> -> return page, and no see link "Translate this page", instead i see link "Make translate the page".

Pls help me.

Reply to "Is not Translate this Page"

Avoid this is a translated version advice

4
151.40.197.208 (talkcontribs)

Is there a way to avoid the "This page is a translated version of the page XXX" message inside the translated pages? I'm using the extension for a documentation site, and I'd like to remove it, at least for not logged users.

Clump (talkcontribs)

For indiscriminate removal you could add a CSS rule to not display it:

.mw-pt-translate-header {
   display: none;
}
151.40.197.208 (talkcontribs)

Thanks for the answer, but I'd like to have the information when logged, but I would like no to show it to the people who just consult the site

Nikerabbit (talkcontribs)

You could use JavaScript to make it visible again to logged in users.


There is no way to change this with configuration only.

Reply to "Avoid this is a translated version advice"

Translate Plugin is not loading the Suggestions on the "right side" of the translate view

7
80.153.99.108 (talkcontribs)

I just set up a frash mediawiki installation and installes all i needed for translating my wiki and the content. manual translations just working like expected but in that view i do not get any suggestions shown? Maybe there is any logfile i could check or is that due to a lack of configuration? (it is pretty much default). Im just wondering that is show forever "Loading..." and no content is shown as in some screenshots of that plugin.

Tuxxic (talkcontribs)

Did you configure TTMServer in the LocalSettings.php ? Link : Help:Extension:Translate/Configuration/fr

$wgTranslateTranslationServices = array(); $wgTranslateTranslationServices['TTMServer'] = array( 'database' => false, // Passed to wfGetDB 'cutoff' => 0.75, 'type' => 'ttmserver', 'public' => false, );

91.48.253.216 (talkcontribs)

that is configured in the Translate.php file like in the default with that 4 entries, so i guess i do not need to do that again in the LocalSettings file, or?

Tuxxic (talkcontribs)

You won't know unless you try, inmy opinion ;)

91.48.246.166 (talkcontribs)

well that did not help is always stays at "loading..."... any other ideas?

Cloud668 (talkcontribs)

I am also having a similar issue on 1.31/MLEB 2018.07 (PHP 7.2.9 cgi-fcgi and on IIS if that matters for whatever reasons), but in my case, the translation aids column is loading fine for page translations but not file based message groups, which only ever showed the "Loading..." string. I've tested some of the same files along with the custom FFS/YAML group configs on an older wiki I have (1.28/MLEB 2016.10/PHP 5.6.11 fpm-fcgi on Ubuntu) and it worked fine there. Both wikis are using the default DB TTM.

On the older wiki, I noticed that the column only loaded after running createMessageIndex.php, but running that on the newer one didn't really help solve the problem.

I'm not sure what could be causing the issue on the newer wiki. Any help is appreciated.

Cloud668 (talkcontribs)

Digging a little into the access logs, it seems that in my case, the problem that the aids never loaded was that the translationaids API call for all file based messages for some reason only ever returns this:

"code":"nomessagefortitle","info":"Title does not correspond to a translatable message"
Reply to "Translate Plugin is not loading the Suggestions on the "right side" of the translate view"

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

2
89.82.208.37 (talkcontribs)

Hello,

Please help,

I am using Mediawiki 1.30

and Language Extension Bundle MediaWikiLanguageExtensionBundle-2018.03.tar.bz2

When I try to translate this page,

https://polyglotclub.com/wiki/index.php?title=Special:Translate&group=page-Test-translate-new1&action=page&filter=&language=fr

I've enabled anonymous translating, so you can check ($wgGroupPermissions['*']['translate'] = true;)

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 Sizzle.select (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:38)

[...]

"

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)
Reply to "Error : "Saving the translation failed: This namespace is reserved for content page translations.""

A Bug in the tool associated with heading

2
Summary by Nikerabbit
Ranjithsiji (talkcontribs)

If I start a new translation using this tool it will not ask for the new title of the new article in new language instead it uses the title from source language resulting a lot of articles created in the foreign language in a wiki. for example, I try to translate an article from Hindi to Engish in English wiki it will start the article title as the title in Hindi. Resulting creating an article with a title in Hindi in English wiki. The UI does not look like we can edit the title. A popup box or an intermediate title asking box is helpful to solve this problem.

Nikerabbit (talkcontribs)

Are there Active steps planned for the internationalization of category names?

2
Summary by Nikerabbit

Some plans yes, not very active. It is a question of MediaWiki core rather than Translate.

Atef81 (talkcontribs)

I am starting a multilingual environment that will have mainly 4 languages. The problem is that the language that will have the most content is Arabic, and my aim is to get as much content translated to the other languages.

When I tried the Translate extension, it worked, but having the categories names in Arabic then "/en" and "/fr" is not practical as non Arabic speakers will find it impossible to understand.

I checked several forums and read that there are steps in the pipeline to rectify this. However, I can't find enough information about this on the Extension official page.

I am trying to start from a page like this and reach an end result like this, where page title and category names are translated to the article language.

Is this likely to be an option soon, or I need to setup a family of wikis that share the same resources like this Mediawiki manual?

@Nikerabbit

Nikerabbit (talkcontribs)

Thanks for asking!

Due to possible naming conflicts, it's not a good idea to translate the actual page titles, unless you disambiguate them with a language code anyway.

But what you can do is to use the feature to translate the (category) page title. This does not affect the URL of the page, nor any links to that page. However, there are feature requests for MediaWiki core to use this translated title in links, including the category list at the bottom of the pages. It is not clear, though, when these will happen. I believe the features are not controversial, but some performance concerns must be taken into account while implementing them.

Some links:

Error using ElasticSearch in 1.27

4
Summary by Nikerabbit

ElasticSearch backend is not working on MediaWiki 1.27 and MLEB. Recommending to upgrade MediaWiki to use ElasticSearch backend.

Lsilverman (talkcontribs)

I'm running MW 1.27 with CirrusSearch+Elastica, which requires ElasticSearch 1.X. Cirrus and Elastica are pinned to the REL1_27 branches.

My wiki emailed me the following error upon attempting to translate my first page:

PHP Fatal error:  Call to undefined method Elastica\Query\BoolQuery::addFilter() in /var/www/devmediawiki-1.27/w/extensions/Translate/ttmserver/ElasticSearchTTMServer.php on line 282

LocalSettings.php portion looks like this:

$wgTranslateTranslationServices['TTMServer'] = array(
        'type' => 'ttmserver',
        'class' => 'ElasticSearchTTMServer',
        'cutoff' => 0.75,
        /*
         * See http://elastica.io/getting-started/installation.html
         * See https://github.com/ruflin/Elastica/blob/master/lib/Elastica/Client.php
        'config' => This will be passed to \Elastica\Client
         */
);
Lsilverman (talkcontribs)

Tracing the problem further, I see that REL1_27 of Elastica includes via composer ruflin/elastica 2.3.1.

elastica 2.3.1's version of Elastica/Query/BoolQuery.php does not contain the function addFilter().

Nikerabbit (talkcontribs)

Unfortunately this incompatibility has not been caught in our testing. Given 1.29 is soon going to be released, which means we are going to drop support for 1.27 from MLEB and Translate, I would encourage you to start planning for an upgrade and use the database backend for translation memory for the time being.

Lsilverman (talkcontribs)

We use Active Directory and LDAP. The LDAP auth plugins have not been updated in some time, and as a result we are stuck on 1.27.

Translation in the source language, English!

2
Summary by Nikerabbit

Manual:$wgPageLanguageUseDB can be used to change page source language.

Donxello (talkcontribs)

Hi, we have an English Wiki but a German article to be translated. By default the extension marks the article as English and consequently we get

Translations to this language in this group have been disabled. Reason:

English is the source language of this page.

Any ideas how to mark this article as German and how to allow translations in the source language?

Thanks

Tristan

Nikerabbit (talkcontribs)

Hopefully you have recent enough MediaWiki to enable Manual:$wgPageLanguageUseDB in LocalSettings.php. Then you can use this feature to change the page content language to German. But you should do that before marking the page for translation.

Summary by Nikerabbit

An issue with older versions of MediaWiki, no longer present in newer versions as far as I know.

67.244.49.134 (talkcontribs)

(Moved from support desk and modified) I have translate installed on my wiki, but when I try to add a translation for a page I get the following error. Saving the translation failed: Unknown error: "tpt-unknown-page" FuzzyBot also isn't running when I mark a page for translation. Running runJobs.php did nothing. Running showJobs.php gave the result 0. Any help would be great. Thanks.

Tuxxic (talkcontribs)

Hi,

Did you run runJobs.php from your actual PHP CLI instead of using an extension like MaintenanceShell ?

I had the same problem but running from CLI solved it.

In fact, in my case I'd like to runJobs eachtime I mark a page for translation, since it isn't done automatically ... :)

This post was hidden by 24.39.1.139 (history)
24.39.1.139 (talkcontribs)

I ran it using SSH.

2002:43F4:3186:1234:35AE:218:4B7:62E5 (talkcontribs)

Please help me.

Nikerabbit (talkcontribs)

So if runJobs.php doesn't work, does running extensions/Translate/scripts/createMessageIndex.php work?

24.39.1.139 (talkcontribs)

That worked

24.39.1.139 (talkcontribs)

FuzzyBot still isn't creating the /en subpages though.

Nikerabbit (talkcontribs)

I don't have much info, so my best guess is that either the JobQueue is seriously broken and not running jobs, or there is some kind of error that prevents Translate from adding jobs to the queue. Enabling PHP error reporting as well as logging exceptions could help to identify the cause. For example:

error_reporting( E_ALL | E_STRICT );

$wgShowExceptionDetails = true;

$wgDebugLogGroups['exception'] = ini_get( 'error_log' ); 

$wgDebugLogGroups['error'] = ini_get( 'error_log' );

$wgDebugLogGroups['fatal'] = ini_get( 'error_log' );

Tuxxic (talkcontribs)

Edit : So here is what I get in my PHP error log after :

  • Adding a new chunk of text
  • Marking therefore the page for translation
  • then trying to translate it afterwards

I don't experience the problem if I update an already existing message group, if it can help you.

Thanks for advice on error logs :)

2017-05-03 12:01:19 SERVERNAME database-name: [3f588d59648bf5725b6fb31e] /index.php?title=Sp%C3%A9cial:PageTranslation   DBUnexpectedError from line 2866 of C:\mediawiki-path\includes\libs\rdbms\database\Database.php: MWCallableUpdate::doUpdate: Cannot flush snapshot because writes are pending (JobQueueDB::doBatchPush).

#0 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1092): Database->flushSnapshot(string)

#1 [internal function]: LoadBalancer->{closure}(DatabaseMysqli)

#2 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1390): call_user_func_array(Closure, array)

#3 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1100): LoadBalancer->forEachOpenMasterConnection(Closure)

#4 [internal function]: LoadBalancer->beginMasterChanges(string)

#5 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(176): call_user_func_array(array, array)

#6 [internal function]: LBFactory->{closure}(LoadBalancer, string, array)

#7 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactorySimple.php(134): call_user_func_array(Closure, array)

#8 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(179): LBFactorySimple->forEachLB(Closure, array)

#9 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(200): LBFactory->forEachLBCallMethod(string, array)

#10 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(262): LBFactory->beginMasterChanges(string)

#11 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(225): DeferredUpdates::runUpdate(MWCallableUpdate, LBFactorySimple, integer)

#12 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(133): DeferredUpdates::execute(array, string, integer)

#13 C:\mediawiki-path\includes\MediaWiki.php(891): DeferredUpdates::doUpdates(string)

#14 C:\mediawiki-path\includes\MediaWiki.php(720): MediaWiki->restInPeace(string)

#15 C:\mediawiki-path\includes\MediaWiki.php(739): MediaWiki->{closure}()

#16 C:\mediawiki-path\includes\MediaWiki.php(543): MediaWiki->doPostOutputShutdown(string)

#17 C:\mediawiki-path\index.php(43): MediaWiki->run()

#18 {main}

Nikerabbit (talkcontribs)
Tuxxic (talkcontribs)

In my case, 1.28.2, but I experienced it also on 1.28.0.

113.172.20.5 (talkcontribs)

Hi Nikerabbit,

I got same problem Saving the translation failed: Unknown error: "tpt-unknown-page"

Wiki version 1.28.1

Use extensions/Translate/scripts/createMessageIndex.php is OK, but translate new page doesn't work

Nikerabbit (talkcontribs)

I don't know if this is specific to 1.28, but I just tried with MediaWiki vagrant on a clean install, using default MLEB configuration, and I did not have this problem.

Tuxxic (talkcontribs)

Thanks for testing.

Would you be interested in the list of my extensions installed, in order to see which one might be the culprit then ?

Nikerabbit (talkcontribs)

There is some info at https://phabricator.wikimedia.org/T100085 about different but possible related error message. It says it would be about exceptions.

I also can reproduce "Cannot flush snapshot" errors on my wiki now, so let's see if I can debug further.

171.233.234.227 (talkcontribs)

Thanks for debug Nikerabbit

ShInKurO (talkcontribs)

Hi all,

I've installed Translate extension (2017.07) on my wiki (mediawiki 1.27). When I try to translate a translable article the translation progressbar of the GUI doesn't go on when I press "Save translation" and I don't obtain any translation of my page after I've finished to translate at all. I've configured $wgJobRunRate to 0 and setted from console configuration of my hosting the cron job php script as written on mediawiki documentation (I cannot access to console).

Any idea about how solve this problem?

Thanks in advance!

Nikerabbit (talkcontribs)

Please open a new thread and check why the saving of the translations is failing, for example using PHP logs or your browser's developer tool and network tab.

ShInKurO (talkcontribs)

new thread opened! :)