Design read-only representation of FTL Messages

[bugzilla-to-github]

This issue was created automatically by a script.

Bug 1431417

Bug Reporter: Eduardo Trápani <[email protected]> CC: @Pike, @mathjazz, @stasm, @zbraniecki

Created attachment 8943623 Screenshot-2018-1-18 Firefox Screenshots · Esperanto (eo)(1).png

See the screenshot. For ftl, just the "value" is listed under other locales. For this[1] it is not very useful, since everybody is using the infinity symbol.

I haven't found a way to list the "title" values for other locales, as it would be shown normally.

[1] https://pontoon.mozilla.org/eo/firefox-screenshots/server.ftl/?status=missing&string=175028

[bugzilla-to-github]

Comment Author: Eduardo Trápani <[email protected]>

Created attachment 8943625 Normal listing in "locales"

This is the expected view, where I can see the translations made by other teams.

Attached file: Screenshot-2018-1-18 Firefox Screenshots · Esperanto (eo).png (image/png, 25485 bytes) Description: Normal listing in "locales"

[bugzilla-to-github]

Comment Author: @mathjazz

We use what's internal called a simple preview here, which is also used in many other places like the String list and the Latest activity column on dashboards.

We need to design a read-only representation for each string, possibly inspired by how we render source strings. It will be used virtually everywhere except for the editor:

• source string
• history
• locales
• machinery
• string list
• latest activity
• contributor timeline
• etc.

[bugzilla-to-github]

Comment Author: @Pike

Let's put some opinions out:

The first thing to pick is the canonical value. That's the question which of the value and attributes we should show. This might be the first non-null, or the longest pre-simplified, or the longest post-simplified. I'd expect that longest pre-simplified is a good compromise. I doubt we have a lot of strings where the accesskey is platform dependent select expression (really long) and the label is the interesting thing.

Then there's the value generation. I think what we want to do is use the default variant of the value, and for that compute the default value of all select expressions.

Message references and other placeables could be anonymized? In the sense that you only see there's a placeable, but not which, and what's in there. That might also be interesting for TM?

I wonder if we should move this into fluent, stas?