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

bpo-31149: Doc: Add Japanese to the language switcher. (#3028) #3081

Merged
merged 1 commit into from Aug 13, 2017

Conversation

Projects
None yet
5 participants
@JulienPalard
Member

JulienPalard commented Aug 13, 2017

Backporting to 2.7 the backports to 3.6 about adding Japanese (and a fix for a bug appearing when adding a language) to the language switcher on docs.python.org.

…… (#3051)

  • bpo-31159: fix language switch regex on unknown yet built languages. (#3039)

This fix a regex issue (a missing non-matching group around an 'or'
list) and the specific possible case where a translation is built but
not yet in known by the picker, but not explicitly listing possible
languages in the regex.
(cherry picked from commit 122081d)

  • bpo-31149: Doc: Add Japanese to the language switcher. (#3028)

(cherry picked from commit c82b7f3)

(cherry picked from commit e8e7fba)

https://bugs.python.org/issue31149

bpo-31159: fix language switch regex on unknown yet built languages. … (
#3051)

* bpo-31159: fix language switch regex on unknown yet built languages. (#3039)

This fix a regex issue (a missing non-matching group around an 'or'
list) and the specific possible case where a translation is built but
not yet in known by the picker, but not explicitly listing possible
languages in the regex.
(cherry picked from commit 122081d)

* bpo-31149: Doc: Add Japanese to the language switcher. (#3028)

(cherry picked from commit c82b7f3)

(cherry picked from commit e8e7fba)

@vstinner vstinner merged commit fe8d9dc into python:2.7 Aug 13, 2017

2 checks passed

bedevere/issue-number Issue number 31149 found
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment