Thanks for the reply @petrs !
So far I can’t run Baserow with my translation files yet.
But I just want to share a few things I tried here:
I was trying to run baserow with json files and .po files from Weblate, but simply placing them in places (mostly under ‘locale’ dir) didn’t work (Japanese was not appearing in the language menu.)
So, after searching around where ‘locale’ or ‘language’ or whatever seemingly-keywords are in the source trees, I ended up with changing 5 files. (git status screenshot at the end of the post).
This actually prompted me with ‘Japanese’ menu in settings, and did change the language, although most of my translation wasn’t appearing.
Then realizing that Weblate doesn’t have .mo files for django, I tried ‘python compilemessages’ to generate .mo files. Which somehow successfully compiled .po files. But nothing really changed.
Finally so far, I added migration file under backend source tree, by copying “0033_alter_userprofile_language.py” and adding “Japanese” in it.
With which it seems backend server stopped working giving me error that I need to “merge” migration files. But I have very limited understanding of Django and docker, so I can’t find out what to do.
Current “git status” is like this.
There seems more changes needed.
If anybody has ideas about what to do from here, I’d be glad to learn more !