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

Czech translation #92

Closed
KittyGiraudel opened this issue Jan 16, 2015 · 28 comments
Closed

Czech translation #92

KittyGiraudel opened this issue Jan 16, 2015 · 28 comments

Comments

@KittyGiraudel
Copy link
Owner

Ping @pavelantolik.

@pavelantolik
Copy link

Hi Hugo,

I've got the repository cloned to my laptop, but I'm still kinda new in GitHub (we use Subversion at work, so my relationship with GitHub so far has been "visitor only"). So I could use a little hint - what exactly does it take to "open a cz branch"? Don't wanna mess anything up :))

@a5e
Copy link
Contributor

a5e commented Jan 17, 2015

  1. git checkout gh-pages && git checkout -b cz && mkdir cz && cp index.md cz/index.md
    ( in order : first we open the gh-pages branch, then we create and go to a cz branch, then we create the folder and finally copy index.md in the cz folder)
  2. translate cz/index.md
  3. git commit -am "added cz translation fixes #92" (commiting your changes and referencing this issue)
  4. git push origin cz (pushing your branch on your github fork)
  5. go to github and click the PR button. (submitting your pull request to the original repository)

Hope this is clear, feel free to ask if it isn't

@KittyGiraudel
Copy link
Owner Author

Thanks Antoine for the heads up.

Adding to this, you have to know that when you create a new branch (git checkout -b <branch_name>), you are using the state of the current branch. That's why you have to put yourself on the gh-pages branch before creating your own, rather than master (which is empty).

More information here: #96.

@tenhobi
Copy link

tenhobi commented May 17, 2015

@hugogiraudel hi, I will try translate the guidelines to Czech lang, If you want... :)
I can not see any work done - so pavelantolik probably did not start, right?

@KittyGiraudel
Copy link
Owner Author

Hello. That's good news. I think it is safe to assume that you will be on
your own on this.

Le dim 17 mai 2015 13:16, Honza Bittner [email protected] a écrit :

@hugogiraudel https://github.com/HugoGiraudel hi, I will try translate
the guidelines to Czech lang, If you want... :)
I can not see any work done - so pavelantolik probably did not start,
right?


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

@tenhobi
Copy link

tenhobi commented May 17, 2015

@hugogiraudel ok, cool. :)

Should I use shortcut for translate according to
the Czech republic -> CZ (https://countrycode.org/czechrepublic)
or
czech lang -> CS (http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)
? :)

@Grawl
Copy link
Contributor

Grawl commented May 17, 2015

I think cz will be better.

@KittyGiraudel
Copy link
Owner Author

cz sounds good to me.

Le dim 17 mai 2015 15:45, Даниил Пронин [email protected] a écrit :

I think cz will be better.


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

@tenhobi
Copy link

tenhobi commented Jun 1, 2015

Here is my progress. Translation is probably not excellent, but I am going to improve it. 😺

  • INDEX

Guideline files:

  • About the author
  • Contributing
  • Table of Contents
  • About Sass
  • Introduction
  • Syntax & formatting
  • Naming conventions
  • Commenting
  • Architecture
  • Responsive Web Design and breakpoints
  • Variables
  • Extend
  • Mixins
  • Conditional statements
  • Loops
  • Warnings and Errors
  • Tools
  • Too Long; Didn’t read

@KittyGiraudel
Copy link
Owner Author

I am really looking forward to it! :)

@tenhobi
Copy link

tenhobi commented Jul 26, 2015

Only 5, small, sections left. :)

Can I release (after that) something like 1.1.0-beta, which will may not have translated codes from _include/ and will may not have stunningly perfect translation?

... just to have it avaible as beta for impatient people? 😸

@KittyGiraudel
Copy link
Owner Author

We cannot release a beta, and I am not willing to do so. However, I am perfectly fine to release the Czech version with English code snippets. We can translate them later on. :)

@tenhobi
Copy link

tenhobi commented Jul 27, 2015

OK, no problem. 👍

@KittyGiraudel
Copy link
Owner Author

Great. Feel free to tell me when I should review it. :)

@tenhobi
Copy link

tenhobi commented Jul 27, 2015

I am really like that I can translate this awesome guidelines, because I can learn a lot from both English and Sass. 😼

Well, I think I am done. 👍
// I have cheked all once again and I think and I hope it is OK. 😼

@KittyGiraudel
Copy link
Owner Author

Alright. Let me review it right now.

@tenhobi
Copy link

tenhobi commented Jul 27, 2015

@hugogiraudel is any chance to make my own IDs for headings? Czech have some extra characters English do not and it only make some babble, which is not so much semantic. 😼

@KittyGiraudel
Copy link
Owner Author

Nope. Not possible. Sorry.

@tenhobi
Copy link

tenhobi commented Jul 27, 2015

So there are some task I want to make for next merge:

  • fix potential typo errors
  • fix links referring to headings
  • translate code snippets

@KittyGiraudel
Copy link
Owner Author

Sounds good. :)

@tenhobi
Copy link

tenhobi commented Aug 25, 2015

I'm sorry, but I had been on summer camp and the rest of the time I have worked on a project. Now I am going to surgery, but I will try to finish this ASAP after I will be +- OK. 😸

@KittyGiraudel
Copy link
Owner Author

I hope everything is fine. Take care!

@tenhobi
Copy link

tenhobi commented Jan 23, 2017

I will continue with translations. 👍

@tenhobi
Copy link

tenhobi commented Jan 24, 2017

Btw. @hugogiraudel should I after translation will be done open PR to your master or gh-pages? Kind of do not know the difference in Jekyll. But other open PR to master so I should do the same?

@tenhobi
Copy link

tenhobi commented Jan 24, 2017

E.g. I am not sure if

  1. here why people do PR to master then?
git checkout gh-pages
git checkout -b cz
git checkout master
git checkout -b cz

@KittyGiraudel
Copy link
Owner Author

KittyGiraudel commented Jan 24, 2017

master, we don’t use gh-pages anymore. It’s obsolete. I’ll delete it soon.

@KittyGiraudel
Copy link
Owner Author

@hobi Do you need this issue to be open or can I close it?

@tenhobi
Copy link

tenhobi commented Jan 30, 2017

@hugogiraudel you can close it. I continue with traslation and updates on my forked repo and then i will do a pull request. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants