sajolida:
>
> - For me it is hard to read the lists, specially the differences when only one line changes in a long list, i.e.
>> https://translate.tails.boum.org/translate/tails/license/es/?type=fuzzy
>> The lists can be made fuzzy adding a space before in each line.
Sorry, here i meant 'can be separated', but luckily you understood. I correct here for other people :D
>
> I see... Then it would be super helpful for me if translators would let
> me know when such things happen. Because I can probably split them into
> different PO strings.
>
> See what I did in d5ad0e8a9a and 3ae262172d.
Yes, I see that the changes d5ad0e8a9a produced on the .po files at 3ae262172d will make this horrible list much easier to translate now. We will just get a new string and the others will remain the same. Pity that many strings are lost, I will try to recover them from the commit.
> Do you want me to break more such lists?
I for sure would like that to happen to new lists. But I am not sure about the already existing lists, what other translators think is better. Maybe they complain about having already translated it...
>> - 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.
Making new checks in weblate is quite easy, see
https://docs.weblate.org/en/weblate-2.19.1/admin/checks.html#custom-checks there is already a check class and you just have to create a file with the little check in python.
>> Many translators translate class names, as in <div class='next'> becomes <div class='prochaine'>
>
> So limiting the number of CSS classes to the bare minimum would help.
yes
>>>> 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 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.
In that case, yes, I like the first better. Markdown seems to be much more understandable.
>>>>> - 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>
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.
> If we're unsure, shall we keep writing the second way?
>
> (Meta: I created #16221 to track this discussion.)
OK I will add my input there then.... maybe I can find some test checks i was experimenting with in weblate...
