[Meta] Translation #96

Open
HugoGiraudel opened this Issue Jan 16, 2015 · 69 comments

Projects

None yet
@HugoGiraudel
Owner
HugoGiraudel commented Jan 16, 2015 edited

💢 Update January '17: help wanted for maintaining the Danish 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 gh-pages branch.
  2. Submit a pull request against the gh-pages branch on GitHub.
  3. This is over!

Translations

Status Language Version Translators
Chinese 1.3 @airen, @pinggod
German 1.3 @morkro
French 1.3 @pierrechoffe
Italian 1.3 @MakhBeth, @mattcav
Greek 1.3 @varemenos, @margaritis
❗️ Polish 1.2 @klapec, @matchabros
❗️ Czech 1.1 @HoBi
❗️ Spanish 1.1 @soniar4i, @davidkpiano
❗️ Korean 1.1 @kimdhoe
❗️ Danish 1.1 Help wanted
❗️ Portuguese 1.1 @magalhini, @couto, @saravieira, @eduardoboucas
❗️ Russian 1.0 @grawl, @PavelDemyanenko, @nastiatikk
Brazilian @jhonnymoreira
Arabic @shadeed
Persian @Mojtabarahimi8
Croatian @andrejmlinarevic

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

Mmmh. I will have a look tomorrow.

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

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

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

@codejanovic

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

@HugoGiraudel
Owner

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

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

@HugoGiraudel
Owner

Sass Guidelines EN 1.1 has been released just now.

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

@morkro
Collaborator
morkro commented Jul 22, 2015

Sure, will add the README.md later 👍

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

@morkro
Collaborator
morkro commented Jul 22, 2015

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

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

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

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

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

@magalhini
Contributor

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

@HugoGiraudel
Owner

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
Contributor

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

@HugoGiraudel
Owner

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!

@pierrechoffe
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’amuser 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
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
Owner

Thank you so much @Grawl. I’m 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
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

@Grawl
Contributor
Grawl commented Jan 3, 2016

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

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

@morkro
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
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! :)

@Grawl
Contributor
Grawl commented Jan 18, 2016

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

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

@HugoGiraudel
Owner

Hey @soniar4i, @davidkpiano, @kimdhoe, @AndersSchmidtHansen, @magalhini, @couto, @saravieira, @eduardoboucas. Your translation is currently lagging behind the main one (1.1 against 1.2). Is there anything you need in order to update it? Can I do something to assist you? Or are you waiting for 1.3 to batch both versions into one go? Let me know. :)

@Grawl
Contributor
Grawl commented Jan 18, 2016

Okay, sounds reasonable.

@kimdhoe
Contributor
kimdhoe commented Jan 19, 2016

Korean 1.2 is almost there!

@HugoGiraudel
Owner

@kimdhoe Great news! Looking forward to it. :)

@HugoGiraudel
Owner

Hey there. I just merged PR #314 which introduces a relevant change for you contributors. The _data folder now contains one file per translation instead of a translations.yml and a languages.yml file. This will make diffs easier and generally makes more sense. :)

Existing translations have been updated accordingly so you don’t have to do anything.

@margaritis
Contributor

It does make more sense! 👍

@HugoGiraudel
Owner

Sass Guidelines 1.3 is live!

Dear friends, Sass Guidelines (EN) version 1.3 just got released with a lot of small additions (and a few bigger ones).

What it means for you as a translator

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

  • Updating it from 1.2 to 1.3 (in the best scenario)
  • Updating it from 1.0 or 1.1 to 1.3 (without forgetting changes from 1.1 and 1.2)

In any case, please submit a pull-request (e.g. [WIP] 1.3 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.

@morkro
Collaborator
morkro commented Mar 1, 2016

Awesome 🎉 Will update the German version this week.

@HugoGiraudel
Owner

Hey y’all 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
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
Owner

I’d 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’m 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
Owner

Rethinking the translation system

Hey there. I have been thinking a lot about the current translation “system” recently, only to come to the conclusion that it’s 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’s still far from ideal…

That being said, we have 12 different languages live, and 5 are currently in the pipes. That’s 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’t 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’s be honest, we don’t 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’s 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’t want to force anybody do anything, especially given that it’s a non-profit open-source project. That’s 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 “UI 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’t 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’s 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
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

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

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
Owner

Hello y’all!

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
Owner

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

@douglasdeodato

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

@HugoGiraudel
Owner

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

@douglasdeodato

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

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

@jhonnymoreira

@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

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

@HugoGiraudel
Owner

Hey y’all 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’d like to have a rough idea of the team for the next few months. :)

Best!

@AndersSchmidtHansen
Contributor
AndersSchmidtHansen commented Jan 16, 2017 edited
@morkro
Collaborator
morkro commented Jan 16, 2017

I will still maintain the German translation 🙋🏻

@soniar4i
Contributor
soniar4i commented Jan 16, 2017 edited
@HugoGiraudel
Owner
HugoGiraudel commented Jan 16, 2017 edited

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
Contributor
varemenos commented Jan 16, 2017 edited

@margaritis and I will continue supporting the Greek translation.

@SaraVieira

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

@HugoGiraudel
Owner
HugoGiraudel commented Jan 16, 2017 edited

@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

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

@pierrechoffe
Contributor

@HugoGiraudel I will continue supporting the French translation.

@SaraVieira

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

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

@pinggod
Contributor
pinggod commented Jan 17, 2017

@HugoGiraudel

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

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