Closed Bug 870391 Opened 12 years ago Closed 12 years ago

Add attachments on translated articles

Categories

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

All
Other
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: regagnon, Unassigned)

References

Details

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

What problems would this solve? =============================== I started to translate this page in French (about Firefox' Page Inspector) https://developer.mozilla.org/fr/docs/Outils/inspecteur It contains images with text. I wanted to upload screenshots from the French version of Firefox with translated explanations. But I couldn't add an attachment from the translation interface, nor reference an attachment from the original article with CKEditor. Who would use this? =================== Translators could translate images, or add localized screenshots of Firefox / Firefox OS. What would users see? ===================== In the translation edit form, there should be the same "Attach files" form as the one on the original article edit interface. I think we should see attachments from the original article separated from the attachments of the translated article. What would users do? What would happen as a result? =================================================== Translators could add new attachments and reference them in the article. We should also be able to reference attachments from the original article in CKEditor. Is there anything else we should know? ======================================
This needs to be added into the backlog
Priority: -- → P1
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/badf91f434b13613bbf673af034eb1c1c40f0b1d fix bug 870391 - Allow attachments in translations https://github.com/mozilla/kuma/commit/d1c1adc282cb4d88d275e66ba86cd7bb7ee6b7c6 Merge pull request #1182 from darkwing/attach-translate-870391 fix bug 870391 - Allow attachments in translations
Status: UNCONFIRMED → RESOLVED
Closed: 12 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.