Page MenuHomePhabricator

[TUX] Buttons to insert non-translatable parts like parameters
Closed, ResolvedPublic

Description

As with the ↓ for translation memory suggestions, it could be useful to add a "button" to insert in the text are the missing parameters detected by the automatic warnings in the translation editor.


Version: master
Severity: enhancement
URL: https://translatewiki.net/wiki/Thread:Support/Enhancement_of_waring_messages

Details

Reference
bz38350

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:08 AM
bzimport set Reference to bz38350.
Nemo_bis created this task.Jul 12 2012, 2:50 AM

Use case: I'm a translator, I want to avoid writing manually the names of the parameters (and other markup maybe) in the messages because it's tedious, so when I can't or forget to copy and paste them from the source text or from the suggestion I want an easy way to insert them in my translation.

Changing importance from lowest to normal since this is THE shortcoming of this extension. As a matter of fact it should be actually be high or even more important. I am utterly astonished why there was no serious reaction from the coders to the thread on twn.n so far. However, I may be biased in this case.

Really, is it that hard to type "$1" or perhaps "%{foo}"? Given that the current insertions don't have accesskey, you would need to use mouse which takes a lot of time.

Did you ever have the chance to translate for e.g. EOL? Obviously not. This is not just about MediaWiki or FreeCol, it is about all projects supported by tw.n

So what is special in EOL?

Designs for adding non-translatable parts (such as parameters, or "magic words") were included in the design specification at http://commons.wikimedia.org/w/index.php?title=File:Translate-workflow-spec.pdf&page=14

(In reply to comment #5)

So what is special in EOL?

EOL, as well as OpenStreetMap and other Ruby on Rails applications, has alphanumeric variables, which make them prone to typos, and some (yes, they are) bad translators, translate the variables. Example of source text:

Article - %{dato_title} from %{supplier}.

Our check system already can identify variables. That would be a nice starting point for this.

The check system need rewriting anyway to be a proper API that TUX can use.

Change 83921 had a related patch set uploaded by Nikerabbit:
Initial support for insertables

https://gerrit.wikimedia.org/r/83921

Change 83921 merged by jenkins-bot:
Initial support for insertables

https://gerrit.wikimedia.org/r/83921

Is there more work needed, or can this be closed as RESOLVED FIXED as per comment 10?

http://laxstrom.name/blag/2013/09/18/insertables-in-translate-extension-make-translating-easier/ says GENDER, GRAMMAR and presumably all standard magic words are not covered yet. Should those be listed in separate bug report(s) or where else, and what about non-MediaWiki projects?

Feel Free to file New bugs for missing insertables if you think it will help to attract fixers for them. They are not going to make me add those any faster ;)

(In reply to comment #13)

Feel Free to file New bugs for missing insertables if you think it will help
to
attract fixers for them. They are not going to make me add those any faster
;)

Ok, I take this as a "not on bugzilla". :) Will add them somewhere else.