fedora-docs-l10n-commops/master/pages/community-blog — Portuguese (Brazil) @ Fedora Weblate: |Name |FAS account |Ben Cotton (_editor-in-chief_) |{url_wiki}/User:Bcotton[bcotton] |Jona Azizaj |{url

Zen

Translation

Source change

|Name |FAS account ~~|IRC nickname~~

|Ben Cotton (_editor-in-chief_)
|{~~FWIKI~~url_wiki}/User:Bcotton[bcotton]
|bcotton

|Brian Exelbierd
|{FWIKI}/User:Bex[bex]
|bexelbie

|Brian Proffitt
|{FWIKI}/User:Bproffit[bproffit]
|bkp

|Jona Azizaj
|{~~FWIKI~~url_wiki}/User:Jonatoni[jonatoni]
~~|jonatoni~~

|Matthew Miller
|{~~FWIKI~~url_wiki}/User:Mattdm[mattdm]
~~|mattdm~~

|Nick Bebout
|{~~FWIKI~~url_wiki}/User:Nb[nb]
~~|nb~~

|Sumantro Mukherjee
|{~~FWIKI~~url_wiki}/User:Sumantrom[sumantrom]
~~|sumantrom~~

English type: Table

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Fedora Magazine vs. Community Blog	Fedora Magazine vs. Community Blog
	What is the difference between the https://fedoramagazine.org[Fedora Magazine] and the Community Blog? They focus on two different audiences (or types of readers).	Qual é a diferença entre https://fedoramagazine.org[Fedora Magazine] e o Community Blog? Eles se concentram em dois públicos (ou tipos de leitores) diferentes.
	The Fedora Magazine targets everyday Fedora users, Linux enthusiasts, and technology hobbyists. Fedora contributors are included in these audiences, but they are not the main focus. The Community Blog is the news hub for Fedora contributors and people working inside of the Fedora community. The Community Blog specifically focuses on our contributors.	A Fedora Magazine é voltada para usuários comuns do Fedora, entusiastas do Linux e entusiastas de tecnologia. Os colaboradores do Fedora estão incluídos nestes públicos, mas não são o foco principal. O Community Blog é o centro de notícias para contribuidores do Fedora e pessoas que trabalham dentro da comunidade Fedora. O Community Blog concentra-se especificamente em nossos colaboradores.
	For example, an article on how to use a new package in Fedora is better for the Magazine. Any Fedora user may be interested in using the package. An article that announces a new feature to a Fedora Infrastructure service or an Ambassador event report is better for the Community Blog. A Fedora user may not be interested, but our contributors have a stronger interest.	Por exemplo, um artigo sobre como usar um novo pacote no Fedora é melhor para a Revista. Qualquer usuário do Fedora pode estar interessado em usar o pacote. Um artigo que anuncia um novo recurso para um serviço de Infraestrutura do Fedora ou um relatório de evento do Ambassador é melhor para o Community Blog. Um usuário do Fedora pode não estar interessado, mas nossos colaboradores têm um interesse maior.
	Sometimes there is some overlap between the two. Think hard about who you are writing for and who you want to read your article. This should answer the question of where to write your article. The CommOps and Fedora Magazine teams are happy to answer any doubts or questions if you are unsure.	Às vezes há alguma sobreposição entre os dois. Pense bem sobre para quem você está escrevendo e para quem deseja que leia seu artigo. Isso deve responder à questão de onde escrever seu artigo. As Equipes da CommOps e do Fedora Magazine terão prazer em responder a quaisquer dúvidas ou perguntas caso você não tenha certeza.
	Write an article	Escreva um artigo
	The Community Blog is managed by the CommOps team. The system administration is managed by {url_wiki}/Infrastructure[Fedora Infrastructure]. However, we need _your help_ to share the awesome things you and your area of Fedora are working on.	O Community Blog é gerenciado pela equipe de CommOps. A administração do sistema é gerenciada pela {FWIKI}/Infrastructure[Infraestrutura do Fedora]. Entretanto, precisamos da _sua ajuda_ para compartilhar as coisas incríveis nas quais você e sua área do Fedora estão trabalhando.
	Articles don't need to be long. Short snippets are useful too. If you're not sure how much to write, 300 words is a good target. If needed, you can always write more.	Os artigos não precisam ser longos. Trechos curtos também são úteis. Se você não tem certeza de quanto escrever, 300 palavras são um bom alvo. Se necessário, você sempre pode escrever mais.
	See the link:{url_commblog}/writing-community-blog-article/[_Writing an article_] guide to get started. This page explains the process for writing and how to get your post published.	Consulte o guia {COMMBLOG}/writing-community-blog-article/[Escrevendo um artigo] para começar. Esta página explica o processo de redação e como publicar sua postagem.
	Community Blog theme	Tema do Community Blog
	The Community Blog WordPress theme is open source. Find the source code https://pagure.io/communityblog-theme[on Pagure]. Open a ticket if you find a bug, problem, or something to improve. Pull requests are also welcome! Before submitting a pull request, post to {team_asynch_communication}[{team_asynch_communication_name}] first and ask for feedback on your planned contribution.	O tema de WordPress do Community Blog é de código aberto. Encontre o código-fonte https://pagure.io/communityblog-theme[no Pagure]. Abra um ticket se encontrar um bug, problema ou algo para melhorar. Pull requests também são bem-vindas! Antes de enviar uma pull request, poste primeiro no {DISCOURSE}[fórum Discourse do CommOps] e peça feedback sobre sua contribuição planejada.
	Editors	Editores
	Community Blog editors review article drafts and schedule new posts. Editors are reachable on {team_asynch_communication}[{team_asynch_communication_name}].	Os editores do Community Blog revisam rascunhos de artigos e agendam novas postagens. Os editores podem ser alcançados no {DISCOURSE}[fórum Discourse do CommOps]. O fórum Discourse é a melhor maneira de entrar em contato com um editor.
	Below, you can find a current list of editors:	Abaixo, você pode encontrar uma lista atual de editores:
	Community Blog editors	Editores do Community Blog
	\|Name \|FAS account \|Ben Cotton (_editor-in-chief_) \|{url_wiki}/User:Bcotton[bcotton] \|Jona Azizaj \|{url_wiki}/User:Jonatoni[jonatoni] \|Matthew Miller \|{url_wiki}/User:Mattdm[mattdm] \|Nick Bebout \|{url_wiki}/User:Nb[nb] \|Sumantro Mukherjee \|{url_wiki}/User:Sumantrom[sumantrom]	\|Nome \|Conta FAS \|apelido no IRC \|Ben Cotton (_editor-in-chief_) \|{FWIKI}/User:Bcotton[bcotton] \|bcotton \|Brian Exelbierd \|{FWIKI}/User:Bex[bex] \|bexelbie \|Brian Proffitt \|{FWIKI}/User:Bproffit[bproffit] \|bkp \|Jona Azizaj \|{FWIKI}/User:Jonatoni[jonatoni] \|jonatoni \|Matthew Miller \|{FWIKI}/User:Mattdm[mattdm] \|mattdm \|Nick Bebout \|{FWIKI}/User:Nb[nb] \|nb \|Sumantro Mukherjee \|{FWIKI}/User:Sumantrom[sumantrom] \|sumantrom

Loading…

None

String added in the repository

English

Portuguese (Brazil) 430 characters edited Current translation Needs editing

6 months ago

None

Source string changed

English 203 characters edited Needs editing

6 months ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Portuguese (Brazil)
No related strings found in the glossary.

18178096 String information

Source string description

type: Table

Flags

no-wrap

Source string location

pages/community-blog.adoc:97

String age

6 months ago

Last updated

6 months ago

Source string age

6 months ago

Translation file

po/pt_BR/master/pages/community-blog.po, string 27

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.