-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Internationalization base #1246
base: master
Are you sure you want to change the base?
Conversation
Created a new user account Rebased off of first divergent main commit
Looks interesting, Thank you for the PR |
A few fixes are still needed, I'll get to them when I can. But for now only french and english. |
Thank you, I think FR, ES and EN would be a very good start. If there are some bugs to be fixed, do you mind keeping this MR in DRAFT please? |
…e as per the doc + added zeroRecords & infoEmpty translations
Ready for review / critiques / comments |
Hey, regarding the push to 2.2.0, considering it's been 7 months since the last release (2.0 vs 2.1), I can't help but feel this PR will be discontinued and have to go through tremendous work to merge by then. |
@Talanor I am trying to go through the changes and release this asap. I need to ask a few things,
|
Sorry I mistakenly closed this! |
Say hello to our lord and savior: internationalization.
This is stable on my staging environment, but probably not production ready.
I'm mainly opening this for tracking purposes / discussion and feedback from users / maintainers (and to move on with my life).
--
Main points of contention :
manage.py makemessages -a -d djangojs
, it will comment out those translations. You can grep#~
in.po
files and delete it to uncomment them beforemanage.py compilemessages
Edit: Most FR translations were AI generated. Even though I reviewed most of it, some weird stuff might have escaped me.