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

No localized strings now when setting language to 'ja-HIRA' #9926

Open
ganicke opened this issue Mar 19, 2024 · 3 comments
Open

No localized strings now when setting language to 'ja-HIRA' #9926

ganicke opened this issue Mar 19, 2024 · 3 comments

Comments

@ganicke
Copy link
Collaborator

ganicke commented Mar 19, 2024

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":

image

@sae220
Copy link
Contributor

sae220 commented Mar 27, 2024

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.

@sae220
Copy link
Contributor

sae220 commented Apr 3, 2024

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.

@sae220
Copy link
Contributor

sae220 commented Apr 12, 2024

I found it works well with query string translate=1.
With query string translate=1, crowdin JIPT is used, I guess.

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

No branches or pull requests

2 participants