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

Describe what not to translate #289

Merged
merged 3 commits into from
Mar 5, 2024
Merged

Describe what not to translate #289

merged 3 commits into from
Mar 5, 2024

Conversation

duncandewhurst
Copy link
Contributor

I forgot to add this in #288

Regarding my question in open-contracting/infrastructure#467 (comment):

Likewise, we should explain what to do with relative URLs, e.g. if a heading in the schema reference Markdown page is translated, should the translator update the references to that heading, or is that something that we do afterwards as part of a tidy-up?

I realised that the anchor slugs created by the MyST parser are not translated, e.g. https://standard.open-contracting.org/infrastructure/latest/es/guidance/identifiers/#project-identifiers-in-ocds

@jpmckinney jpmckinney merged commit 43448bd into main Mar 5, 2024
4 checks passed
@jpmckinney jpmckinney deleted the translation-guidance branch March 5, 2024 20:07
@jpmckinney
Copy link
Member

@duncandewhurst
Copy link
Contributor Author

Ah, how did I miss that!

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

Successfully merging this pull request may close these issues.

2 participants