Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTF-8 for XLIFF-files #5151

Closed
eschumacher-99 opened this issue Jan 6, 2021 · 3 comments
Closed

UTF-8 for XLIFF-files #5151

eschumacher-99 opened this issue Jan 6, 2021 · 3 comments
Labels
duplicate Similar issue or pull request already exists. enhancement Adding or requesting a new feature.

Comments

@eschumacher-99
Copy link

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?

image
This is one of the HTML entities I'm talking about, which should be shown as "Hello, world! <"

image
This is the xliff file taken from an example for xliff files.

@nijel nijel added duplicate Similar issue or pull request already exists. enhancement Adding or requesting a new feature. labels Jan 6, 2021
@nijel
Copy link
Member

nijel commented Jan 6, 2021

Duplicate of #3081

@nijel nijel marked this as a duplicate of #3081 Jan 6, 2021
@nijel nijel closed this as completed Jan 6, 2021
@eschumacher-99
Copy link
Author

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?

@nijel
Copy link
Member

nijel commented Jan 6, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Similar issue or pull request already exists. enhancement Adding or requesting a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants