Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a glossary of common translations and style guide #7

Open
Darking360 opened this issue Oct 2, 2019 · 10 comments
Open

Create a glossary of common translations and style guide #7

Darking360 opened this issue Oct 2, 2019 · 10 comments
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed stale?

Comments

@Darking360
Copy link
Contributor

Darking360 commented Oct 2, 2019

🚨 Create a glossary of common translations and style guide

Motivation

To keep all the translations on the same page, we need to make sure that we use a neutral Spanish and that we use common words for the translations, for example, some people could translate "library" as "libreria" or to "biblioteca", we need to make a consensus on these translations and write them down in an easy accessible document here on the Spanish docs, it could be an MD page or a Wiki, we need to agree on this.

Start

As a really good point to start we can take a look into the glossary of terms from the React translations, which has a pretty good start of common words, discuss them here and start our own.

You can find the guide here.

Discuss

Should we use a page or separate wikis for this? Comment your opinions.

@Darking360 Darking360 added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Oct 2, 2019
@horacioh
Copy link
Contributor

horacioh commented Oct 2, 2019

related PR: #6

@jorgearuv
Copy link
Contributor

Can we have a separate file to add more terms to the list?

@horacioh
Copy link
Contributor

siempre puedes hacer una PR al glosario @jorgeruvalcaba ;)

@jorgearuv
Copy link
Contributor

Excelente! añadiré algunos términos en un momento.

@horacioh
Copy link
Contributor

maybe we can close this since we already have the glosary in place?
cc @Darking360

Darking360 added a commit that referenced this issue Oct 24, 2019
Added 'starter' and 'component shadowing' to the translation glossary #7
@jose4125
Copy link
Contributor

puedo añadir branch a las traducciones comunes? @horacioh @Darking360

@Darking360
Copy link
Contributor Author

Hola @jose4125 claro! Por favor 🚀

@alvaromontoro
Copy link
Contributor

Sé que puede ser un cambio algo trivial, pero la tabla de traducciones comunes no está ordenada alfabéticamente. ¿Está bien si después de terminar la traducción que tengo asignada la pongo en orden A-Z?

@gatsbot
Copy link

gatsbot bot commented Nov 23, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

@iamrahulmahato
Copy link

@Darking360 can we translate to other languages like hindi so other people can understand it

@horacioh horacioh removed their assignment Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed stale?
Projects
None yet
Development

No branches or pull requests

6 participants