Add support for in-context localization

[bugzilla-to-github]

This issue was created automatically by a script.

Bug 1536884

Bug Reporter: @mathjazz CC: @flodolo, [email protected], @lliehu, @zbraniecki Blocker for: Bug 1303066 See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1303066

As part of Translate.Next rewrite we need to figure out the architecture of in-context localization: either we implement something completely different or fix bug 1303066.

[bugzilla-to-github]

Comment Author: @mathjazz

We should figure out what do with in-context l10n support first, let's do that in Q4.

[bugzilla-to-github]

Comment Author: @mathjazz

Over the last few months two groups of people have spoken in favour of re-implementing in-context localization:

• People how want to use it to localize their projects
• People who said they got attracted to Pontoon primarily by this feature (2 core contributors)

So let's do this. I'm leaving this bug open as a tracker and closing 1303066. We'll need a specification before moving forward.

We currently don't have a specific need for in-context l10n at Mozilla, hence the P5.

[bugzilla-to-github]

Comment Author: [email protected]

I was wondering if this means there currently is not in-context support with in pontoon? If so, are you aware that it is still mentioned on https://pontoon.mozilla.org/?

[bugzilla-to-github]

Comment Author: @mathjazz

Hi Fritz. That is correct - in-context l10n is not supported ATM.

And we should remove that block until it is.

[mathjazz]

If so, are you aware that it is still mentioned on https://pontoon.mozilla.org/?

Adding a note that this section has been removed a while ago.

[mathjazz]

Adding a note from an old document about a couple of features that are possibly related to in-context L10n:

Page translation: When you open a website and Pontoon has it's translation to your language, we could just load it and retranslate the page.

Feedback collector: Similar to those small vertical tabs that ask for feedback on certain websites, I can imagine an interface that users can use to submit feedback about copy and translations on the page they're currently viewing. Example flow: click the "feedback" tab, select the DOM element that you want to give feedback on, type the description of the issue ("a typo") or a suggestion for a new translation, hit submit. Behind the scenes, a request to Pontoon API is made and a new suggestion is recorded.