-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[pt] Update README.pt.md #3166
[pt] Update README.pt.md #3166
Conversation
I was discussing this on Mastodon and after reading a bit on the i18n issue, I have some feedback:
The way I see it, it looks like if you mixed both EDIT: I was reading the previous issue and I agree with the author of the previous PR that translated the README to portuguese that a portuguese should review the PR as well, to provide feedback on it. Both me and the PR author are from Brazil, which makes it a bit harder to provide "neutral" text for lusophones in general. |
Signed-off-by: Matheus Horstmann <[email protected]>
We (the other author and me) tried to make as neutral as possible, I agree with you that it should be reviewed by portuguese speakers around the world, not just from Portugal and Brazil. I fixed grammars errors and also agreed that |
Having lived in Brazil and Portugal, I think I qualify as a speaker of both
Thanks for putting the work in the translation, and let me know if there's anything I can do to help. Cheers! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Some minor nits
|
||
## Ajuda em português | ||
|
||
No momento, o suporte em português no canal do IRC **não está ativo**. Em caso de problemas, | ||
use as [*issues*](https://github.com/swaywm/sway/issues/) do Github (*em inglês*). | ||
No momento, o suporte em português no canal no IRC **não está ativo**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the second no
is redundant, canal IRC
should suffice,
|
||
## Assinaturas dos *Releases* | ||
## Assinaturas dos lançamentos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think lançamentos
is usual terminology. If anything I'd stick with the anglicized Releases
.
[B22DA89A](http://pgp.mit.edu/pks/lookup?op=vindex&search=0x52CB6609B22DA89A) | ||
e publicadas [no GitHub](https://github.com/swaywm/sway/releases). | ||
Cada versão é assinada com a chave [B22DA89A][sway pgp] e publicada | ||
[no Github][sway releases]. | ||
|
||
## Instalação | ||
|
||
### A partir de pacotes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Por
is better than A partir de
for this and subsequent subsections.
|
||
Se você está interessado em manter um pacote do Sway para a sua distribuição, | ||
visite o canal no IRC ou mande um email para [email protected] (*em inglês*). | ||
Se estiveres interessado em manter um pacote em sua distribuição, visite o |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
você estiver
Se você está interessado em manter um pacote do Sway para a sua distribuição, | ||
visite o canal no IRC ou mande um email para [email protected] (*em inglês*). | ||
Se estiveres interessado em manter um pacote em sua distribuição, visite o | ||
canal no IRC ou mande um e-mail para <[email protected]> (*em inglês*). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a link to the IRC channel.
o Sway lerá o arquivo normalmente. Senão, copie o arquivo de configuração de exemplo | ||
para `~/.config/sway/config`. É comum esse arquivo estar localizado em | ||
`/etc/sway/config`. Veja `man 5 sway` para informações sobre configuração. | ||
Se já usas i3, copie teu arquivo de configuração para `~/.config/sway/config` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Se você já usa i3, copie sua configuração para ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think configuração
already strongly implies that it's an arquivo
so it becomes redundant.
para `~/.config/sway/config`. É comum esse arquivo estar localizado em | ||
`/etc/sway/config`. Veja `man 5 sway` para informações sobre configuração. | ||
Se já usas i3, copie teu arquivo de configuração para `~/.config/sway/config` | ||
e Sway lerá o arquivo normalmente. Senão, copie o arquivo de configuração |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think usará
is better than lerá
here.
para `~/.config/sway/config`. É comum esse arquivo estar localizado em | ||
`/etc/sway/config`. Veja `man 5 sway` para informações sobre configuração. | ||
Se já usas i3, copie teu arquivo de configuração para `~/.config/sway/config` | ||
e Sway lerá o arquivo normalmente. Senão, copie o arquivo de configuração |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the correct form is Se não
, no?
`/etc/sway/config`. Veja `man 5 sway` para informações sobre configuração. | ||
Se já usas i3, copie teu arquivo de configuração para `~/.config/sway/config` | ||
e Sway lerá o arquivo normalmente. Senão, copie o arquivo de configuração | ||
de exemplo para `~/.config/sway/config`. É comum esse arquivo estar localizado |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
arquivo de configuração exemplo
, the de
seems unnecessary.
relatos, o gdm funciona bem com o Sway). | ||
|
||
Execute `sway` a partir do console. Alguns gerenciadores de *display* podem | ||
funcionar, porém não são oficialmente suportados (segundo relatos, gdm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe link to gdm.
Just an addendum after having review the file, this is through and through a Brazilian Portuguese doc, if someone wishes to add a Portugal Portuguese README it should have some changes. |
As I said in Mastodon European Portuguese is understandable by Brazilians, and vice-versa. And translate for both at same time could sound strange. |
Yes, that's what I said, translating to both at the same time would sound strange.
Sure, this is mostly true with some minor exceptions. This doesn't, however, negate the fact that the dialects are different enough that it can feel uncomfortable for a native speaker of one to read a document in the other, specially a technical one. I think we are fine with just a Brazilian Portuguese document, at least until until someone steps up to support an European Portuguese one, and then we could maybe just have both, not that the differences matter too much. |
If the agreement is to translate it to Brazilian Portuguese, I think the
file should be renamed to suit it better.
…On Tue, 27 Nov 2018, 09:13 Bernardo Meurer ***@***.*** wrote:
translate for both at same time could sound strange.
Yes, that's what I said, translating to both at the same time would sound
strange.
European Portuguese is understandable by Brazilians, and vice-versa.
Sure, this is mostly true with some minor exceptions. This doesn't,
however, negate the fact that the dialects are different enough that it can
feel uncomfortable for a native speaker of one to read a document in the
other, specially a technical one.
I think we are fine with just a Brazilian Portuguese document, at least
until until someone steps up to support an European Portuguese one, and
then we could maybe just have both, not that the differences matter too
much.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3166 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABMW-6k2UWNxYghg7W4PLM2ki1nB512Xks5uzR5YgaJpZM4YtATC>
.
|
There's another attempt here: #4931 |
Update #1318
Signed-off-by: Matheus Horstmann [email protected]