[Meta] Translation

[KittyGiraudel]

💢 Update March 2021: help wanted for maintaining the Polish, Czech and Danish translations.

Let me open this issue so that I can talk to all of you kind folks who agreed to translate the guidelines. 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 the CHANGELOG.md.

Submitting your work

1. Make sure your version is up-to-date with the current main branch.
2. Submit a pull request against the main 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, @modkaffes, @sebdesign
✅	Spanish	1.3	@soniar4i, @davidkpiano
✅	Portuguese	1.3	@magalhini, @Couto, @SaraVieira, @eduardoboucas, @hunkjazz
✅	Russian	1.3	@irene-97, @PavelDemyanenko, @nastiatikk, @arbaev
✅	Korean	1.3	@kimdhoe @woochul2
✅	Dutch	1.3	@noah-vdv
❗	Polish	1.2	@klapec, @matchabros
❗	Czech	1.1	@hobi
❗	Danish	1.1	Help wanted

✅ means up-to-date.
❗ means not up-to-date.
❌ means in progress.

[srescio]

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

[KittyGiraudel]

Mmmh. I will have a look tomorrow.

[Grawl]

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

[KittyGiraudel]

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]

@KittyGiraudel please note that only latin characters remains. Russian language don't have any latin characters so remains only words like “Sass” 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---.

[KittyGiraudel]

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]

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

[KittyGiraudel]

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

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

[KittyGiraudel]

Sass Guidelines EN 1.1 has been released just now.

[KittyGiraudel]

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/KittyGiraudel/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]

Sure, will add the README.md later 👍

[morkro]

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.

[KittyGiraudel]

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]

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

[KittyGiraudel]

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.

[KittyGiraudel]

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]

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

[KittyGiraudel]

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]

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

[KittyGiraudel]

Hey there,

It’s been a while since I haven’t 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]

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

[KittyGiraudel]

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

[morkro]

I will still maintain the German translation 🙋🏻

[soniar4i]

Hi everyone! I hope I can update the spanish version soon :)

[KittyGiraudel]

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]

@margaritis and I will continue supporting the Greek translation.

[SaraVieira]

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

[KittyGiraudel]

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

[SaraVieira]

@KittyGiraudel 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 ?

[KittyGiraudel]

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/KittyGiraudel/sass-guidelines/blob/master/CHANGELOG.md#120-september-1st-2015.
Commits from 1.3: https://github.com/KittyGiraudel/sass-guidelines/blob/master/CHANGELOG.md#130-march-1st-2016

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

[pierrechoffe]

@KittyGiraudel I will continue supporting the French translation.

[SaraVieira]

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

[KittyGiraudel]

@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’ll give you write access. :)

[thinkininfinity]

@KittyGiraudel

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

[SaraVieira]

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

[KittyGiraudel]

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

@PINGGOD @airen Thank you for all you’ve done. :)

[tenhobi]

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

[KittyGiraudel]

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

[kimdhoe]

@KittyGiraudel I'll catch up slowly. 🏃

[KittyGiraudel]

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

[hunkjazz]

@KittyGiraudel Do you need help to update portuguese translation?

[KittyGiraudel]

@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’ll be happy to merge a PR. :)

[KittyGiraudel]

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

[hunkjazz]

I'm happy to help.

[KittyGiraudel]

I’m 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/! ✨

[KittyGiraudel]

Super excited to announce that we now have a Dutch version of Sass Guidelines thanks to @noah-vdv: https://sass-guidelin.es/nl/! 🎉

[KittyGiraudel]

Hello friends,

I realized it would be nice to have the translation disclaimer in the current page language instead of always in English.

See screenshot

So I was wondering if you could help me translate these 2 sentences.

You are viewing the {language} translation from {translator A} and {translator B} of the original Sass Guidelines from Kitty Giraudel.

This version is exclusively maintained by contributors without the review of the main author, therefore might not be completely authentic.

Note:

• {language} is the name of your language.
• I will replace {translator A} and {translator B} (and more when needed) with your names. 😅
• I will deal with the implementation, I just need your help with translations. :)

Thank you! 💖

---

Translations:

• CZ
• DA
• DE
• EL
• EN
• ES
• FR
• IT
• KO
• NL
• PL
• PT
• RU
• ZH

[strangernr7]

U bekijkt de nederlandse vertaling van Noah van der Veer van de originele Sass Guidelines van Kitty Giraudel.

Deze versie wordt exclusief onderhouden door bijdragers zonder de beoordeling van de hoofdauteur en is daarom mogelijk niet volledig authentiek.

[morkro]

Thank you @KittyGiraudel! Here's the German version:

Du schaust dir gerade die deutsche Übersetzung von Moritz Kröger der originalen Sass Guidelines von Kitty Giraudel an.

Diese Version wird exklusiv durch die Übersetzer gepflegt, ohne zusätzliche Überprüfung des Hauptautors, und mag deshalb nicht vollständig authentisch sein.

[varemenos]

Here is the Greek version, courtesy of @modkaffes

Βλέπετε την ελληνική μετάφραση των Μόδεστο Καφφέ, Σεμπαστιέν Νικολάου, Άδωνη Κακουλίδη και Κωνσταντίνου Μαργαρίτη για τις πρωτότυπες Οδηγίες για Sass των Kitty Giraudel.
Αυτή η έκδοση συντηρείται αποκλειστικά από συνεισφέροντες χωρίς τον έλεγχο του κύριου συντάκτη, επομένως μπορεί να μην είναι εντελώς αυθεντική.

@KittyGiraudel could you please include @modkaffes and @sebdesign in the list of Greek translators? They are included in the website but not in this issue (which is most likely my fault 😞).

[MakhBeth]

Stai leggendo la traduzione italiana di Davide Di Pumpo e Matteo Cavucci delle originali linee guida per Sass di Kitty Giraudel.

Questa versione è mantenuta esclusivamente dai collaboratori, senza la revisione dell'autore principale. Per questo potrebbe non essere completamente autentica.