Page MenuHomePhabricator

CX2: Better direct users to in-line templates that were converted to text
Open, MediumPublic


When in-line templates cannot be transferred into the translation, they are converted into regular text (T204942). In this way, the information is kept in a basic form, but users need to review if the result is appropriate in order to further edit it if needed.

Currently, a warning is shown at a paragraph level for these cases, but it may not be always easy for users to identify which is the relevant piece of content inside the paragraph. Helping users to identify the relevant content more easily would avoid confusion.

We want to explore simple ways to point users to the affected content without increasing the complexity too much (risking errors and markup leaking). In order to achieve this we may want to relax the initial requirements of highlighting the affected content while the issue card is active (T204942), in favour of a more simple approach (even if less precise).

Some ideas to explore:

  • Highlight the whole sentence. It may be possible to use the current mechanism of sentence highlighting to target the whole sentence where the in-line template was. This highlight can be persistent with the issue card or, if that is too complex, shown temporally when the paragraph is added to the translation (and fading away after a few seconds).
  • Include part of the affected content for additional context. If highlighting the information in context is not possible, we may want to extend the warning message to include part of the affected content (e.g., "2 kilometres (1.2 mi)" ). In this way, the user would be able to scan the content looking for it more easily. For cases with long text, we need to consider setting a max-length and using ellipsis.

(More specific design details to be added once we have a technical assessment of the possible paths forward)

Event Timeline

Note that according to T204942#4874734, when multiple templates cannot be adapted currently we only show one issue card. As part of the current ticket we may need to surface each issue independently (i.e., with one issue card instance for each missing template instance).