sajolida:
> emma peel:
>> sajolida:
>>
>>> Emma: How frequently do you see translators mess up with the HTML in
>>> strings on Weblate?
>>
>> VERY often
>
I confirm by the group of italian speaker
>
>> I keep answering inline:
>>
>>>> On 09/09/2018 03:31 PM, sajolida wrote:
>>>> [...]>
>>>>> Only some days ago did I realize that this might be a real pain for
>>>>> translators to translate and maintain. Of course, you've been dealing
>>>>> with that for years and already know how to do it well, but what about
>>>>> newer translators and future teams?
>>>>>
>>>>> I haven't done much translations myself and I've never used Weblate, so
>>>>> I'd like to know how much of a relief it would be if we stopped writing
>>>>> this way and used Markdown instead.
>>
>> - Weblate has some XMl validation tests, but they don't work with Markdown. https://translate.tails.boum.org/checks/?project=tails (all fixed currently) so currently we make some mistakes when translating that break the page, like
>> translating [[link]] by [[somenewwordnotarealpage]] or [[link] without the right amount of [.
>
> Ok. I think I discussed this with Hans-Christoph Steiner in Mexico and I
> asked him to check with the Weblate devs if it would be possible to add
> validation tests for Markdown.
>
hum.. I have doubt to change to markdown.. it-s a solution that could
introduce others problems.. I think, but I open to speak about this..
> So limiting the number of CSS classes to the bare minimum would help.
>
>>>> I think that changing it to pure markdown would definitly be an improvement.
>>
>> I am not so sure about that, I think it is important to add comments and make it as simple as possible!
>
> I don't understand this...
I think I could help. I work in markup also for job, but I need to have
an appointment remote to start to work on because.. I don-t know some
part of the workflow of the website of TAILS. For example I don-t know
wich software decide/harvest the string by ikiwiki. if you explain me
this part, I can set the stuffs on my pc and make experiment :)
I-m available to take care of this aspect. can we take a remote
appointment about this?
hugs ignifugo
>
> I mean writing:
>
> **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>
>
> But we would still be able to add HTML comments in the Markdown whenever
> needed.
>
>>>>> - Hearing from how do this goes for the less technical of our
>>>>> translators. Say someone who doesn't otherwise know HTML. How frequent
>>>>> is it for newer translators to made mistakes on these?
>>
>> Very frequent
>
> Thanks, that's what I wanted to know.
>
>>>>> - Whether you think that Markdown instead of HTML would lower the error
>>>>> rates. Because I still want application names to display in italic :)
>>
>> I am not so sure about this. I think html gets checked by weblate better.
>
> Ahh... Then I'm not sure about my plan anymore.
>
> 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>
>
> ?
>
> If we're unsure, shall we keep writing the second way?
>
> (Meta: I created #16221 to track this discussion.)
>
