sajolida:
> emma peel:
>> sajolida:
>>> To rephrase my question, do you think it would be better for translators
>>> (and Weblate) to write:
>>>
>>> **Applications ▸ Tails ▸ Configure persistent storage**
>>>
>>> Instead of:
>>>
>>> <span class="guimenu">Applications</span> ▸
>>> <span class="guisubmenu">Tails</span> ▸
>>> <span class="guimenuitem">Configure persistent storage</span>
>>> </span>
>>
>> I think translators are less likely to make errors with the first version. But if they do make errors, weblate will be able to spot the html errors better than the markdown ones.
>
> I added this to #16221.
>
> On the other hand, I don't think it's theoretically impossible to
> validate Markdown and detect a missing '*', for example:
>
> **Applications ▸ Tails ▸ Configure persistent storage*
>
> (or similar)
>
> See projects like:
>
> https://github.com/MihaZupan/MarkdownValidator
>
> I'll ask Hans-Christoph and see if he can help us make up our mind...
A final update on this thread so that we can close it.
Next versions of Weblate will have Markdown validation. Weblate will check
that the Markdown is the same in the original string and the translation.
Once we have this, I think we should drop the CSS formatting as it will
solve our concerns with Markdown.
I linked to the Weblate issue on #16221
and blocked it by the translation platform (#10034).
Thanks ignifugo and emmapeel for moving this discussion forward!
--
sajolida
