Language Translated Untranslated Untranslated words Untranslated characters Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0 0 0 2 0 0
Chinese (Simplified) (zh_CN) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 2% 77 2,795 17,766 1 0 0
Chinese (Traditional) (zh_TW) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 79 2,797 17,777 0 0 0
Dutch (nl_NL) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 79 2,797 17,777 1 0 0
French (fr_FR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 79 2,797 17,777 0 0 0
German (de_DE) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 78 2,796 17,769 0 0 0
Italian (it_IT) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 10% 71 2,727 17,329 0 0 0
Norwegian Bokmål This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 79 2,797 17,777 0 0 0
Persian This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 2% 77 2,795 17,766 0 0 0
Portuguese (Brazil) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0 0 0 0 4 0
Spanish This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 45% 43 2,152 13,873 16 0 0
Turkish (tr_TR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 79 2,797 17,777 0 0 0
Please sign in to see the alerts.

Overview

Project website docs.freebsd.org/en
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
Translation license BSD 2-Clause "Simplified" License
Filemask documentation/content/*/articles/explaining-bsd/_index.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 948 33,564 213,324
Source 79 2,797 17,777
Translated 21% 207 18% 6,314 18% 39,936
Needs editing 1% 15 2% 846 2% 5,373
Failing checks 2% 20 2% 885 2% 5,601
Strings with suggestions 1% 4 1% 229 1% 1,290
Not translated strings 76% 726 78% 26,404 78% 168,015
Last year Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 111 changes 0 changes 135 changes 0 changes 55 changes 0 changes 66 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

33,564
Hosted words
948
Hosted strings
21%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+1%
—
Hosted strings
+1%
—
Translated
—
—
Contributors
-50%
User avatar None

Automatic translation

Documentation / articles/explaining-bsd/_index — Spanish

It is at the individual committer's discretion whether they should obtain authority before committing changes to the source tree. In general, an experienced committer may make changes which are obviously correct without obtaining consensus. For example, a documentation project committer may correct typographical or grammatical errors without review. On the other hand, developers making far-reaching or complicated changes are expected to submit their changes for review before committing them In extreme cases, a core team member with a function such as Principal Architect may order that changes be removed from the tree, a process known as _backing out_. All committers receive mail describing each individual commit, so it is not possible to commit secretly.
Depende del criterio individual de cada committer cuándo pedir autorización antes de hacer cambios en el árbol de fuentes. En general, un committer experimentado puede realizar cambios que obviamente son correctos sin obtener consenso. Por ejemplo, un committer que trabaje en un proyecto de documentación puede corregir errores tipográficos o gramaticales sin necesidad de revisión. Por otra parte, se espera que los desarrolladores que pretendan realizar cambios de gran calado o complicados envíen sus cambios para que sean revisados antes de ser incluidos. En casos extremos un miembro del core team con una función como la del Principal Architect puede ordenar que los cambios sean retirados del árbol, es lo que llamamos <firstterm>backing out</firstterm>. Todos los committers reciben un correo electrónico que describe cada commit, por lo que no es posible hacer un commit en secreto.
a month ago
User avatar None

New contributor

Documentation / articles/explaining-bsd/_index — Spanish

New contributor a month ago
User avatar dbaio

Translation changed

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

It is at the individual committer's discretion whether they should obtain authority before committing changes to the source tree. In general, an experienced committer may make changes which are obviously correct without obtaining consensus. For example, a documentation project committer may correct typographical or grammatical errors without review. On the other hand, developers making far-reaching or complicated changes are expected to submit their changes for review before committing them In extreme cases, a core team member with a function such as Principal Architect may order that changes be removed from the tree, a process known as _backing out_. All committers receive mail describing each individual commit, so it is not possible to commit secretly.
Fica a critério do bom senso individual de cada committer a decisão se eles devem obter ou não um consenso antes de enviar alterações para o repositório de código fonte. Em geral, um committer experiente pode fazer alterações que sejam inquestionavelmente corretas sem obter consenso. Por exemplo, um committer do projeto de documentação pode corrigir erros tipográficos ou gramaticais sem revisão. Por outro lado, espera-se que os desenvolvedores que realizam mudanças complexas ou muito extensas enviem suas alterações para revisão antes de enviá-las para o repositório de código fonte. Em casos extremos, um membro do Core Team com uma função tal como a de arquiteto principal, pode ordenar que as alterações sejam removidas do repositório, num processo conhecido como <firstterm>backing out</firstterm>_backing out_. Todos os committers recebem emails que descrevem cada commit individual, portanto não é possível enviar alterações para o repositório de código fonte em segredo.
a month ago
User avatar dbaio

Translation changed

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

One detail that the lawsuit did clarify is the naming: in the 1980s, BSD was known as "BSD UNIX(R)". With the elimination of the last vestige of AT&T code from BSD, it also lost the right to the name UNIX(R). Thus you will see references in book titles to "the 4.3BSD UNIX(R) operating system" and "the 4.4BSD operating system".
Um detalhe que o processo civil não deixa claro refere-se ao nome: nos anos 80 o BSD era conhecido como "BSD UNIX(R)". Com a eliminação dos últimos vestígios do código da AT&T do BSD, ele também perdeu o direito ao nome UNIX(R). Desta forma você verá referências em livros para o "sistema operacional 4.3BSD UNIX(R)" e o "sistema operacional 4.4BSD".
a month ago
User avatar dbaio

Translation changed

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

The X Window system used in most versions of BSD is maintained by the http://www.X.org/[X.Org project]. FreeBSD allows the user to choose from a variety of desktop environments, such as Gnome, KDE, or Xfce; and lightweight window managers like Openbox, Fluxbox, or Awesome.
O sistema X Window usado na maioria das versões do BSD é mantido pelo http://www.X.org/[Projeto X.Org]. O FreeBSD permite ao usuário escolher a partir de uma variedade de ambientes de desktop, tais como o Gnome, KDE ou Xfce; e gerenciadores gráficos (gerenciadores de janelas) mais leves, como Openbox, Fluxbox ou Awesome.
a month ago
User avatar dbaio

Translation changed

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

__Some of the utilities are derived from the GNU project, others are not.__
__Alguns utilitários são derivados do projeto GNU, outros não são.__
a month ago
User avatar dbaio

Translation changed

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

__The BSD C library is based on code from Berkeley, not the GNU project.__
__A biblioteca C do BSD é baseada no código de Berkeley, não no projeto GNU.__
a month ago
User avatar dbaio

New translation

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

Brief explanation about BSD
Breve explicação sobre BSD
a month ago
User avatar None

Automatic translation

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

It is at the individual committer's discretion whether they should obtain authority before committing changes to the source tree. In general, an experienced committer may make changes which are obviously correct without obtaining consensus. For example, a documentation project committer may correct typographical or grammatical errors without review. On the other hand, developers making far-reaching or complicated changes are expected to submit their changes for review before committing them In extreme cases, a core team member with a function such as Principal Architect may order that changes be removed from the tree, a process known as _backing out_. All committers receive mail describing each individual commit, so it is not possible to commit secretly.
Fica a critério do bom senso individual de cada committer a decisão se eles devem obter ou não um consenso antes de enviar alterações para o repositório de código fonte. Em geral, um committer experiente pode fazer alterações que sejam inquestionavelmente corretas sem obter consenso. Por exemplo, um committer do projeto de documentação pode corrigir erros tipográficos ou gramaticais sem revisão. Por outro lado, espera-se que os desenvolvedores que realizam mudanças complexas ou muito extensas enviem suas alterações para revisão antes de enviá-las para o repositório de código fonte. Em casos extremos, um membro do Core Team com uma função tal como a de arquiteto principal, pode ordenar que as alterações sejam removidas do repositório, num processo conhecido como _backing out_<firstterm>backing out</firstterm>. Todos os committers recebem emails que descrevem cada commit individual, portanto não é possível enviar alterações para o repositório de código fonte em segredo.
a month ago
User avatar None

New contributor

Documentation / articles/explaining-bsd/_index — Portuguese (Brazil)

New contributor a month ago
Browse all component changes