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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Meta] Translation #96

Open
HugoGiraudel opened this issue Jan 16, 2015 · 80 comments
Open

[Meta] Translation #96

HugoGiraudel opened this issue Jan 16, 2015 · 80 comments
Labels

Comments

@HugoGiraudel
Copy link
Owner

@HugoGiraudel HugoGiraudel commented Jan 16, 2015

馃挗 Update January '17: help wanted for maintaining the Danish and Russian translations as well as future Chinese translation.

Let me open this issue so that I can talk to all of you kind folks who agreed to translate the guidelines at once. If any of you have a question about anything, please feel free to ask!

Getting started

  1. Read CONTRIBUTING.md to know more about Git and the branching system in use.
  2. Read TRANSLATING.md to know more about how to actually translate the guidelines.

Note: if you are updating a translation rather than starting from scratch, help yourself with CHANGELOG.md.

Submitting your work

  1. Make sure your version is up-to-date with the current master branch.
  2. Submit a pull request against the master branch on GitHub.
  3. This is over!

Translations

Status Language Version Translators
Chinese 1.3 Help wanted
German 1.3 @morkro
French 1.3 @pierrechoffe
Italian 1.3 @MakhBeth, @mattcav
Greek 1.3 @varemenos, @margaritis
Spanish 1.3 @soniar4i, @davidkpiano
Portuguese 1.3 @magalhini, @Couto, @SaraVieira, @eduardoboucas, @JLammeer
Russian 1.3 @irene-97, @PavelDemyanenko, @nastiatikk, @arbaev
Polish 1.2 @klapec, @matchabros
Czech 1.1 @hobi
Korean 1.1 @kimdhoe
Danish 1.1 Help wanted

means up-to-date.
means not up-to-date.
means in progress.

This was referenced Jan 17, 2015
@HugoGiraudel HugoGiraudel changed the title Translation meta-issue [Meta] Translation Jan 18, 2015
@srescio
Copy link

@srescio srescio commented Jan 18, 2015

I'm experiencing some issue with headings titles and anchors generated by Jekyll, it seems to have issues handling accented vowels, as result i get [Cosa 猫 Sass]-(#cosa-%C3%A8-sass) which doesn't work as proper anchor and doesn't make page scroll to the related element, if there's no fix/workaround I'll just replace them rephrasing the headlines that have this issue (only one so far), even though it would feel less "natural" to me

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 18, 2015

Mmmh. I will have a look tomorrow.

@Grawl
Copy link
Contributor

@Grawl Grawl commented Jan 19, 2015

@srescio I have not worked on it but already see this problem and I think that we have add some HTML into our Markdown like this:

<a href='#colors'>笑胁械褌邪</a>

鈥

## <a name='colors'>笑胁械褌邪</a>

But I don't know how it would work with existing Sass Guidelines frontend.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 19, 2015

Okay, so I just checked and "Cosa 猫 Sass" leads to cosa--sass. So please don't refrain yourself using special characters. They are omitted in ids.

@Grawl
Copy link
Contributor

@Grawl Grawl commented Jan 19, 2015

@HugoGiraudel please note that only latin characters remains. Russian language don't have any latin characters so remains only words like 鈥淪ass鈥 or other terms that we don't translate.

So if we have Using Sass in your project it will be translated like 袠褋锌芯谢褜蟹芯胁邪薪懈械 Sass 胁 胁邪褕械屑 锌褉芯械泻褌械 and will be converted to something like -sass---.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 19, 2015

Mpf. That is an issue for Russian I suppose. Let me have a look, if I can find something.

We might be onto something with this: http://kramdown.gettalong.org/options.html#option-transliterated-header-ids. I just tried it and it works just fine, however I am not sure GitHub Pages will support it... I need to investigate.

Let's see: jekyll/jekyll#1095 (comment).

@codejanovic
Copy link

@codejanovic codejanovic commented Jan 19, 2015

@HugoGiraudel: Wouldn't it be helpful to add a Gitter-Room for further communication?

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 19, 2015

Good idea. Done. If someone did not have an invitation, please ask.

https://gitter.im/HugoGiraudel/sass-guidelines

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Apr 11, 2015

Sass Guidelines EN 1.1 has been released just now.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jul 22, 2015

I have updated the existing CONTRIBUTING.md file at the root of the repository. It now contains enough information about how to deal with Git, especially regarding the existing branching system.

I also realised my translating guidelines emitted in the original description of this issue sucked. I have been bad at this, and I sincerely apology. To solve this problem, I created a TRANSLATING.md file at the root of the repository, containing a lot of information about what should be translated, what shouldn't, and how to get started.

Then each language folder should have its own README.md file containing language-specific notes. I created a template for this here: https://github.com/HugoGiraudel/sass-guidelines/blob/gh-pages/en/README.md. I would really appreciate if you all could copy this template in your own language folder, translate and fill it. Feel free to submit a small pull-request when it is done. Thank you.聽:)

PS: already done for the Portuguese, Danish, German and Polish versions.

PS: I also updated the description of this very issue. :)

Ping @pierrechoffe, @klapec, @matchabros, @morkro, @soniar4i, @davidkpiano, @Grawl, @PavelDemyanenko, @airen, @pinggod, @kimdhoe, @AndersSchmidtHansen, @srescio, @hobi, @ttomdewit, @bartveneman, @varemenos, @margaritis, @magalhini, @Couto, @SaraVieira, @eduardoboucas, @wood1y, @jhonnymoreira, @shadeed.

@morkro
Copy link
Collaborator

@morkro morkro commented Jul 22, 2015

Sure, will add the README.md later 馃憤

@morkro
Copy link
Collaborator

@morkro morkro commented Jul 22, 2015

I got a question regarding the two lists of either translated or untranslated words.

German is a bit of an exception here. We have this ability to turn any foreign word into a valid german one, by keeping the original word and just adding german stuff to it (like adding an article, postfixing it, ...), called Germanising. Where do I list them? It's not really translated in the classical way, but neither kept original. Should I ignore them in general?

I already asked some of my german colleagues and it's a difficult topic. It's still a technical term though, but made fit into proper german grammar.
For instance the term branch. The german term would be Zweig but in a technical context I would still refer to it as "[...] der Branch [...]". It's english though, but the grammar changed to fit into proper german. It could now be used as a German term. :)

So, to sum this up. Is it okay if I may add a third list for "eingedeutschte" (germanised) terms? Does that even make sense and I should maybe just ignore them at all?

Sorry for my little German lession here.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jul 22, 2015

Maybe just explain this in the German README.md? :)

So, to sum this up. Is it okay if I may add a third list for "eingedeutschte" (germanised) terms? Does that even make sense and I should maybe just ignore them at all?

Anything that makes sense. The point of this README is to easy working with contributors.

@morkro
Copy link
Collaborator

@morkro morkro commented Jul 22, 2015

馃憤 good point. I'll just add a little explanation regarding this then.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jul 23, 2015

About 24 hours in, already 4 translations (on 9) have their own README.md. Let me tell that I am very proud to have contributors as you folks. Thank you so much.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Sep 1, 2015

Sass Guidelines 1.2 is live!

Dear friends, Sass Guidelines (EN) version 1.2 just got released with a lot of small additions (and a few bigger ones). A special thanks to @morkro for helping me proofreading everything.

What it means for you as a translator

Depending on the state of your translation, it can mean:

  • Updating it from 1.1 to 1.2 (in the best scenario)
  • Updating it from 1.0 to 1.2 (without forgetting changes from 1.1)
  • Translating it to 1.2 directly. It might be a bit tricky so what you can do I suppose is keep going until you're done with 1.1, and then apply the 1.2 changes. Your call.

In any case, please submit a pull-request (e.g. [WIP] 1.2 French) when you are ready and we will work together to make sure the update is going seamlessly. :)

Changelog

Here it is.

Ping @pierrechoffe, @klapec, @matchabros, @morkro, @soniar4i, @davidkpiano, @Grawl, @PavelDemyanenko, @airen, @pinggod, @kimdhoe, @AndersSchmidtHansen, @srescio, @hobi, @ttomdewit, @bartveneman, @varemenos, @margaritis, @magalhini, @Couto, @SaraVieira, @eduardoboucas, @wood1y, @jhonnymoreira, @shadeed.

@AndersSchmidtHansen
Copy link
Contributor

@AndersSchmidtHansen AndersSchmidtHansen commented Sep 1, 2015

Awesome! Great work!

I'll do my best to squeeze in time for updating the Danish translations. We're swamped with todos right now, so I apologize beforehand if I don't get to updating it in the near future. :)

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Sep 9, 2015

Important warning

Pay attention: the content of the commit 4a44888 about reworking the @extend section has been changed as part of a later pull-request: #259. Be sure to translate the content of that latter PR as well.

Ping @pierrechoffe, @klapec, @matchabros, @morkro, @soniar4i, @davidkpiano, @Grawl, @PavelDemyanenko, @airen, @pinggod, @kimdhoe, @AndersSchmidtHansen, @srescio, @hobi, @ttomdewit, @bartveneman, @varemenos, @margaritis, @magalhini, @Couto, @SaraVieira, @eduardoboucas, @wood1y, @jhonnymoreira, @shadeed.

@magalhini
Copy link
Contributor

@magalhini magalhini commented Sep 15, 2015

Will have a closer look at this sometime this week, @HugoGiraudel ! Thanks for the updates :)

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Nov 26, 2015

Hey there,

It鈥檚 been a while since I haven鈥檛 checked up on you folks! It would be nice if you could give me the current status of your work (if any) for those of you who are moving from 1.1 (or even 1.0) to 1.2, and for those of you who are translating the guidelines in a new language for the first time.

Thank you for your understanding!

Ping @pierrechoffe, @klapec, @matchabros, @morkro, @soniar4i, @davidkpiano, @Grawl, @PavelDemyanenko, @airen, @pinggod, @kimdhoe, @AndersSchmidtHansen, @srescio, @hobi, @ttomdewit, @bartveneman, @varemenos, @margaritis, @magalhini, @Couto, @SaraVieira, @eduardoboucas, @jhonnymoreira, @shadeed, @Mojtabarahimi8.

@varemenos
Copy link
Contributor

@varemenos varemenos commented Nov 26, 2015

The Greek translation is almost done. It will be based on v1.2.
We are in the process of proof reading it.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 3, 2016

Happy New Year dear contributors, and thank you for all the work you did on the guidelines in 2015. Best wishes to y鈥檃ll! Needless to say I am super glad to have you onboard, and hope we can push this project even further in 2016. :)

Let me know if I can do anything to assist you!

@douglasdeodato
Copy link

@douglasdeodato douglasdeodato commented Aug 9, 2016

@HugoGiraudel I can try Help on this, but pt is related to Portuguese from Portugal, pt-br is related to Portuguese from Brazil, Off course is very similar but exist few differences when you write a phrase or word. I could not see pt-br , I will fork the project create a branch and start from scratch , I will try translare a session everyday, I will create a new Issue topic related for that if you don't mind. what do you think? thank you.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Aug 9, 2016

Sure. I鈥檓 fine with having a PT-BR translation if you feel like doing it. Keep me updated. :)

@jhonnymoreira
Copy link

@jhonnymoreira jhonnymoreira commented Aug 10, 2016

@HugoGiraudel I've been through some stuff the last few months and kept myself away from everything related to programming. I got back this month and I saw @douglasdeodato interest on help. I'll try to set things up with him to deliver the most recent translation since I'm available full time right now [=

@douglasdeodato
Copy link

@douglasdeodato douglasdeodato commented Aug 10, 2016

@jhonnymoreira Hi Jhonny , off course we can start do this together why not 馃憤

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 16, 2017

Hey y鈥檃ll lovely contributors! I wish you a happy new year!

Would you mind telling me if you plan on updating your translation (if not up-to-date) or if I should look up for some help from new translators? I鈥檇 like to have a rough idea of the team for the next few months. :)

Best!

@AndersSchmidtHansen
Copy link
Contributor

@AndersSchmidtHansen AndersSchmidtHansen commented Jan 16, 2017

@morkro
Copy link
Collaborator

@morkro morkro commented Jan 16, 2017

I will still maintain the German translation 馃檵馃徎

@soniar4i
Copy link
Contributor

@soniar4i soniar4i commented Jan 16, 2017

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 16, 2017

Ping @klapec, @matchabros, @davidkpiano, @Grawl, @PavelDemyanenko, @airen, @srescio, @hobi, @ttomdewit, @bartveneman, @varemenos, @margaritis, @magalhini, @Couto, @SaraVieira, @eduardoboucas, @jhonnymoreira, @shadeed, @nastiatikk.

(Sorry for the spam, I just would like to make sure everyone can be notified of my last message. 馃槉)

@varemenos
Copy link
Contributor

@varemenos varemenos commented Jan 16, 2017

@margaritis and I will continue supporting the Greek translation.

@SaraVieira
Copy link

@SaraVieira SaraVieira commented Jan 16, 2017

@HugoGiraudel I can take a look at PT-PT translation and see what is missing :)

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 16, 2017

@SaraVieira The Portuguese translation is currently in 1.1 (English in 1.3). If you would like to sync it, I鈥檇 be happy to help you get started. :)

@SaraVieira
Copy link

@SaraVieira SaraVieira commented Jan 16, 2017

@HugoGiraudel Already started by creating the branch and I am going commit by commit to see what is missing.
Should I add a pull request when I reach 1.2 or only on 1.3 ?

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 16, 2017

It depends on how you want to do it. It might be easier to move from 1.1 to 1.2, then 1.2 to 1.3 and therefore to send 2 PRs in total.

Commits from 1.2: https://github.com/HugoGiraudel/sass-guidelines/blob/master/CHANGELOG.md#120-september-1st-2015.
Commits from 1.3: https://github.com/HugoGiraudel/sass-guidelines/blob/master/CHANGELOG.md#130-march-1st-2016

If you have any doubt or question, please ask. :)

@pierrechoffe
Copy link
Contributor

@pierrechoffe pierrechoffe commented Jan 16, 2017

@HugoGiraudel I will continue supporting the French translation.

@SaraVieira
Copy link

@SaraVieira SaraVieira commented Jan 16, 2017

@HugoGiraudel can you please give me push access so I can send the modifications to the branch?

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 16, 2017

@SaraVieira You could also fork the repository on your own GitHub account and create a PR from here? If you cannot do that for any reason, please ask and I鈥檒l give you write access. :)

@pinggod
Copy link
Contributor

@pinggod pinggod commented Jan 17, 2017

@HugoGiraudel

@airen and I will no longer support the Chinese translation(its latest version is 1.3).

@SaraVieira
Copy link

@SaraVieira SaraVieira commented Jan 17, 2017

@HugoGiraudel Np, I forked the repository and I'm bumping it to 1.2

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 17, 2017

@SaraVieira Let me know if I can be of any help.

@pinggod @airen Thank you for all you鈥檝e done. :)

@tenhobi
Copy link

@tenhobi tenhobi commented Jan 23, 2017

@HugoGiraudel tomorrow I will have my last exam in a semester and then I wanna do a big update with translation.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 23, 2017

@hobi Awesome to hear. Let me know if I can help. :)

@kimdhoe
Copy link
Contributor

@kimdhoe kimdhoe commented Jan 31, 2017

@HugoGiraudel I'll catch up slowly. 馃弮

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Jan 31, 2017

@kimdhoe Terrific. If I can help in any way, please ask.

@hunkjazz
Copy link
Contributor

@hunkjazz hunkjazz commented Feb 24, 2018

@HugoGiraudel Do you need help to update portuguese translation?

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Feb 24, 2018

@JLammeer Help is always welcome. The Portuguese translation is 2 versions behind (currently 1.1) so there is quite a bit of work to update it. If you feel like it though, I鈥檒l be happy to merge a PR. :)

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Mar 18, 2018

The Portuguese version has been successfully updated to v1.3 thanks to @JLammeer鈥檚 hard work! Thank you so much. :)

@hunkjazz
Copy link
Contributor

@hunkjazz hunkjazz commented Mar 18, 2018

I'm happy to help.

@HugoGiraudel
Copy link
Owner Author

@HugoGiraudel HugoGiraudel commented Aug 20, 2018

I鈥檓 very happy to announce that the Russian version is now up-to-date in 1.3 thanks to @arbaev fantastic work: https://sass-guidelin.es/ru/!

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

Successfully merging a pull request may close this issue.

None yet
You can鈥檛 perform that action at this time.