-
-
Notifications
You must be signed in to change notification settings - Fork 120
Update tabcontents.yaml fix URL redirect http -> https #744
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@rgommers @steppi It looks like this isn't in
content/pt/tabcontents.yaml
orcontent/ja/tabcontents.yaml
. Is there a plan or mechanism to keep the translations up-to-date?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.
@steppi could you please have a look at this?
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.
@steppi Gentle ping.
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.
Sorry. I'm not sure how I missed the pings back in April. This url has made it into
content/ja/tabcontents.yaml
andcontent/pt/tabcontents/yaml
nownumpy.org/content/ja/tabcontents.yaml
Lines 102 to 103 in f9a497c
numpy.org/content/pt/tabcontents.yaml
Line 87 in f9a497c
The mechanism for keeping translations up to date is that updates to the source content propagate to Crowdin through the GitHub integration and translators get notified that there is new or updated content to translate. The updates made in Crowdin are pushed to the running branch
l10n_main
and we have a GitHub action which essentially cherry picks commits from this branch to create PRs for particular languages.Process-wise, it would be fine either to just update the url in
content/en/tabcontents.yaml
and let the other updates be made by translators through Crowdin, or to make the change for all of the translated urls directly in GitHub. Originally, we had Crowdin configured in such a way that made it difficult to resolve conflicts when changes are made outside of Crowdin but that isn't an issue any more.In this particular case, I think it's better the change
http
->https
directly in GitHub for the different languages, since this isn't really something that should require translator attention. As an aside, I want to figure out how to hide things like urls and other strings which should not be translated from the translators.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.
Thank you, Albert!