You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I've noticed that HTML entities used in XLIFF files arn't converted to UTF-8 on Weblate.
This is something that would make working with Weblate almost impossible for our translators.
I did notice that this enhancement was already added to the todo list, but I would like to ask when to expect the solution?
Also, are there any other file formats that cause less problems concerning the encoding and the state of translation?
As far as I've seen, GNU Gettext format would be best practise, is that correct?
This is one of the HTML entities I'm talking about, which should be shown as "Hello, world! <"
This is the xliff file taken from an example for xliff files.
The text was updated successfully, but these errors were encountered:
I did notice that this enhancement was already added to the todo list, but I would like to ask when to expect the solution?
Also, are there any other file formats that cause less problems concerning the encoding and the state of translation?
As far as I've seen, GNU Gettext format would be best practise, is that correct?
There is no schedule on that, but in case you want to discuss that, please followup in the original issue.
The XML formats with possibly nested tags are problematic in this. Once the nested XML tags are allowed, the XML entities encoding must follow that behaviour. If you don't need the inner XML markup, anything besides XLIFF and Android resource strings will probably do a better job in this regard.
Hello,
I've noticed that HTML entities used in XLIFF files arn't converted to UTF-8 on Weblate.
This is something that would make working with Weblate almost impossible for our translators.
I did notice that this enhancement was already added to the todo list, but I would like to ask when to expect the solution?
Also, are there any other file formats that cause less problems concerning the encoding and the state of translation?
As far as I've seen, GNU Gettext format would be best practise, is that correct?
This is one of the HTML entities I'm talking about, which should be shown as "Hello, world! <"
This is the xliff file taken from an example for xliff files.
The text was updated successfully, but these errors were encountered: