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

Update and rename ca-CA.json to ca-ES.json #699

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Ecron
Copy link

@Ecron Ecron commented Oct 23, 2023

The language code is not correct. The current one (ca-CA) would be for Catalan spoken in Canada (I wish!), but Catalan is mostly spoken in Spain (along with Andorra, France, and Italy). A correct language code would be ca-ES (although the best practice would be a generic language code "ca.json").

Also, I corrected some typos and untranslated sentences.

The language code is not correct. The current one (ca-CA) would be for Catalan spoken in Canada (I wish!), but Catalan is mostly spoken in Spain (along with Andorra, France, and Italy). A correct language code would be ca-ES (although the best practice would be a generic language code "ca.json").

Also, I corrected some typos and untranslated sentences.
@xeanhort
Copy link
Contributor

Hi @Ecron, thanks for your contribution!

I just wanted to mention this PR that already addresses the untranslated strings, and this opened issue that is related to the language code.

I suggest waiting until the first PR is merged (soon hopefully), and then synchronizing yours with the other string translations + file rename.

@Ecron
Copy link
Author

Ecron commented Oct 23, 2023

Damn it, I didn't see those, my apologies! You should totally wait until those are merged/solved. Sorry again for not checking first 😣

@jaruba
Copy link
Member

jaruba commented Nov 25, 2023

the issue here is that if you change a file name, all the users that ever selected "Catalan" will revert back to english (because the previous translation file / choice would no longer exist)

@xeanhort
Copy link
Contributor

Is it possible redirect this language to the other in the code for this specific case? Not the best solution but it will work. Or maybe keeping both files (or maybe removing the country extension?).

Nevertheless, we can merge #695 first, clean this PR, and then decide what to do.

@Ecron
Copy link
Author

Ecron commented Jul 10, 2024

Any news on this PR? I see #695 was closed on March 10, #667 was closed on October 14 2023 and there are no changes in #696...

Thanks in advance.

@xeanhort
Copy link
Contributor

The previous ones were merged (but there's a new one opened 3 weeks ago pending to be merged, not managed by me). I'm not sure what changes are still valid from this PR. Can you synchronize it with the latest changes to see the differences and put it easy to the maintainers?

Merged changes proposed by @xeanhort in his Stremio#805, merging both Stremio#805 and Stremio#699.
@Ecron
Copy link
Author

Ecron commented Jul 12, 2024

I just merged the changes I made for this #699 with the changes made by #805, so #805 can be closed and this can be merged.

@jaruba
Copy link
Member

jaruba commented Jul 12, 2024

there is really no good way to go about changing the translation filename, it will break translations for everyone that selected it before

regarding this suggestion:

Is it possible redirect this language to the other in the code for this specific case?

while possible, we don't add hacks to our code under any circumstance..

@xeanhort
Copy link
Contributor

Ok! Then we have to keep the current filename. @Ecron can you keep the original file name?

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 this pull request may close these issues.

None yet

3 participants