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

Translation - UnicodeDecodeError 'utf-8' codec can't decode byte #1861

Closed
Torxed opened this issue Jun 12, 2023 · 7 comments · Fixed by #1870
Closed

Translation - UnicodeDecodeError 'utf-8' codec can't decode byte #1861

Torxed opened this issue Jun 12, 2023 · 7 comments · Fixed by #1870

Comments

@Torxed
Copy link
Member

Torxed commented Jun 12, 2023

screenshot

@Torxed
Copy link
Member Author

Torxed commented Jun 12, 2023

A continue on the error skips the language entirely. But that's perhaps not ideal.

@svartkanin
Copy link
Collaborator

I think something went wrong here when merging in the translations files, let me have a look

@Torxed
Copy link
Member Author

Torxed commented Jun 13, 2023

I thought that might be it. I also need to submit .mo files for all the languages as I haven't updated some of them yet.

@svartkanin
Copy link
Collaborator

Okay I got it fixed. But I'll also create a new github action to run a check on translation files as this has happened a few times now and it's difficult to detect especially when there's multiple translation PRs open

@Torxed
Copy link
Member Author

Torxed commented Jun 13, 2023

Thank you! I'm also submitting a PR to state that we only wish contributors to submit .po files to ease with merging. And that we'll perform .mo creation later.

They should also only touch the specific language they're modifying, and not the base.pot file, as everyone will be updating that with every PR otherwise :)

What do we think about a global ignore on .mo? I can do a git add --force on them before release if that workflow works for everyone.

@svartkanin svartkanin mentioned this issue Jun 13, 2023
@svartkanin
Copy link
Collaborator

svartkanin commented Jun 13, 2023

I don't think that's an easy one though unless it's possible with msgmerge and xgettext. Because running those will essentially update the base.pot and then populate the respective base.po files of each language. For people to see which texts have to be translated they will have to generate them.

We can ignore the .mo file, but not sure if that would help much?

@Torxed
Copy link
Member Author

Torxed commented Jun 13, 2023

The .mo would help because quite often people update the same language, and .mo is not git friendly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants