Feature: Translate guestbook directions into other languages about guestbook HOT 18 CLOSED

By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂

I think Bekah mentioned issue #81, @CBID2 😄

Yeah I get it now @adiati98.😊 How are you doing with your PR by the way?

The issue just got the green light today. So I haven't worked on it yet as I was outside the whole day 🙂

from guestbook.

@CBID2 here's my suggestion: we make a folder structure that's linked in the ReadMe for the translations. Along with that, we have an issue that's always up that's for translations--we can ask people to comment on the language they would like to work on, and we can add a note that the translations are not actively maintained by the maintainers, but by contributors.

So, the folder structure would look like this:

Translations - This folder holds a README.md that links to folders for each of the translations.

Translations > README

Welcome to our Guestbook translations! Below, you'll find links to the folders of all the translations we currently have. If you'd like to add a translation, check out this issue.

• [French](links to french folder)
• [Portuguese](links to Portuguese folder)

French Folder

 - README.md (this is the file that has the translation)

With all that said, I think we should wait for @adiati98's PR, bc we can't translate the CLI, but we can translate manual changes.

One thing we need to note is that the info they put in must be in English and appear as exactly as it appears for other contributors. Meaning, the spelling can't change. (It breaks the CLI too--ask me how I found out, lol).

from guestbook.

By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂

I think Bekah mentioned issue #81, @CBID2 😄

from guestbook.

@CBID2 I did look into Crowdin. I think we need to make sure there's interest. I'm super excited to have folks interested in translating, but we need to gauge how many people are using the translated versions as part of the discussion. Maybe we should consider adding something to the PR template to ask them to select the language they used to complete the task.

from guestbook.

@CBID2 that would be great!

from guestbook.

@CBID2, because this isn't docsify, we might need to approach it in a different way. Do you have a suggestion for how to do that?

from guestbook.

@CBID2, because this isn't docsify, we might need to approach it in a different way. Do you have a suggestion for how to do that?

#Hi @BekahHW. Great question. I think we can create a sidebar and add a translation feature button.

from guestbook.

@CBID2 this repo is markdown only, though. I don't think you can do that in markdown.

from guestbook.

@CBID2 this repo is markdown only, though. I don't think you can do that in markdown.

@BekahHW, I found some localization tools like Crowdin(Note: freecodeCamp uses this tool to translate their curricula)but they require a monthly fee, so I'm trying to find a free solution.

from guestbook.

@CBID2 here's my suggestion: we make a folder structure that's linked in the ReadMe for the translations. Along with that, we have an issue that's always up that's for translations--we can ask people to comment on the language they would like to work on, and we can add a note that the translations are not actively maintained by the maintainers, but by contributors.

So, the folder structure would look like this:

Translations - This folder holds a README.md that links to folders for each of the translations.

Translations > README

Welcome to our Guestbook translations! Below, you'll find links to the folders of all the translations we currently have. If you'd like to add a translation, check out this issue.

• [French](links to french folder)

• [Portuguese](links to Portuguese folder)

---

French Folder

 - README.md (this is the file that has the translation)

With all that said, I think we should wait for @adiati98's PR, bc we can't translate the CLI, but we can translate manual changes.

One thing we need to note is that the info they put in must be in English and appear as exactly as it appears for other contributors. Meaning, the spelling can't change. (It breaks the CLI too--ask me how I found out, lol).

Great idea @BekahHW! :) We should also wait for French PR that I did with @geoffreylgv

from guestbook.

By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂

from guestbook.

@CBID2 I know. I was referring to Ayu's PR for this issue

from guestbook.

@CBID2 I know. I was referring to Ayu's PR for this issue

Ohh thanks for clarifying @BekahHW. Lol, silly me 🤦🏾‍♀️

from guestbook.

By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂

I think Bekah mentioned issue #81, @CBID2 😄

Yeah I get it now @adiati98.😊 How are you doing with your PR by the way?

from guestbook.

By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂

I think Bekah mentioned issue #81, @CBID2 😄

Yeah I get it now @adiati98.😊 How are you doing with your PR by the way?

The issue just got the green light today. So I haven't worked on it yet as I was outside the whole day 🙂

Ah great. I always find myself to be more focused after exercising outside

from guestbook.

@CBID2 here's my suggestion: we make a folder structure that's linked in the ReadMe for the translations. Along with that, we have an issue that's always up that's for translations--we can ask people to comment on the language they would like to work on, and we can add a note that the translations are not actively maintained by the maintainers, but by contributors.

So, the folder structure would look like this:

Translations - This folder holds a README.md that links to folders for each of the translations.

Translations > README

Welcome to our Guestbook translations! Below, you'll find links to the folders of all the translations we currently have. If you'd like to add a translation, check out this issue.

• [French](links to french folder)
• [Portuguese](links to Portuguese folder)

French Folder

 - README.md (this is the file that has the translation)

With all that said, I think we should wait for @adiati98's PR, bc we can't translate the CLI, but we can translate manual changes.

One thing we need to note is that the info they put in must be in English and appear as exactly as it appears for other contributors. Meaning, the spelling can't change. (It breaks the CLI too--ask me how I found out, lol).

For the project structure related to the translations, we can have like @BekahHW said, Translations folder, and inside have a folder named language country (fr for Français or pt for Portuguese) /Translations/fr/README.md

Also, in the fr folder, we should have the navbar/sidebar in the specific language.

from guestbook.

Hey @BekahHW! 😊 Once and if we get more volunteers to translate, OpenSauced should definitely consider implementing Crowdin. One of the translate leads from FreecodeCamp has shown me how they implement it: https://contribute.freecodecamp.org/#/how-to-translate-files

from guestbook.

@CBID2 I did look into Crowdin. I think we need to make sure there's interest. I'm super excited to have folks interested in translating, but we need to gauge how many people are using the translated versions as part of the discussion. Maybe we should consider adding something to the PR template to ask them to select the language they used to complete the task.

That's a great idea! :) I do a PR for that part if you'd like.

from guestbook.