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 · 79 comments

Comments

Projects
None yet
@HugoGiraudel
Owner

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
鉂楋笍 Polish 1.2 @klapec, @matchabros
鉂楋笍 Czech 1.1 @hobi
鉂楋笍 Korean 1.1 @kimdhoe
鉂楋笍 Danish 1.1 Help wanted
鉂楋笍 Russian 1.0 @irene-97, @PavelDemyanenko, @nastiatikk, 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 from Translation meta-issue to [Meta] Translation Jan 18, 2015

@srescio

This comment has been minimized.

Show comment
Hide comment
@srescio

srescio 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

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 18, 2015

Owner

Mmmh. I will have a look tomorrow.

Owner

HugoGiraudel commented Jan 18, 2015

Mmmh. I will have a look tomorrow.

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Jan 19, 2015

Contributor

@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.

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 19, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Jan 19, 2015

Contributor

@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---.

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 19, 2015

Owner

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).

Owner

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

This comment has been minimized.

Show comment
Hide comment
@codejanovic

codejanovic Jan 19, 2015

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 19, 2015

Owner

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

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

Owner

HugoGiraudel commented Jan 19, 2015

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Apr 11, 2015

Owner

Sass Guidelines EN 1.1 has been released just now.

Owner

HugoGiraudel commented Apr 11, 2015

Sass Guidelines EN 1.1 has been released just now.

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jul 22, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@morkro

morkro Jul 22, 2015

Collaborator

Sure, will add the README.md later 馃憤

Collaborator

morkro commented Jul 22, 2015

Sure, will add the README.md later 馃憤

@morkro

This comment has been minimized.

Show comment
Hide comment
@morkro

morkro Jul 22, 2015

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jul 22, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@morkro

morkro Jul 22, 2015

Collaborator

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

Collaborator

morkro commented Jul 22, 2015

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jul 23, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Sep 1, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@AndersSchmidtHansen

AndersSchmidtHansen Sep 1, 2015

Contributor

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. :)

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Sep 9, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@magalhini

magalhini Sep 15, 2015

Contributor

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

Contributor

magalhini commented Sep 15, 2015

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Nov 26, 2015

Owner

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.

Owner

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

This comment has been minimized.

Show comment
Hide comment
@varemenos

varemenos Nov 26, 2015

Contributor

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

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 3, 2016

Owner

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!

Owner

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!

@pierrechoffe

This comment has been minimized.

Show comment
Hide comment
@pierrechoffe

pierrechoffe Jan 3, 2016

Contributor

脌 toi aussi mon cher Hugo, je te souhaite une tr猫s belle ann茅e et la r茅alisation de tes voeux les plus chers, tant personnels que professionnels. Continue de bien t鈥檃muser chez ES, petit veinard !
Pierre

Le 3 janv. 2016 脿 16:48, Hugo Giraudel notifications@github.com a 茅crit :

Happy New Year dear contributors, and thank you for all the work you did on the guidelines in 2015. 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!


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

Contributor

pierrechoffe commented Jan 3, 2016

脌 toi aussi mon cher Hugo, je te souhaite une tr猫s belle ann茅e et la r茅alisation de tes voeux les plus chers, tant personnels que professionnels. Continue de bien t鈥檃muser chez ES, petit veinard !
Pierre

Le 3 janv. 2016 脿 16:48, Hugo Giraudel notifications@github.com a 茅crit :

Happy New Year dear contributors, and thank you for all the work you did on the guidelines in 2015. 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!


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

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Jan 3, 2016

Contributor

I am happy to be onboard! Also I'm planning to finally update russian translation up to latest version because I'm sharing it too much because this guideline is crazy good to start with.

Contributor

Grawl commented Jan 3, 2016

I am happy to be onboard! Also I'm planning to finally update russian translation up to latest version because I'm sharing it too much because this guideline is crazy good to start with.

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 3, 2016

Owner

Thank you so much @Grawl. I鈥檓 really looking forward to have the Russian translation up to date with the English one as it is the most needed and read translations of all. :)

Owner

HugoGiraudel commented Jan 3, 2016

Thank you so much @Grawl. I鈥檓 really looking forward to have the Russian translation up to date with the English one as it is the most needed and read translations of all. :)

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 3, 2016

Owner

In case you are interested, here are the numbers for the period 01.09.2015 鈥 01.01.2016.

screen shot 2016-01-03 at 17 04 37

Owner

HugoGiraudel commented Jan 3, 2016

In case you are interested, here are the numbers for the period 01.09.2015 鈥 01.01.2016.

screen shot 2016-01-03 at 17 04 37

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Jan 3, 2016

Contributor

Wow! Russian translation is very popular. It's a great reason for me to update it :)

Contributor

Grawl commented Jan 3, 2016

Wow! Russian translation is very popular. It's a great reason for me to update it :)

@varemenos

This comment has been minimized.

Show comment
Hide comment
@varemenos

varemenos Jan 3, 2016

Contributor

Happy new year everyone!
Damn those numbers are nice, didn't expect so much traffic for the translated versions.

The greek translation was again delayed but we are almost there (like 99% of it is done). I will be leaving for my 9 month mandatory military service in the 20th of this month so it will definitely be done by then.

Contributor

varemenos commented Jan 3, 2016

Happy new year everyone!
Damn those numbers are nice, didn't expect so much traffic for the translated versions.

The greek translation was again delayed but we are almost there (like 99% of it is done). I will be leaving for my 9 month mandatory military service in the 20th of this month so it will definitely be done by then.

@morkro

This comment has been minimized.

Show comment
Hide comment
@morkro

morkro Jan 4, 2016

Collaborator

Great traffic info, thanks :)
Would be great to see how many countries are visiting the english version though. For instance German is very low, is the rest browsing the English version or are Germans rare in general?

Collaborator

morkro commented Jan 4, 2016

Great traffic info, thanks :)
Would be great to see how many countries are visiting the english version though. For instance German is very low, is the rest browsing the English version or are Germans rare in general?

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 18, 2016

Owner

Hey there!

The Greek translation of Sass-Guidelines has finally been finished and released this morning, thanks to great work from our friends in Greece. 馃帀

I also took this as an opportunity to remove the third component of version numbers as it turns out to be completely obsolete. We will now refer to version as 1.0, 1.1, 1.2, 1.3, etc.

Speaking of which, there currently is a pull request in progress for version 1.3 if you are curious: #292.

Best! :)

Owner

HugoGiraudel commented Jan 18, 2016

Hey there!

The Greek translation of Sass-Guidelines has finally been finished and released this morning, thanks to great work from our friends in Greece. 馃帀

I also took this as an opportunity to remove the third component of version numbers as it turns out to be completely obsolete. We will now refer to version as 1.0, 1.1, 1.2, 1.3, etc.

Speaking of which, there currently is a pull request in progress for version 1.3 if you are curious: #292.

Best! :)

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Jan 18, 2016

Contributor

Moving from semver? Better using it, or it will too hard to maintain?

Contributor

Grawl commented Jan 18, 2016

Moving from semver? Better using it, or it will too hard to maintain?

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 18, 2016

Owner

The thing is we do not really need SemVer, and more than that: we cannot really use SemVer. As a reminder, for Sass-Guidelines the version number is used to keep translations in sync. If the document was only in English, it would not need to be versioned.

In theory, the third component of a SemVer version number is used for bug fixes. In this project, it would mean typos. Typos are not versioned; they are directly merged in the main branch.

Which leaves us with version bumps used for additions, updates and removals of content, such as those which happened in 1.1, 1.2 and soon 1.3. These need to be bundled in versions so that contributors like you can actually see what happened on the English version and update their translation accordingly.

Hope it makes it clearer. :)

Owner

HugoGiraudel commented Jan 18, 2016

The thing is we do not really need SemVer, and more than that: we cannot really use SemVer. As a reminder, for Sass-Guidelines the version number is used to keep translations in sync. If the document was only in English, it would not need to be versioned.

In theory, the third component of a SemVer version number is used for bug fixes. In this project, it would mean typos. Typos are not versioned; they are directly merged in the main branch.

Which leaves us with version bumps used for additions, updates and removals of content, such as those which happened in 1.1, 1.2 and soon 1.3. These need to be bundled in versions so that contributors like you can actually see what happened on the English version and update their translation accordingly.

Hope it makes it clearer. :)

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Mar 3, 2016

Owner

Hey y鈥檃ll beautiful people!

I would like to know if I can do anything to assist you in updating your translation to version 1.3. Do you feel confident upgrading it in the next few weeks? Else, shall I find you some support? Please, be sure to tell.

For instance, @nastiatikk is joining the Russian team to take over the current state of the Russian translation because @Grawl and @PavelDemyanenko do not have enough time. Welcome onboard!

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

Owner

HugoGiraudel commented Mar 3, 2016

Hey y鈥檃ll beautiful people!

I would like to know if I can do anything to assist you in updating your translation to version 1.3. Do you feel confident upgrading it in the next few weeks? Else, shall I find you some support? Please, be sure to tell.

For instance, @nastiatikk is joining the Russian team to take over the current state of the Russian translation because @Grawl and @PavelDemyanenko do not have enough time. Welcome onboard!

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

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Mar 3, 2016

Contributor

I found git too hard to update translations. Maybe some crowdsource translating service (like ones noticed in this Quora page) will be better. Hunting for changes in commits for each file is terrible, but raw diff lurking is even harder.

Contributor

Grawl commented Mar 3, 2016

I found git too hard to update translations. Maybe some crowdsource translating service (like ones noticed in this Quora page) will be better. Hunting for changes in commits for each file is terrible, but raw diff lurking is even harder.

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Mar 3, 2016

Owner

I鈥檇 argue the difficulty to update the Russian translation partially comes from the fact that it is lagging behind by 3 versions. However I will definitely concede that content translation process could be improved, and I鈥檓 well willing to investigate any possibility.

Maybe instead of bundling a lot of changes in versions (1.1, 1.2, 1.3鈥), we could push changes one commit at a time? Translation work would be more frequent but much simpler?

On my end, I already made sure that no translation file has any HTML for instance, to make sure diffs are not polluted with irrelevant changes.

Owner

HugoGiraudel commented Mar 3, 2016

I鈥檇 argue the difficulty to update the Russian translation partially comes from the fact that it is lagging behind by 3 versions. However I will definitely concede that content translation process could be improved, and I鈥檓 well willing to investigate any possibility.

Maybe instead of bundling a lot of changes in versions (1.1, 1.2, 1.3鈥), we could push changes one commit at a time? Translation work would be more frequent but much simpler?

On my end, I already made sure that no translation file has any HTML for instance, to make sure diffs are not polluted with irrelevant changes.

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Mar 3, 2016

Owner

Rethinking the translation system

Hey there. I have been thinking a lot about the current translation 鈥渟ystem鈥 recently, only to come to the conclusion that it鈥檚 really not great even if it seems to work. It has certainly gotten much better over the past year (some of you might remember the early days when the whole guidelines were in a single file). However, it鈥檚 still far from ideal鈥

That being said, we have 12 different languages live, and 5 are currently in the pipes. That鈥檚 huge for such a small open-source project. We have to find a way to make it work for everybody, and in the simplest way possible.

What currently doesn鈥檛 work?

Translating the guidelines in a new language from scratch is actually not too hard. The main problem right now is updating a translation. Which is actually the most part of the translation work on Sass Guidelines. Let鈥檚 be honest, we don鈥檛 add a new language every day.

Their are two concurrent problems: it is hard to figure out what changed, and new versions are somewhat large (usually a dozen commits, involving a couple of hours of translation work). The current process for updating a translation is to check the changelog, and to reproduce commits one by one. Not ideal. Translators do not really care about why something changed. They just want to know what changed and what they have to do on their translation to make it up-to-date.

This also means that translators currently need a bit of Git knowledge and that really sucks. Translation work has nothing to do with versioning, and someone with little to no technical background should be able to join and help. GitHub interface is able to bridge the gap a little, but I am not sure it鈥檚 enough given the current state of things. Which leads me to the next point.

On top of that, translators currently have to have some knowledge about the project and its technical setup. It is not mandatory to be able to run the project locally, but knowing where to find what and how it generally works appears like a prerequisite right now. Still, it should not. A translator should not have to know anything about the project setup. They should only be presented with content to be translated. Ideally, this content should be decoupled from any technical consideration.

Last but not least, as of today translators join to maintain a full version. While it is very good for consistency, it also asks a lot of time from them, sometimes more time than they can actually afford. I don鈥檛 want to force anybody do anything, especially given that it鈥檚 a non-profit open-source project. That鈥檚 also why I think the current system is broken. Someone should be able to come and translate a few sentences then leave, the same way translations work on Wikipedia for instance. Then, everybody could participate as much as they want, little by little.

What can we do?

I will be entirely honest with you and admit that I am not sure. I have little to no experience with internationalisation, and Sass Guidelines is pretty much a playground for me here. Needless to say I am incredibly happy and lucky to have you all onboard and willing to help making this project available for the many. 12 languages is more than I ever wished for, and I sincerely hope we can onboard even more in the future.

But if we want to make this work on the long run, and be able to onboard new translators for existing or new languages, we need to simplify the way it works right now.

I suppose that the best way would be to move towards a dictionary based system. Basically, every single chunk of content should be mapped to a key, that would be shared between all translations. The Jekyll layer would get the correct content based on the current language and the key. This is how it works right now with the 鈥淯I translations鈥 in the _locales folder (Twitter button, donate partial, site baseline, etc.). We would need this for the whole thing, not only the UI.

So the first solution would be for me to move all the content to these locale files. Then, the Jekyll layer would be only about including the right keys at the right place. Every single word, phrase, sentence or paragraph would live inside YAML files. That would make it easy for anyone to just update a translation from the GitHub UI for instance.

Or we could look at third party services. We could either have a web interface to access these dictionaries (format to be defined: YAML, XLIFF, JSON, PO, etc.) or a desktop application even if I think that makes it harder so probably not a good idea. I found these tools:

  • Pootle: needs to be installed on a web server;
  • Poedit: desktop application;
  • Zanata: software as a service;
  • POEditor: has a nice free plan and looks gorgeous;
  • Transifex: too expensive.

I need to benchmark them a bit because I have no clue how they work. POEditor looks very nice and usable as far as I can tell. Tried it a bit, the UI is lovely and simple enough.

Then translating some content or updating a translation would be as simple as accessing the dictionary of the relevant language (via a web UI for instance), change the content and save it. On my side, I will have to sync and deploy the translations on a regular basis, but that is really the easy part at this point.

Any thought?

So here we are folks. I need your opinion on this.
What do you like in the current workflow?
What don鈥檛 you like?
What do you find annoying?
What would be ideal for you?
Do you have any hint?
Do you have any experience on translating content through a third-party service?
Please, speak your mind freely. I am really interested in anyone鈥檚 opinion.

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

Owner

HugoGiraudel commented Mar 3, 2016

Rethinking the translation system

Hey there. I have been thinking a lot about the current translation 鈥渟ystem鈥 recently, only to come to the conclusion that it鈥檚 really not great even if it seems to work. It has certainly gotten much better over the past year (some of you might remember the early days when the whole guidelines were in a single file). However, it鈥檚 still far from ideal鈥

That being said, we have 12 different languages live, and 5 are currently in the pipes. That鈥檚 huge for such a small open-source project. We have to find a way to make it work for everybody, and in the simplest way possible.

What currently doesn鈥檛 work?

Translating the guidelines in a new language from scratch is actually not too hard. The main problem right now is updating a translation. Which is actually the most part of the translation work on Sass Guidelines. Let鈥檚 be honest, we don鈥檛 add a new language every day.

Their are two concurrent problems: it is hard to figure out what changed, and new versions are somewhat large (usually a dozen commits, involving a couple of hours of translation work). The current process for updating a translation is to check the changelog, and to reproduce commits one by one. Not ideal. Translators do not really care about why something changed. They just want to know what changed and what they have to do on their translation to make it up-to-date.

This also means that translators currently need a bit of Git knowledge and that really sucks. Translation work has nothing to do with versioning, and someone with little to no technical background should be able to join and help. GitHub interface is able to bridge the gap a little, but I am not sure it鈥檚 enough given the current state of things. Which leads me to the next point.

On top of that, translators currently have to have some knowledge about the project and its technical setup. It is not mandatory to be able to run the project locally, but knowing where to find what and how it generally works appears like a prerequisite right now. Still, it should not. A translator should not have to know anything about the project setup. They should only be presented with content to be translated. Ideally, this content should be decoupled from any technical consideration.

Last but not least, as of today translators join to maintain a full version. While it is very good for consistency, it also asks a lot of time from them, sometimes more time than they can actually afford. I don鈥檛 want to force anybody do anything, especially given that it鈥檚 a non-profit open-source project. That鈥檚 also why I think the current system is broken. Someone should be able to come and translate a few sentences then leave, the same way translations work on Wikipedia for instance. Then, everybody could participate as much as they want, little by little.

What can we do?

I will be entirely honest with you and admit that I am not sure. I have little to no experience with internationalisation, and Sass Guidelines is pretty much a playground for me here. Needless to say I am incredibly happy and lucky to have you all onboard and willing to help making this project available for the many. 12 languages is more than I ever wished for, and I sincerely hope we can onboard even more in the future.

But if we want to make this work on the long run, and be able to onboard new translators for existing or new languages, we need to simplify the way it works right now.

I suppose that the best way would be to move towards a dictionary based system. Basically, every single chunk of content should be mapped to a key, that would be shared between all translations. The Jekyll layer would get the correct content based on the current language and the key. This is how it works right now with the 鈥淯I translations鈥 in the _locales folder (Twitter button, donate partial, site baseline, etc.). We would need this for the whole thing, not only the UI.

So the first solution would be for me to move all the content to these locale files. Then, the Jekyll layer would be only about including the right keys at the right place. Every single word, phrase, sentence or paragraph would live inside YAML files. That would make it easy for anyone to just update a translation from the GitHub UI for instance.

Or we could look at third party services. We could either have a web interface to access these dictionaries (format to be defined: YAML, XLIFF, JSON, PO, etc.) or a desktop application even if I think that makes it harder so probably not a good idea. I found these tools:

  • Pootle: needs to be installed on a web server;
  • Poedit: desktop application;
  • Zanata: software as a service;
  • POEditor: has a nice free plan and looks gorgeous;
  • Transifex: too expensive.

I need to benchmark them a bit because I have no clue how they work. POEditor looks very nice and usable as far as I can tell. Tried it a bit, the UI is lovely and simple enough.

Then translating some content or updating a translation would be as simple as accessing the dictionary of the relevant language (via a web UI for instance), change the content and save it. On my side, I will have to sync and deploy the translations on a regular basis, but that is really the easy part at this point.

Any thought?

So here we are folks. I need your opinion on this.
What do you like in the current workflow?
What don鈥檛 you like?
What do you find annoying?
What would be ideal for you?
Do you have any hint?
Do you have any experience on translating content through a third-party service?
Please, speak your mind freely. I am really interested in anyone鈥檚 opinion.

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

@Grawl

This comment has been minimized.

Show comment
Hide comment
@Grawl

Grawl Mar 3, 2016

Contributor

I have an experience with Poedit and gettext and found it nice to work with. But I have nothing to say about updates. Nor I translated a content once, nor a few updates, but not versions.

Contributor

Grawl commented Mar 3, 2016

I have an experience with Poedit and gettext and found it nice to work with. But I have nothing to say about updates. Nor I translated a content once, nor a few updates, but not versions.

@lgiraudel

This comment has been minimized.

Show comment
Hide comment
@lgiraudel

lgiraudel Mar 3, 2016

In my opinion you should:

  • extract translations in dedicated files with a key / value pair. In some formats, it's possible to use complex keys so it should be possible to use the english version as a key (but keep the possibility to overload the english version)
  • extract translation files in a dedicated repository, used as a submodule: it will permit to send PR notifications to translators for changes in translations and not for changes in the source code. The best would be to trigger notifications only when the default version (english one) has some changes and not for every translation PR.

In my opinion you should:

  • extract translations in dedicated files with a key / value pair. In some formats, it's possible to use complex keys so it should be possible to use the english version as a key (but keep the possibility to overload the english version)
  • extract translation files in a dedicated repository, used as a submodule: it will permit to send PR notifications to translators for changes in translations and not for changes in the source code. The best would be to trigger notifications only when the default version (english one) has some changes and not for every translation PR.
@martinschaible

This comment has been minimized.

Show comment
Hide comment
@martinschaible

martinschaible Mar 3, 2016

I worked recently on a translation project for a CMS (PresideCMS from the UK). The team used Zanata, which worked out very well. Very comfortable and easy to use. The output was managed by the project leader and the string ended in their repository as files with the extension ".properties." The problems i experienced are more on the human side:

  • People translated text without using the software, ending having translated strings without a context.
  • Not enough space in the UI: German strings are needing more space rather than english strings. French strings are consuming sometimes 50% more space rather than the english strings.
  • Sometimes technical strings where, let's say "overtranslated". E.G. a "Spool folder" can be translated to "Spool-Ordner" for the german language.
  • For a lot of CMS related translations, the world is using a kind of standardized strings. It might help to see how other products are looking in a foreign language.

In a other project (Pydio from France) i worked, we had to edit the i18n files directly. This worked out pretty good too. The benefit was, that a search and replace for some simple strings-types where possible, which saves time. The problem might be a merge in the repository, if several people are working on the same files. This can cost time for sure.

Independly, how the translation is organized, future updates can cause problems. E.g. The application gets new strings, which needs more translation.

I think, it is important, that the translated strings of an application are splitted to many smaller modules instead of having a big file.

I worked recently on a translation project for a CMS (PresideCMS from the UK). The team used Zanata, which worked out very well. Very comfortable and easy to use. The output was managed by the project leader and the string ended in their repository as files with the extension ".properties." The problems i experienced are more on the human side:

  • People translated text without using the software, ending having translated strings without a context.
  • Not enough space in the UI: German strings are needing more space rather than english strings. French strings are consuming sometimes 50% more space rather than the english strings.
  • Sometimes technical strings where, let's say "overtranslated". E.G. a "Spool folder" can be translated to "Spool-Ordner" for the german language.
  • For a lot of CMS related translations, the world is using a kind of standardized strings. It might help to see how other products are looking in a foreign language.

In a other project (Pydio from France) i worked, we had to edit the i18n files directly. This worked out pretty good too. The benefit was, that a search and replace for some simple strings-types where possible, which saves time. The problem might be a merge in the repository, if several people are working on the same files. This can cost time for sure.

Independly, how the translation is organized, future updates can cause problems. E.g. The application gets new strings, which needs more translation.

I think, it is important, that the translated strings of an application are splitted to many smaller modules instead of having a big file.

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Apr 4, 2016

Owner

Hello y鈥檃ll!

What is the current status with the update of your translation to 1.3? Shall I try to find some help for you on Twitter maybe? Please keep me updated. :)

Cheers!

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

Owner

HugoGiraudel commented Apr 4, 2016

Hello y鈥檃ll!

What is the current status with the update of your translation to 1.3? Shall I try to find some help for you on Twitter maybe? Please keep me updated. :)

Cheers!

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jun 4, 2016

Owner

I am super happy to introduce the Italian version (1.3) to the party: https://sass-guidelin.es/it/! 馃帀

Owner

HugoGiraudel commented Jun 4, 2016

I am super happy to introduce the Italian version (1.3) to the party: https://sass-guidelin.es/it/! 馃帀

@douglasdeodato

This comment has been minimized.

Show comment
Hide comment
@douglasdeodato

douglasdeodato Aug 9, 2016

@HugoGiraudel what is the story about the pt-br translate?

@HugoGiraudel what is the story about the pt-br translate?

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Aug 9, 2016

Owner

I think the main problem right now is that it鈥檚 not up to date. :)

Owner

HugoGiraudel commented Aug 9, 2016

I think the main problem right now is that it鈥檚 not up to date. :)

@douglasdeodato

This comment has been minimized.

Show comment
Hide comment
@douglasdeodato

douglasdeodato 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 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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Aug 9, 2016

Owner

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

Owner

HugoGiraudel commented Aug 9, 2016

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

@jhonnymoreira

This comment has been minimized.

Show comment
Hide comment
@jhonnymoreira

jhonnymoreira 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 [=

@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

This comment has been minimized.

Show comment
Hide comment
@douglasdeodato

douglasdeodato Aug 10, 2016

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 16, 2017

Owner

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!

Owner

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

This comment has been minimized.

Show comment
Hide comment
@AndersSchmidtHansen

AndersSchmidtHansen Jan 16, 2017

Contributor
Contributor

AndersSchmidtHansen commented Jan 16, 2017

@morkro

This comment has been minimized.

Show comment
Hide comment
@morkro

morkro Jan 16, 2017

Collaborator

I will still maintain the German translation 馃檵馃徎

Collaborator

morkro commented Jan 16, 2017

I will still maintain the German translation 馃檵馃徎

@soniar4i

This comment has been minimized.

Show comment
Hide comment
@soniar4i

soniar4i Jan 16, 2017

Contributor
Contributor

soniar4i commented Jan 16, 2017

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
Owner

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

This comment has been minimized.

Show comment
Hide comment
@varemenos

varemenos Jan 16, 2017

Contributor

@margaritis and I will continue supporting the Greek translation.

Contributor

varemenos commented Jan 16, 2017

@margaritis and I will continue supporting the Greek translation.

@SaraVieira

This comment has been minimized.

Show comment
Hide comment
@SaraVieira

SaraVieira Jan 16, 2017

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 16, 2017

Owner

@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. :)

Owner

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

This comment has been minimized.

Show comment
Hide comment
@SaraVieira

SaraVieira 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 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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 16, 2017

Owner

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. :)

Owner

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

This comment has been minimized.

Show comment
Hide comment
@pierrechoffe

pierrechoffe Jan 16, 2017

Contributor

@HugoGiraudel I will continue supporting the French translation.

Contributor

pierrechoffe commented Jan 16, 2017

@HugoGiraudel I will continue supporting the French translation.

@SaraVieira

This comment has been minimized.

Show comment
Hide comment
@SaraVieira

SaraVieira Jan 16, 2017

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 16, 2017

Owner

@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. :)

Owner

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

This comment has been minimized.

Show comment
Hide comment
@pinggod

pinggod Jan 17, 2017

Contributor

@HugoGiraudel

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

Contributor

pinggod commented Jan 17, 2017

@HugoGiraudel

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

@SaraVieira

This comment has been minimized.

Show comment
Hide comment
@SaraVieira

SaraVieira Jan 17, 2017

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

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

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 17, 2017

Owner

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

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

Owner

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

This comment has been minimized.

Show comment
Hide comment
@tenhobi

tenhobi Jan 23, 2017

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

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 23, 2017

Owner

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

Owner

HugoGiraudel commented Jan 23, 2017

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

@kimdhoe

This comment has been minimized.

Show comment
Hide comment
@kimdhoe

kimdhoe Jan 31, 2017

Contributor

@HugoGiraudel I'll catch up slowly. 馃弮

Contributor

kimdhoe commented Jan 31, 2017

@HugoGiraudel I'll catch up slowly. 馃弮

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Jan 31, 2017

Owner

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

Owner

HugoGiraudel commented Jan 31, 2017

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

@JLammeer

This comment has been minimized.

Show comment
Hide comment
@JLammeer

JLammeer Feb 24, 2018

Contributor

@HugoGiraudel Do you need help to update portuguese translation?

Contributor

JLammeer commented Feb 24, 2018

@HugoGiraudel Do you need help to update portuguese translation?

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Feb 24, 2018

Owner

@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. :)

Owner

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

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Mar 18, 2018

Owner

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

Owner

HugoGiraudel commented Mar 18, 2018

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

@JLammeer

This comment has been minimized.

Show comment
Hide comment
@JLammeer

JLammeer Mar 18, 2018

Contributor

I'm happy to help.

Contributor

JLammeer commented Mar 18, 2018

I'm happy to help.

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