No localized strings now when setting language to 'ja-HIRA'
ganicke opened this issue · 3 comments
It seems that something isn't fully connected with the addition of "ja-HIRA". Not seeing any strings at all in the response payload when ja-hira is selected. The response should at least have the default preload of "ja":
I guess each editor uses {host}/api/translations API and this API uses crowdin API internally.
And now this API doesn't work well.
We should check whether crowdin API which is used internally works well.
I want someone to check this or generate crowdin API key for my checking.
I noticed I can generate crowdin API key by myself.
I generated my key and made some tests.
I found the locale of "ja-hira" edited into upper case "ja-HIRA" but the id is still lower case "ja-hira".
Now I'm trying to update the crowdin API version, so I will be able to solve this problem after that.
I found it works well with query string translate=1.
With query string translate=1, crowdin JIPT is used, I guess.