Changed incorrect language code de_CH of es_CL

[dgmouris]

Fixes #297

[Andrew-Chen-Wang]

Just edited your comment for automatic resolving of issue. Thanks for double checking!

Edit: Just took a look at the .mo file. It turns out that there is a language code in there as well (that's also incorrect). I'm not looking forward to tampering a partially non UTF-8 file that may be binary, so do you mind recompiling the files according to documentation? https://docs.djangoproject.com/en/3.1/topics/i18n/translation/#message-files

Thanks!

This is what I'm seeing in the de_CH django.mo file:

fi��ï������������Ã�������|����������<���Ò���,���.���(���[���2���Ñ���O���∑���������������$���3���4�������h�������Ä�������ê�������¢�������∑�������Ã��� ���Ë�������	�����������
���)���
���4�������?�������C���.���H���G���w���>���ø���*���˛���5���)���X���_���"���∏�������€���6���Î�������"�������<�������O�������d�����������#���ù�������¡�������·�������Ù���������������������%�������)�����������
���������������	���������������������������
���������������������������������������������������������������Authorization header must contain two space-delimited values�Cannot create token with no type or lifetime�Given token not valid for any token type�No active account found with the given credentials�The '{}' setting has been removed. Please refer to '{}' for available settings.�Token '{}' claim has expired�Token Blacklist�Token contained no recognizable user identification�Token has no '{}' claim�Token has no id�Token has no type�Token has wrong type�Token is blacklisted�Token is invalid or expired�Unrecognized algorithm type '{}'�User is inactive�User not found�created at�expires at�jti�user�Project-Id-Version: djangorestframework_simplejwt
Report-Msgid-Bugs-To: 
POT-Creation-Date: 2020-01-04 10:30-0300
Last-Translator: rene <[email protected]>
Language: es_CL
MIME-Version: 1.0

[Andrew-Chen-Wang]

Cool, turns out .mo files also needs to be regenerated. I think django-admin makemessages -l de_CH is good enough to update it. @dgmouris

[Andrew-Chen-Wang]

LGTM Thanks @dgmouris !

Actually is there a reason why all the paths had to include the package name?

[dgmouris]

Hey @Andrew-Chen-Wang,

I took a look at some docs (https://docs.djangoproject.com/en/3.1/topics/i18n/translation/) and It looks like I needed to run a couple of things.

1. django-admin.py makemessages -l de_CH
2. django-admin.py compilemessages -l de_CH

As well I ran the "makemessages" and compilemessages" and it seems like the mo files for es_CL and ru_RU aren't updated.

UPDATE:
I just compiled them and added them to this PR because it might cause issues to others...

[Andrew-Chen-Wang]

@dgmouris I took a look at dj-stripe's repo. They don't even have the .mo file and I believe it's because Django will create the .mo file if the developer chooses to support i18n. (i.e. the devs need to run the compile messages or other commands). In this case, it's fine but I'm curious as to why the .po files changed the paths for all of them

[dgmouris]

@Andrew-Chen-Wang I moved into the rest_framework_simplejwt and it fixed all of the paths to what was expected.

My apologies:) It should be all good now.

Cheers,

Dan

[Andrew-Chen-Wang]

Thanks for the help @dgmouris!