Translations Of The Site about makefiletutorial HOT 9 OPEN

The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.

from makefiletutorial.

The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.

Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.

from makefiletutorial.

Woah, GitLocalize sounds super useful. This may not be so hard with it :). I'll think about this more and maybe play around with GitLocalize this weekend, thank you

from makefiletutorial.

@theicfire congratulations for the tutorial. It is just amazing !!
I would love also to contribute in the Spanish translation. Let me know :D

from makefiletutorial.

If this idea go ahead, I would like to maintain the Brazilian Portuguese version.

from makefiletutorial.

Oh I appreciate the offer! Hmm, the issue is I don't have any great immediate ideas on how to go about doing the translations. Some thoughts:

• What happens if there are changes?
• General infrastructure (i.e. letting users select their language, or using geolocation services to select languages)

Are there success stories you know of that talk about simple static website translations and maintenance?

from makefiletutorial.

Hi @theicfire,

I have already contributed the translations of some open source repositories . Let me answer you questions based on my experiences;

What happens if there are changes?
You can either have a manual process (I mean notifying maintainers on every update) or use a tool for this. I have used GitLocalize in some of the projects I involved in. This decision depends on the infrastructure decision.

General infrastructure
One way for managing translations is to ask people to use their forked repositories. You will link them form your main repository or from the site. They have to generate the static sites like you do in the main repository. In this way, handling changes are totally responsibility of the fork repository maintainers. This not the best way for me. For example, Hacker Laws repository manages some of the translations in this way. I am the one maintaining the Turkish repository and I can say that handling the changes are not easy in this way.

Second way is to create a language based folder structure on the main repository. Ask people to maintain the translations on the main repository. The localized static site is generated by you and linked directly from the site by letting user to select the language. For example, PHP - The Wrong Way is a good example for that.

I also involved the translation of Open Source Guides which has the second way infrastructure and it can be accepted as a success story. They generate the static site by using localized content from separate folders.

from makefiletutorial.

The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.

Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.

from makefiletutorial.

@gavinliu6 　　I don't know you've done it. I did it again.

from makefiletutorial.