-
Notifications
You must be signed in to change notification settings - Fork 27
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
Locales #12
Comments
I don't know if It may be more useful to provide links to alternate languages in the form: <link rel="alternate" hreflang="en" href="https://docs.wpilib.org/en/latest/" />
<link rel="alternate" hreflang="fr" href="https://docs.wpilib.org/fr/latest/" /> ^ This is what Google Search uses to differentiate between languages: https://support.google.com/webmasters/answer/189077 |
That's something that we might be able to insert in extra tags on the per lang build, but not something that should be done in the extension. |
We should be able to take advantage of READTHEDOCS_LANGUAGE for this |
It’s not the correct format that ogp expects, it wants language_TERRITORY. |
It does indeed what language territory. However are locale codes can be used to lookup language territory. |
I added support for this (the non-og meta version) directly into frc-docs a while ago. https://github.com/wpilibsuite/frc-docs/blob/main/source/_extensions/localization.py |
Not sure if this is possible, but if it is, then adding support for and changing the
og:locale
based on the translated version of the documentation would be nice if possible. Additional adding support forog:locale
andog:locale:alternate
would be useful anyways for non-English documentation and documentation who has non-English translations.The text was updated successfully, but these errors were encountered: