Translate into German

[incompl]

Translate into German

[g12n]

I could pitch in some help as well

[incompl]

The translation instructions are in the README.

[Kriesse]

I’m available for help with german translation / proofreading as well.

[g12n]

I just started a german translation. I am happy for any help.
Would you rather go for a more formal language or an informal.
In German: Sie oder du?

[zu]

I already sent the first 62 lines of a German translation by emai,l as I don't know how to send a pull request.
If it would help, I could place the translation file in it's present stage in a google docs or a shared Dropbox folder.
This would allow to work as a team on the same file to finish a first iteration instead of having several people starting to work in parallel.
Of course, we also could merge the files later.

I used "Sie", the formal language.

[Kriesse]

@zu Would you mind sharing your initial work somehow? Google docs could work for a first iteration, but it would be nice to keep everything related to the repo and public for everyone.
I'd be happy to help if you are not familiar with pull requests, just let me know!

@mi1980ge I'd vote for a less formal "Du" translation. Reading "Sie" in an open source / tech education context sounds awkward to me.

[g12n]

We should devide the remaining chapters between us.

I forked the repository and committed the first part of my translation.
https://github.com/mi1980ge/csslayoutsite/blob/master/translations/de.yaml

@Kriesse Was this the best practice? Sorry, this is my first git team effort so I hope i at least started it right. But I am happy for tutoring and a quick intro.

@zu If you like i can add your translation to the yaml file.

In this open source context I tend to use "Du" as well 👍

[zu]

@Kriesse No I don't mind to share my initial work at all. Actually I did by sending the file as an email attachment to incompl. But as for now it doesn't show up in the repo. And yes you could help me out concerning pull requests.

I was not sure about the "Sie" or "Du" and actually changed to "Du" mistakenly, but corrected it.

@ml1980ge if you tell me how, I can send you the file.
Actually, I'm not sure, if forking is the best idea. Can it be merged together later?
I agree that everything should stay in the public repo.

[Kriesse]

@mi1980ge Yay, nice work!
Not sure about best practices when it comes to translations. I'd say, you make a pull request against the original repo. So others can fork it from there and contribute.

Style question:
Should we translate CSS terms like "selectors" and "values"?
I'd prefer to keep the english terminology, and maybe just add a translation in parentheses when they occur for the first time. Open for discussion!

[Kriesse]

@zu One quick way to share what you worked on so far would be just put it in a gist:
https://gist.github.com/

[Kriesse]

@zu If you fork the original repo (or start from @mi1980ge's repo), and commit and pull your changes, you should see this button:

From there it's pretty strict forward and as soon as your pull request gets accepted, your changes will show up in the original repo. Does that help?

[zu]

Thanks, but sorry, not really.
I "Cloned in Mac", have a local repo now in the GitHub App, committed from
there, which somehow doesn't do anything I'd expect.

So a little more help is needed (in German or English).

Thanks

-- |/ ------------------------
Christian Zumbrunnen
Holzmatt 7, 5200 Brugg

[phone]

From: Kristina Schneider [email protected]
Reply-To: incompl/csslayoutsite
<[e-mail]
ub.com>
Date: KW:12 | Mittwoch, 20. März 2013 19:57
To: incompl/csslayoutsite [email protected]
Cc: Christian Zumbrunnen [email protected]
Subject: Re: [csslayoutsite] Translate into German (#32)

@zu https://github.com/zu If you fork the original repo (or start from
@mi1980ge https://github.com/mi1980ge 's repo), and commit and pull your
changes, you should see this button:
<https://f.cloud.github.com/assets/53684/282378/e44b70e6-918f-11e2-8063-2ca
2d0dcb30c.png>
From there it's pretty strict forward and as soon as your pull request gets
accepted, your changes will show up in the original repo. Does that help?

‹
Reply to this email directly or view it on GitHub
#32 (comment) .

[zu]

ok, I now somehow saw how it works with forking and pull requests and hope i din't make a bigger mess. Got to learn a lot.

[zu]

Now my pull request was accepted and you can work from here.
@Kriesse I translated terms like selector and value: Selektoren, Eigenschaften und Werte
Begriffe wie width übersetze ich selbstverständlich nicht (sondern gebe in Klammern die deutsche Bedeutung wider).
Lässt sich aber alles noch anpassen.

[Kriesse]

@zu Cool, glad it worked!

Translating only "Selektoren, Eigenschaften und Werte" etc. sounds good to me. And right, we can always give it a final proof-read and change things that sound awkward.

[g12n]

I finally manages to pull @zu changes into my repo.
I would tackle the next chapter now.

@zu Did you already start with the section "positon" (lines 69 to 87 in the english original)? Otherwise I'll tackle it tonight.

Let's quickly sum um the style considerations:

• Only Translate "selector, property and value" to "Selektoren, Eigenschaften und Werte"
• use "Du" instead of "Sie"

Remaining Chapters to translate:

• position
• position example
• float
• clear
• the clearfix hack
• float layout example
• percent width
• media queries
• inline-block
• inline-block layout
• column
• flexbox
• css frameworks

shall we just split this list into two (or 3) sections and each one of us tackles one?

[Kriesse]

Thanks for the summary!
I pulled the latest from the original repo and work on those now:

• clear
• clearfix hack

[g12n]

I translatet a few more chapters (see checklist).
Need some serious proof reading and help changing the original chapter of @zu from »Sie« to »Du«.

[incompl]

Could you all put together a translation for index.translator that includes everyone who helped? For example, in french it is

index.translator: "Traduit par <a href=\"http://www.joel-matelli.fr\">Joël Matelli</a>"

Thanks!

[incompl]

Sweet, it's almost done!

[incompl]

Need any help finishing the translation? I can't wait to publish the German version!

[zu]

me too!

what do I need to do?
in my sight it's finished...

Greg mailto:[email protected]
15. Mai 2013 18:43

Need any help finishing the translation? I can't wait to publish the
German version!

—
Reply to this email directly or view it on GitHub
#32 (comment).

[incompl]

Oh! I thought there was still a section left. Taking a look at it now

[Kriesse]

Looks good to me, except maybe one final round of proof-reading. Nice work everyone!

[Kriesse]

A few notes:

• use "ß" where appropriate, as in "große" (not "grosse")
• Beware the Deppenleerzeichen: e.g. "CSS-Grundlagen" needs a hyphen. I'd suggest the same for words like "Box-Model", unless you keep the english term, but then I'd spell it all lowercase: "box model"
• Always have a space after comma, period etc.

I can take care of this later tonight. In the meantime, feel free to go ahead!

[incompl]

It's up! http://de.learnlayout.com

[incompl]

@Kriesse I opened a new issue for your suggestions: #78. This issue is now closed. Horray! Thanks everyone!

[Kriesse]

W00t! High fives everyone!