Muri Nicanor:
> Hi sajolida, hi Cody,
Hi Muri!
Thanks a lot for your answer :)
I thought the topic would raise more interest amongst other
translators... Maybe the current situation is not that bad.
I'll put Emma in explicit copy now.
Emma: How frequently do you see translators mess up with the HTML in
strings on Weblate? Can the incorrect HTML be spotted automatically
somewhere down the line?
> 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.
>
> I have some experience with html, so for me its not that hard to parse
> those, but i can see how it might lead to confusion and/or mistakes and
> changing it to pure markdown would definitly make it easier to read. How
> hard it is also depends on the strings before and after the
> application-span.
> I think that changing it to pure markdown would definitly be an improvement.
Ok!
> Maybe i'm wrong, but isn't it also possible to use custom html
> attributes nowadays? Something like
> <application>Tails Installer</application>
> would (imo) also be an improvement and would not have the downside of
> losing the 'styleability'.
HTML 5 allows you to define custom data-* attributes:
https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Use_data_attributes
An attribute being a property of a tag. But I don't think HTML 5 allows
you to create custom *tags*.
>> For example:
>>
>> - <span class="application">Tails Installer</span>
>>
>> Would become:
>>
>> - *Tails Installer*
>>
>> I'm also interested in:
>>
>> - Whether it depends on your translation tools, for example, if PO Edit
>> is affected in the same way as Weblate. They might be easier to
>> translate on some tool than other or some tools might detect broken
>> HTML.
>
> I haven't used weblate that much, so i'm not sure if its easier or
> harder. At least in vim and poedit it doesn't make a difference. Poedit
> allows to just copy the source string using a Ctrl+b and then modify it
> and i see that weblate does the same with Ctrl+o- this make it easier,
> because you can just ignore the html part (you don't have to copy it by
> hand) and concentrate on the content.
Ok, good to know.
What about strings updates. For example, when you want to unfuzz a
string I guess it's sometimes better to fix the string that is already
translated without going back to a copy of the original string in
English, right?
>> - 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?
>>
>> - Whether you think that Markdown instead of HTML would lower the error
>> rates. Because I still want application names to display in italic :)
>
> are there even errors with html? i can not recall any...
Your HTML can be invalid and they all kind of bads things can happen.
There are some services to validate HTML for example:
https://validator.w3.org/
> maybe a bit off topic, but for me the hardest to read are string like:
> [[!meta title="Other Linux (Red Hat, Fedora, etc.)"]] [[!meta
> robots="noindex"]] [[!meta stylesheet="bootstrap.min" rel="stylesheet"
> title=""]] [[!meta stylesheet="inc/stylesheets/assistant"
> rel="stylesheet" title=""]] [[!meta stylesheet="inc/stylesheets/linux"
> rel="stylesheet" title=""]]
Excellent point! Let's see if we can fix this.
These are also a pain for me because whenever I want to change one of
the meta directives, it breaks translations for all the others.
--
sajolida
