1243140 - Use Microsoft Terminology in translate view

Status: RESOLVED DUPLICATE of bug 1624557

(Webtools Graveyard :: Pontoon, defect, P3)

Description

[Matjaz Horvat [:mathjazz]]

1. Create and use a common mozilla glossary (a list of strings with translations) that all locales will translate in Pontoon. Should be expandable.

2. Make glossary terms highlighted in source string, with ability to insert their translations into textarea, like placeables. Translation should be displayed on hover?

Comment 1

[Matjaz Horvat [:mathjazz]]

In accordance with the TBX file format, each term should contain the following fields: 
- source term
- source term note (part of speech)
- source term description (definition)
- target term

Terminology should behave similarly as other localization projects in Pontoon. Localizers could add/review translations (target terms) in a familiar interface and also upload/download TBX files. To make it work, we need to simply add support for the TBX file format and put terminology files for all locales in a repository.

In the next iteration, we should allow localizers to also define new terms.

Comment 2

[Matjaz Horvat [:mathjazz]]

We should check licences and try to reuse these terminology collections, which are available in several languages:
https://mozilla.locamotion.org/projects/terminology/
https://www.microsoft.com/Language/en-US/Terminology.aspx

Comment 3

[Jarek Śmiejczak [:jotes]]

mathjazz: I think this feature could be a good point to start our migration into react or angular. We could start to create separate template that would share the same look with the current of "translate.html" . I can look into this if you won't mind.

Comment 4

[Matjaz Horvat [:mathjazz]]

I'm open for this. But please note that this is probably going to be a relatively small change in terms of Translation interface UI.

A term needs to be highlighted in the source string and its data from the terminology reference needs to be presented somehow, with the ability to insert the target term into translation textarea. Something similar as placeable, but visually differentiated.

Comment 5

[Jarek Śmiejczak [:jotes]]

:mathjazz,:pike,:adrian

So, as We discussed at the latest Water-cooling meeting, there are some unresolved legal concerns.
Support for MS Terminology was only a small part of my previous PR -> and most of work was mostly connected to https://bugzilla.mozilla.org/show_bug.cgi?id=1381959

However, as this feature landed in Our current OKRs, I feel We need to discuss again features required for MVP.

My initial idea:
I could start from creating small django-admin module in which Kekoa could import/edit terminology.
I feel that models and admin panel could land separately and later the import of tbx files.

However, that raises next question -> How much terminology should be integrated with the current base.Entity class?
I feel that's a bad idea to "hack" terminology stuff into it, but later -> That also may be not the best idea to create a separate interface for contributors.
If you have any thoughts/requirements on how the first version of The Terminology should look like -> I would love to hear them :D

At the end of discussion I would like to have a set of requirements on which everybody agrees and I can start implementation again.
In the meantime, I'll rebase the previous PR against fresh master.

Comment 6

[Axel Hecht [:Pike]]

Please keep work-related bugzilla inquiries to my work account.

One of the ways to go about this is to assume that we have a couple of external services for Terminology. Some/one of them might be hosted on pontoon.m.o, but for the translate UI, that shouldn't matter much?

If I look at the user story, I think that the 3rd bucket is the one we can most easily make progress on.

The first bucket, the actual storage of the mozilla terminology, is an item we should discuss, there is more than one option right now. Which I don't know how to list right now, too.

I'd take the import of external TBX files out of the picture for now, though it isn't really, as the mozilla-specific word-list that Kekoa did excluded more generic computer terms on purpose.

Comment 7

[Matjaz Horvat [:mathjazz]]

As agreed on the call, let's put this on hold until we have more relevant information available.

Comment 8

[Jarek Śmiejczak [:jotes]]

:mathjazz
I don't know how the current status of the TM looks like :D Is it okay to create a separate bug to add a support of TMX/TBX formats in Pontoon? TMX terms would be displayed in the same way as the rest of the strings.
This could be a good entry point to develop more TMX/TBX related features.