You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So after @lorenzolewis mentioned the existence of Starlight i18n VS Code extension a while ago, I took a look at it and it does work as intended and would surely help a lot for contributors.
Only catch is that by default it tries to find locale setting directly inside Astro config and cannot reference to our locales.json. So the question would be should we change our config so that Starlight i18n would work by default, or should we try to open an upstream issue at HiDeoo/starlight-i18n for overriding and also maybe try to fix it ourselves? 馃憖
The text was updated successfully, but these errors were encountered:
It might be possible to just import it from the Astro config inside of the i18n-tracker package but I haven't given it a shot yet.
Nonetheless, I think an upstream feature request would be beneficial here because I've seen other projects have to access the i18n data via things like a CI pipeline and keeping it as a JSON file like this could be the easiest way to get access to it with things like GitHub runners.
Good news, Starlight-i18n will be adding support for reading external locale json without any extra setup on next release, so now that we won鈥檛 be needing changes from our end, I鈥檓 updating the issue title to reflect it better.
dklassic
changed the title
[2.0] Astro config has to be updated to accommodate Starlight i18n VS Code extension behavior?
[2.0] Add Starlight i18n VS Code extension recommendation in translation.md
Jan 4, 2024
dklassic
changed the title
[2.0] Add Starlight i18n VS Code extension recommendation in translation.md
[2.0] Add Starlight i18n VS Code extension recommendation in translating guide
Jan 4, 2024
馃搵 Explain your issue
So after @lorenzolewis mentioned the existence of Starlight i18n VS Code extension a while ago, I took a look at it and it does work as intended and would surely help a lot for contributors.
Only catch is that by default it tries to find locale setting directly inside Astro config and cannot reference to our locales.json. So the question would be should we change our config so that Starlight i18n would work by default, or should we try to open an upstream issue at HiDeoo/starlight-i18n for overriding and also maybe try to fix it ourselves? 馃憖
The text was updated successfully, but these errors were encountered: