Translate the Regular Expression Tutorial into your language (HTML/CSS)

[niccokunzmann]

This is a lot of work which can be done partly but: You will get help and learn regular expressions, HTML, CSS and Jekyll on the way.
You can add your own language.

• You can link it on the index.html page and write "(work in progress)" so that it is live but not expected to be complete and others can join.
• You can start translating from English or German
• Have a look at the steps folder for the different steps and an explanation of how to translate the steps.
• You can add your name to the CCby license in your language at the bottom of the tutorial.

Hints:

• Translation description

[weerox]

I'm about to translate this to Swedish now, and just wanted to confirm that I will be naming files according to an english keyboard (replace ö with o, and å with a), just to make sure we doesn't break anything

[niccokunzmann]

@weerox I do not know if it breaks anything. You can try it out. It does not hurt :)

If you like to create pull-requests in between, we can help you if we spot anything and merge as soon as possible, so you can get people reviewing it here or at your fork. Translating takes some time so I would rather merge what you did in Swedish and get more people to help out than require a full translation.

You can, let me know if I can help in any way because I would like to.

[weerox]

@niccokunzmann What about the translation branch? I saw it had another file structure. Is it an updated file structure that you are working on? (I'll create a PR to the master branch)

[niccokunzmann]

@weerox The tanslation branch was for #13 as we figured out how to structure the translations. I deleted it.

[weerox]

I've been thinking about the translations, and realized that if anyone wanted to translate the tutorial inte a language similar to Swedish (Danish, for example), then the introduction-file might have to be named the same, which would break the whole thing.

[weerox]

I spent this weekend trying to figure out a better way to handle translations, and came up with this.
Every language get their own folder ("sv/", "en/", "de/", etc.) and the files only have the numbers in the filename. This means that it might be easy to implement a language switcher (just switch the language dir in the url).
I have also gathered all strings that has to be translated into a single file, so it is easier to find them.
What do you think @niccokunzmann?

[niccokunzmann]

I think this is really good. It is much clearer now, where we need to translate it and one only needs to know html and JSON.

[weerox]

So I will create a better commit message and push later today

[weerox]

Oh, sorry. I forgot that I pushed to master from my local translation branch. I didn't remember that that would change the PR I had made...