Portuguese (Portugal) Translation Progress #1
Comments
|
@fjoshuajr @jbarradas uma questão que me surgiu agora que comecei a traduzir. Eu estou a traduzir de modo a dirigir-me a tu e não a você. Exemplo básico:
Que abordagem devemos usar? |
|
@telmogoncalves sou a favor de Experimente. |
|
E como já começaste a traduzir, existem alguns pontos que temos que discutir.
E tomar em consideração o Universal Style Guide. |
|
@fjoshuajr vou alterar então, que eu estava a ir com a abordagem tu. Em relação às palavras que podem ou não ser traduzidas concordo contigo, eu já vi algures alguém a falar sobre isso, quando encontrar meto aqui. |
|
E também acho que devemos capitalizar a primeira palavra nos títulos. |
|
I’ve created a Slack called react-translations. If you guys think it’s easier to discuss some topics there let me know and I’ll invite you 👍 |
|
@telmogoncalves is that slack for just Portuguese or for all translators? :P |
|
All translators 😊 I was thinking about creating channels for the different languages. |
|
@telmogoncalves if you do, use Discord instead. Slack has a 10K message limit in their free tier. |
|
@fjoshuajr you think the 10k limit will be a problem? |
|
@fjoshuajr @jbarradas thoughts? |
|
How about we bring it up with the larger github group? (https://github.com/orgs/reactjs/teams/reactjs-org-localization) I know a lot of the other languages have Slack / Discord / LINE / WhatsApp / Spectrum / Weibo already -- another channel of communication might make things more confusing. |
|
That sounds good. I can ping them tomorrow morning if no one does. |
|
I agree with a global slack (or whatever) with different channels for each language. This way we can exchange ideas between mantainers of different languages. |
|
Technically, the github team is supposed to be that. I'd prefer relying on something within github itself so we don't require maintainers to get yet another account on something else. But I guess it's not really amenable to real-time chat. |
+1 |
|
@fjoshuajr @jbarradas let's probably wait to see if it's OK with @tesseralis. |
Is this regarding a live chat? Just create a room for us (you can send invitation for slack). As she said, we should use GitHub the most we can, so things get in record and centralized. We should use live chat just for quick questions/decisions between us. And try to put every important decision in Github some way. What you guys think? |
Yeah, we can do that. I'll be needing emails do add to slack. |
Invite me 🤓 |
|
May I translate Home Page? |
|
@nelsonmfinda assigned to Home Page, thanks! |
|
@telmogoncalves can you invite me to the slack and make me admin? Thinking about it, I think it's useful to have one central source for ephemeral discussion (the Polish group already started a spectrum, haha). I think I'll make it official and put it in the documentation / set up a way to automate adding people to the slack. |
@tesseralis The link https://github.com/orgs/reactjs/teams/reactjs-org-localization not found 😞 |
|
@nelsonmfinda sorry, it's the secret group available only to maintainers ^_^ |
|
@tesseralis no problem. |
|
@fjoshuajr @imflavio Can you please join us in Slack? We should handle some superficial discussions, translations suggestions, etc, in there. Instead of filling github with non-relevant comments. Appreciate! :) |
|
Hi everyone! |
|
@nelsonmfinda Only for context words and expressions I'm using Reverso and Linguee. And a lot of common sense. Sometimes the English sentence says more than we would say in Portuguese. Sometimes it says less than we would. So, we need to be careful to not translate things literally, step back, and think how would we say "that" in a fluent way. If you need translation suggestions, please head to the slack channel ;) |
|
Thanks @jbarradas |
|
Português/Portuguese: (Eu removo este comentário, se tiver abusado de algum modo. Eu só queria pedir ajuda e ajudar, peço desculpa) (Peço desculpa, por ser muito longo) Tem a tradução deste projeto num site chamado Crowdin https://crowdin.com/ , Onde é feito a localização (explicação da diferença de localização de tradução https://content.lionbridge.com/the-difference-between-translation-and-localization-for-multilingual-website-projects-definitions/ ou https://www.vengaglobal.com/blog/translation-localization-difference/ (explica um pouco melhor)) deste projeto e é bem mais fácil de traduzir lá (imagens do Editor do Crowdin https://support.crowdin.com/online-editor/ (é a versão antiga que está nas imagens. Agora ficou bem melhor)). Eu já trabalho lá há um bom tempo e mesmo assim, falta tanto para acabar e daria muito jeito, se pudesse ter ajuda lá. Obrigado pela vossa atenção . Se quiserem ajudar, por favor, entrem por aqui https://translate.crowdin.com/project/react (podem entrar na vossa conta do google/github/facebook, etc e depois, irá voltar a essa página). Alguns dos exemplos de localização no Crowdin: NodeJs, Minecraft, GitLab, Hypixel, GommeHDNet (também server multiplayer de Minecraft ), CodeOrg (tutoriais de programação), Raspberry e muitos outros projetos para tradução/localização. Pequeno à parte: Eu também estou a traduzir o próprio site, ou seja, existe uma versão em português ainda não acabada (vai a 65%) e se quiserem ajudar de alguma forma https://pt.crowdin.com/project/react (fica em pt-pt com algumas coisas em inglês (ainda não foram traduzidas )) ou https://translate.crowdin.com/project/react (para ajudar na tradução do site (é uma espécie de tradução ao vivo, o que significa que podemos ver o que traduzimos enquanto escrevemos https://support.crowdin.com/in-context-localization/ )) (Se leram a diferença entre localização e tradução irão perceber) Se repararem eu próprio fiz uma espécie localização deste comentário de português para inglês (um pouco de propósito) Se me quiserem mandar uma mensagem lá https://crowdin.com/messages/create e põe Luis Trindade ou ldiogotrindade Inglês/English: (I will remove this comment if I abused in some way. I just wanted to ask for some help and to help, I'm really sorry) (I'm really sorry for being so long) Small apart: I'm as well translating the site itself, wich means that the site has a portuguese version (as much others) and still unfinished (is 65% done) and if want to help in some way can use https://pt.crowdin.com/project/react (will be in pt-pt with some english words (aren't yet translated)) or https://translate.crowdin.com/project/react (to help to translate (is like a live translation wich means that we can see what we translate while we write https://support.crowdin.com/in-context-localization/ )) ( if have read the site of the site about the difference in between in localization and translation will understand ) If you notice I made a kind of localization of this comment from Portuguese to English (a bit in purpose) If want to PM me there https://crowdin.com/messages/create and put in the search Luis Trindade or ldiogotrindade |
|
@luisdiogo2071317 Boas. Don't take me wrong. Mas já fazer a tradução desta documentação de react não está fácil, quanto mais fazer outras. |
|
@jbarradas é que lá e aqui a diferença é que lá tem um Editor muito bom, enquanto que aqui, temos que depender imenso dos outros. Se, fores ver alguns dos projetos, por exemplo, o do React e testares algumas traduções, vais entender rapidamente. Eu já estou lá desde outubro de 2018 e tenho trabalhado em imensos projetos e daria jeito se alguém que já está habituado ou que já fez a tradução duma x página, aqui pôr a mesma coisa lá. É que, quando é-se o único a fazer um projeto de mais de 300 mil palavras fica muito difícil. E pôs a última foi mais para, por exemplo, uma frase ou palavra está incorreta dizem-me e corrijo e pronto. É assim, que lá funciona. E naquele texto enorme eu só falei muito superficialmente o que tem lá. E eu também estou a tratar do Support e só irá ficar em pt-pt quando chegar por volta dos 30% e ainda vai nos 13 % |
|
We actually were originally doing the translations on Crowdin but decided to switch to GitHub because we felt that it didn't suit our needs. It seems that you are familiar with and prefer the Crowdin editor, but from talking to other developers, they tend to prefer GitHub because it's a system they're already familiar with. Pull requests and reviews are familiar to developers compared to whatever system Crowdin uses. There also doesn't seem to be any easy way to organize work on Crowdin, so there's no way to say which pages are the most important to be translated. In addition, we ran into a lot of quality issues with the Crowdin translations. While some languages had good maintainers, others were not as well maintained and were inconsistent and full of errors. In fact, I looked at some of the Crowdin translations for projects you mentioned and found the same issues there. By doing this on GitHub with dedicated maintainers of each language, we can ensure that the community is empowered to keep their translations up-to-date and consistent. Another reason we're using GitHub is that many developers are motivated in contributing directly to the React organization as contributors, and creating translations is one of the most accessible ways to do that. Developers are generally more excited to work on translations here than on Crowdin! In fact, within two months of starting this project we already have six completed translations! And while you mention a lot of projects using Crowdin, I would also like to mention that Angular and Vue, two other popular frameworks, use this approach as well. I definitely think Crowdin is useful for a lot of projects, but in our case, our community has coding experience and is more comfortable using GitHub. I hope that answers your questions, and I hope you will join us in translating the official React docs! |
|
@tesseralis To be truthy I didn't know that and btw I am a programmer so for being in here or in Crowdin is the same. But at the same time I prefer more Crowdin where I can see if what I am translating it corresponds what should be instead of just translating. Crowdin is a lot more interactive in a lot ways. It has what is called Crowdin In-Context wich is a kind of live translator where we can see what we translate while we write (just a demo of Crowdin In-Context https://demo.crowdin.com/) . And I think it's possible to use it in the React site. I know that because I'm a contributor of the Crowdin Support so I know a lot of things about Crowdin and I translate as well the Crowdin site itself.
|
|
@luisdiogo2071317 the project is shut down. If you want to discuss this further, may I ask that you join our Slack? |
|
@tesseralis I do want to help but I don't know much how to translate in here. By being proofreader of Crowdin site and a multiplayer server of Minecraft (GommeHDNet) I know well how to translate, but at the same time it may became confusing. I, basically, when I'm translating to English I translate in literal words as if I was going to speak into Portuguese |
|
@luisdiogo2071317 You are still welcome to help. All translations go through a review process. However, literal translation is not the way to go, we should adapt to how the language is written. |
|
@jbarradas When I speak and translate i do it in a way but when is really to translate I go for real |
|
Eu estou a tentar fazer push de algo que já traduzi e não consigo fazê-lo e diz sempre que não tenho permissão. |
|
Posso já fazer logo duma vez todos do faq? ( exceto aquele que já tem posse) |
|
@imflavio @flowck you both have claimed pages, but never submitted any PR. Should they remain claimed for you to translate or should we remove the claim? Thanks |
|
Remove mine please |
|
Hi guys, native speaker here! I can pick up whatever's next on priority list (State and Lifecycle maybe?) Thanks! |
|
Olá @antonio-rodrigues, bem-vindo! Sim, podes escolher Alguma referência para ajudar-te no processo de tradução: #9 |
|
@fjoshuajr podes marcar então |
|
@antonio-rodrigues done. Quando tiveres um PR avisa para actualizarmos na lista. |
|
Hey everyone, native speaker here. |
Go for it, we haven't been too active in the last few months though. Make sure you follow the rules / guidelines. Let's see if that changes this year. |
Thanks, will start working on it as soon as possible 😄 |
|
Boas pessoal finalizei a pagina da acessibilidade |
|
Code splitting ✔️ #52 |
|
It looks like this translation has stalled, and is now very outdated. |
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
And please join us in Slack (https://rt-slack-invite.herokuapp.com), we have dedicated channels for each translation team. You might seek help there, either with translation processes or suggestions of words/sentences you might have been struggling with.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
Basics
API Reference
Navigation
These are the navigation links that appear in the sidebar. Possibly wait until
the corresponding sections are translated to do these.
Next Steps
These are the next most important translations, ordered by importance:
Installation
Hooks
Everyone is hooked on hooks! People are really excited about these, and it would be great for them to be translated.
Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
Advanced Guides
FAQ
Contributing
Priority: Low
Components
Components in
src/componentsthat have some text in them.Additional Translations
These are not the primary translation targets.
The text was updated successfully, but these errors were encountered: