Overview

Project website pagure.io/fedora-docs-l10n/council
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/council.git
Repository branch master
Last remote commit automatic update of pot/po files bafcb739a
♪ I'm a bot, bot, bot ♪ authored 8 hours ago
Last commit in Weblate Update translation files 8034c7c4d
Weblate authored 8 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-council/nav/
File mask po/*/master/pages/procedures/survey/how-to.po
Translation file Download po/pt_BR/master/pages/procedures/survey/how-to.po
Last change Oct. 20, 2023, 10:14 p.m.
Last change made by Anonymous
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 54 707 5,413
Translated 1% 1 1% 8 1% 48
Needs editing 66% 36 77% 550 82% 4,472
Read-only 0% 0 0% 0 0% 0
Failing checks 24% 13 22% 156 22% 1,235
Strings with suggestions 29% 16 61% 437 52% 2,828
Untranslated strings 31% 17 21% 149 16% 893
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 40 changes 0 changes 0 changes 0 changes 89 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

707
Hosted words
54
Hosted strings
1%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+1%
—
Contributors
—
User avatar anonymous

Suggestion added
For increased visibility we also promote the survey on IRC and Twitter. This should be done sparingly as their is a potential for it to feel spammy. It could potentially go to other social media platforms but the main audience for that platform should be contributors not users. Don't forget to remind people they can earn a badge!
Para aumentar a visibilidade, também promovemos a pesquisa no IRC e no Twitter. Isso deve ser feito com moderação, pois há o risco de parecer spam. Também pode ser feita em outras plataformas de mídia social, mas o público principal dessas plataformas deve ser os colaboradores, não os usuários. Não se esqueça de lembrar as pessoas de que elas podem ganhar um distintivo!
a year ago
User avatar anonymous

Suggestion added
A lot of folks are on multiple mailing lists so it is important to choose high level "announce" channels over team channels. A short email should be sent with a link to the Community Blog post as well as a link directly to the survey.
Muitas pessoas estão em várias listas de e-mail, por isso é importante escolher canais de "anúncio" de alto nível em vez de canais de equipe. Deve ser enviado um e-mail curto com um link para o artigo no Community Blog, bem como um link diretamente para a pesquisa.
a year ago
User avatar anonymous

Suggestion added
Mailing Lists
Listas de E-mails
a year ago
User avatar anonymous

Suggestion added
The first step is to open a ticket on the https://pagure.io/design/issues[Design Team pagure] to get any updates on artwork. *This ticket should be opened by April 1st, and closed by May 1st.* If there are no changes from the Design Team, proceed with the previous design. Once the artwork is finalized, a ticket is opened on the https://pagure.io/fedora-websites/issues[Websites & Apps Team] repo to get it published. *This ticket should be opened by May 1st* and needs continuous check-ins. The websites that we aim to cover are:
O primeiro passo é abrir um ticket no https://pagure.io/design/issues[repositório do Design Team] para obter quaisquer atualizações sobre a arte. **Este ticket deve ser aberto até 1º de abril e encerrado até 1º de maio.** Se não houver mudanças da equipe de design, continue com o design anterior. Depois que a arte estiver finalizada, abra um ticket no https://pagure.io/fedora-websites/issues[repositório Websites & Apps Team] para publicá-la. **Este ticket deve ser aberto até 1º de maio** e requer verificações contínuas. Os websites que pretendemos abranger são:
a year ago
User avatar anonymous

Suggestion added
Each year we need to write at least two blog posts for the survey. The first one is to promote taking the survey, the second features the released dataset and any findings. These are published on the link:{COMMBLOG}[CommBlog], make sure to follow link:{COMMBLOG}/writing-community-blog-article/[the guidelines]. The promotional blog post should then be pinned on Discussion.fpo for the month the survey is open.
Todos os anos precisamos escrever pelo menos dois posts no blog para a pesquisa. O primeiro é para promover a participação na pesquisa, o segundo apresenta o conjunto de dados liberados e quaisquer descobertas. Esses posts são publicados no https://communityblog.fedoraproject.org/[CommBlog], certifique-se de seguir https://communityblog.fedoraproject.org/writing-community-blog-article/[as diretrizes]. O post promocional do blog deve ser fixado na Discussão.fpo durante o mês em que a pesquisa está aberta.
a year ago
User avatar anonymous

Suggestion added
Each year we generate a https://badges.fedoraproject.org/[Fedora Badge] that survey recipients can claim when they submit their survey responses. A ticket needs to be opened on the https://pagure.io/fedora-badges/issues[Badges repo] requesting the badge. The panda graphic stays the same, and the year is updated accordingly. *This ticket should be opened by April 1st* in order to give the Badges team enough time to generate the artwork, push the badge to the website, and provide a claim link to the Survey team.
Todo ano geramos um https://badges.fedoraproject.org/[Distintivo Fedora] que os destinatários da pesquisa podem reivindicar ao enviar suas respostas à pesquisa. Um ticket precisa ser aberto no https://pagure.io/fedora-badges/issues[repositório Badges] solicitando o distintivo. O gráfico do panda permanece o mesmo, e o ano é atualizado de acordo. **Este ticket deve ser aberto até 1º de abril** para dar tempo suficiente à equipe de Badges para gerar a arte, disponibilizar o distintivo no site e fornecer um link de reivindicação à equipe da Pesquisa.
a year ago
User avatar anonymous

Suggestion added
Fedora Badges
#### Fedora Badges
a year ago
User avatar anonymous

Suggestion added
**July 1st-31st**:
First round of survey analysis
**1º de julho a 31 de julho** Primeira rodada de análise da pesquisa
a year ago
User avatar anonymous

Suggestion added
**June 30th**:
One day reminder to fill out survey on IRC and Twitter
**30 de junho** Lembrete de um dia para preencher a pesquisa no IRC e no Twitter
a year ago
User avatar anonymous

Suggestion added
**June 15th**:
Two week reminder to fill out survey on IRC and Twitter
**15 de junho** Lembrete de duas semanas para preencher a pesquisa no IRC e no Twitter
a year ago
Browse all translation changes