Project:Support desk

About this board

Welcome to the MediaWiki Support desk. This is a place where you can ask any questions you have about installing, using or administrating the MediaWiki software.

(Read this message in a different language)

See also

Before you post

Post a new question

  1. To help us answer your questions, please indicate which version of MediaWiki you are using, as found on your wiki's Special:Version page:
  2. If possible, add $wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 ); to LocalSettings.php in order to make MediaWiki show more detailed error messages.
  3. Please include the web address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
  4. To start a new thread, click the box with the text "Start a new topic".

The Translation tool has too many problems

1
Filipe46 (talkcontribs)

I already complained about that, made the ticket and everything. Yet, no solutions were presented.

The tool keeps flagging every single stretch of the text as having 100% to 96% unmodified text, thus blocking the publication of the article. Almost every translation keeps giving me the false-positive of it being an earlier version of the article, thus also impeding the publication of the same.

The tool never saves the infobox, thus forcing me to remake it every time I open the translation. It keeps losing entire paragraphs already translated, thus wasting my time in re-translating the same thing 3 or 4 times.

It also clashes auto translation with my translations, usually on links.

By clicking "Reply", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 4.0 License and GFDL.
Reply to "The Translation tool has too many problems"

help : cannot use a Tunit inside a syntaxhighlight

2
Wladek92 (talkcontribs)
TheDJ (talkcontribs)

There is no substitution inside syntaxhighlighting. It takes code as is and wikicode doesn't really do anything there (not really true, because categorization works, but that is because it happens outside of the rendering pipeline of highlighted fragments).