Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
17.10.14, 18.8.0
-
None
-
Unknown
-
Description
The translation macro takes a translation key and a language in free text fields of the Edit Macro dialog, so the user has to know the exact key, case included, and an unknown language falls back silently.
The main problem:
- The keys and the languages of the wiki are only known at runtime, so both lists need a provider.
Depends on
Most of these fields cannot be offered before these generic changes, each giving the macro the means to declare the expected value:
- XWIKI-23045, which lets a parameter get its values from a provider, with or without custom values.
KOs covered
| Macro | Criterion | Parameter | Problem | Depends on |
|---|---|---|---|---|
| translation | C4 input-assistance | key | A plain text field for the exact key: a typo displays the key. A picker suggesting the keys of the wiki with their text in the current language could be used. | XWIKI-23045 |
| translation | C4 input-assistance | locale | A free text field, although the useful values are the languages of the wiki: zz falls back silently. A select of the languages, like the one of the Localization administration, could be used. | XWIKI-23045 |
Impact found on macro fluidity
These 2 KOs come from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance of its usability criteria. The page of each macro, linked in the table, has the full notes and the steps to reproduce. Fixing them means changing the declaration of the parameters in the macro definitions.
Attachments
Issue Links
- depends on
-
-
- Open
-