1625443 - [FTL] Improve support for selectors and fluent messages with multiple attributes

Status: RESOLVED FIXED

(Webtools Graveyard :: Pontoon, defect, P2)

Description

[:Gijs (he/him)]

Right now labels for these strings are not very clear (cf. attachment 9134629 [details]), which means people on the l10n team are telling developers writing code to avoid writing messages where more than one value/attribute involves a selector.

The input fields and the reference translations should be clearly labeled to indicate what label/value in the message they are, and what selector is being used (if any)

Comment 1

[Matjaz Horvat [:mathjazz]]

Attachment: UI Proposals

Thanks for the report and sorry to hear you can't use strings like that.

The form-based Fluent editor intentionally hides some information from complex Fluent Messages to reduce complexity and avoid confusing localizers, who are used to localizing simple strings to simple strings. That's why we don't show any selector data for example.

OTOH localizers are more likely interested in attribute names, which is why we show them, but not if they contain selectors as in your example. So let's fix that. I'm attaching an example with 2 potential UI solutions. The one in the original string more closely follows the syntax, but uses a lot of vertical space. The other solution is used in the editor and just prepends variant names with attribute names.

An idea for the next iteration would be to also engage our accesskey UI for cases like this.

Comment 2

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/pontoon/pull/1614