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

Initialize localization #4

Open
wants to merge 7 commits into
base: gh-pages
Choose a base branch
from
Open

Initialize localization #4

wants to merge 7 commits into from

Conversation

autarc
Copy link
Member

@autarc autarc commented Oct 13, 2013

No description provided.

@mbesser
Copy link
Contributor

mbesser commented Oct 16, 2013

Forked your (@autarc) original PR and made a PR on it myself. There are some suggestions for improvement included. In order to make it work, you have to merge it into your PR, right? My github forking experience was close to non-existent until yesterday ;)

Suggesting some refinements for the german localization of index.md.
@thatbettina
Copy link
Contributor

Hi there.
I'm a little confused: What is the best way to proofread what @autarc wrote?
Fork it and do a PR on it?
Use Sphinx? (If so, how?)
Do in-line comments?

@Ivoz
Copy link
Member

Ivoz commented Oct 18, 2013

@thatbettina

What is the best way to proofread what @autarc wrote?

Probably checkout his fork, and read the pages he has created under locales/DE/*

Fork it and do a PR on it?

Exactamundo, like mbesser has done.

Use Sphinx? (If so, how?)

We would need to set up a Sphinx project and translate the files into ReStructuredText, as well as possibly create an appropriate theme. I'm thinking about setting something like this up as a future goal. At the moment, you can check out the python-beginners repo for an example of a Sphinx tutorial we've done which has some translations. I'm still trying to get the translation process streamlined.

@autarc

Not sure why you added locales/EN/* when that is the source material? Won't this only lead to duplication? I'm wondering what your intent was here.

@autarc
Copy link
Member Author

autarc commented Oct 19, 2013

@Ivoz

The idea was to have an extensible structure - which currently contains just english & german translations but could later include other languages as well. Since were running out of time I kept the original file structure for the online page as well, although for maintenance it will be better with the seperated locales.

@lehmannro
Copy link

I'll try to rephrase my warning: If you were to ever start a localized
version of the material, do NOT duplicate the whole material. If the
English source material ever changes, translators for other languages need
to keep track of these changes and apply them to all localized versions as
well. This is a recipe for on-going hassle.

If you were to ever start a localized version, better migrate the whole
curriculum to something which has gettext-style translation support
built-in. Sphinx is one solution; I'm sure there are others.

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.

5 participants