Closed Bug 871252 Opened 11 years ago Closed 11 years ago

See original article's tags in translation interface

Categories

(developer.mozilla.org Graveyard :: General, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: regagnon, Unassigned)

Details

(Whiteboard: [specification][type:feature])

What problems would this solve?
===============================
Currently, while translating an article, translators needs to open a new tab for the original article, to read its associated tags.

This feature would help every pages to be tagged. Currently many new translated contents are missing tags.

Who would use this?
===================
Translators could speed up their works.

What would users see?
=====================
In the translation interface, the translators would see under the original content, the associated tags, at about the same position as the tag input.

What would users do? What would happen as a result?
===================================================
Translators could read the tags. If they feel the tag can be used on the translation, they will write it in the tag input.

This could be improved by allowing the translators to click on individual tag, to directly copy them in the tag input.

Is there anything else we should know?
======================================
I don't think that the original tags should be directly copied in the translation tag input. This would be OK for generic tags (i.e. 'HTML', or 'DOM'), but some tags needs to be translated. I fear that if the original tags are directly copied in the translation tag input, many translators will miss the input and add wrong tags on translations.
Commit pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/7a23965e0c63e7cbfe425cca7592b3332544f72f
fix bug 871252 - Show original doc tags in trans interface
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.