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

Unable to Access Google Charts API Reference Documentation #3006

Open
fruscianteee opened this issue Mar 25, 2024 · 3 comments
Open

Unable to Access Google Charts API Reference Documentation #3006

fruscianteee opened this issue Mar 25, 2024 · 3 comments

Comments

@fruscianteee
Copy link

Hello,

I've encountered an issue while attempting to access the Google Charts API reference documentation. While I am able to visit the main glossary page at https://developers.google.com/chart/glossary?hl=ja, clicking on the link to the "API Overview" page results in an "Internal Server Error".

The specific URL I'm trying to access is https://developers.google.com/chart/interactive/docs/reference?hl=ja.

Is there an alternative way to access this information or a known issue that is being resolved? Any guidance or updates on this matter would be greatly appreciated.

Thank you.

@dlaliberte
Copy link

It looks like there is a problem on the documentation site with the reference page translation hl=ja, so until this problem gets fixed, you'll have to live with the English version at [https://developers.google.com/chart/interactive/docs/reference]. You might have to revisit the [Home] (https://developers.google.com/chart) page and reset the translation to English, or perhaps some other language will work.

@fruscianteee
Copy link
Author

Thank you for the quick response and the workaround by switching to the English version of the documentation. I was able to access the reference page successfully after changing the language settings.

Should we close this issue considering the workaround provided, or keep it open until the translation link issue is resolved? I would appreciate your advice on how best to proceed.

@dlaliberte
Copy link

Should we close this issue considering the workaround provided, or keep it open until the translation link issue is resolved? I would appreciate your advice on how best to proceed.

Other people might experience the same issue until it is fixed. So keeping this post open is probably useful.

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