-
-
Notifications
You must be signed in to change notification settings - Fork 2
Initial machine translations. #18
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
Conversation
|
At this point, the translations and translation code should all be active; moving to ready for review. I'm about to get on a plane; merge at your convenience. |
kattni
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@freakboy3742 Two things, on one of which your opinion would be appreciated. See inline.
docs/en/contributing/index.md
Outdated
| There are plenty of ways to contribute to BeeWare. The [contribution guide](guide/index.md) covers everything you need to know to provide your contribution. | ||
|
|
||
| ## [Sprints](sprint-guide.md) | ||
| ## [Sprints](sprint-guide.md) { #sprints } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Sprint Guide itself has #sprints as the H1 title anchor. It'll pick the closest one, but, I don't know what that technically means. We shouldn't have it in both places. Which would you prefer the anchor link to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah - I missed the significance of that in my enthusiasm. I'd say the sprint guide itself is the much more useful anchor.
| } | ||
|
|
||
| a.docs-tutorial-button { | ||
| a.docs-tutorial { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You blasted -button from this as well. :) I'll push the fix after I get an answer on the sprints anchor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix was to update the reference in the div itself. That's why this is not showing outdated.
kattni
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
|
@freakboy3742 I'm not certain why the RTD builds aren't showing up in the CI status. They were triggered and built successfully (https://app.readthedocs.org/projects/beewareorg/builds/31326980/ for example). I'm going to merge this. If something is wonky, we can address it in a subsequent PR. |
The full set of initial machine translations.
Includes some minor tweaks to tox configs for consistency.
PR Checklist: