Translation status

189 Strings 100%
Browse Translate
7,211 Words 100%
50,679 Characters 100%

Strings status

Strings Words Characters
189 7,211 50,679
All strings Browse Translate Zen
189 7,211 50,679
Translated strings Browse Translate Zen

Overview

Project website www.linuxfromscratch.org
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 git@git.linuxfromscratch.org:fr-lfs
Repository branch trunk
Last remote commit Automatic BLFS commit based on 05b84e9f32221ccda04825312c07f233c3cbf1b0 344ed3a163
Julien Lepiller authored 10 hours ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 892aeef097
User avatar jamenson authored 9 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/introduction/important/building-notes.po
Translation file Download blfs/pt_BR/introduction/important/building-notes.po
Last change Feb. 6, 2025, 4:19 p.m.
Last change made by None
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
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 189 7,211 50,679
Translated 100% 189 100% 7,211 100% 50,679
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
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 0 changes 0 changes 0 changes 247 changes 0 changes 85 changes 0 changes 1 change 0 changes 8 changes 0 changes 0 changes 0 changes 0 changes 0 changes 14 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

7,211
Hosted words
189
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “blfs/pt_BR/introduction/important/building-notes.po” file was changed. 2 weeks ago
User avatar None

String updated in the repository
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
No passado, existia o LFS Reforçado, onde o gcc (uma versão muito mais antiga) era forçado a usar o reforçamento (com opções para desativar parte dele na base do por pacote). Os livros atuais do LFS e BLFS estão levando adiante uma parte do espírito dele ao habilitar PIE (<option>-fPIE -pie</option>) e SSP (<option>-fstack-protector-strong</option>) como padrões para GCC e clang. E o lincador (<command>ld</command>) também habilitou <option>-Wl,-z,relro</option>, o que torna uma parte da Global Offset Table (GOT) imutável, por padrão desde Binutils 2.27. O que está sendo coberto aqui é diferente - primeiro você tem que ter certeza de que o pacote está realmente usando teus sinalizadores adicionados e não os substituindo.
2 weeks ago
User avatar None

String updated in the repository
Note that the <option>-j</option> switches only limits the parallel jobs started by <command>make</command> or <command>ninja</command>, but each job may still spawn its own processes or threads. For example, some tests of packages can spawn multiple threads for testing thread safety properties. There is no generic way for the building system to know the number of processes or threads spawned by a job. So generally we should not consider the value passed with <option>-j</option> a hard limit of the number of logical cores to use. Read <xref linkend='build-in-cgroup'/> if you want to set such a hard limit.
Observe que as chaves <option>-j</option> somente limitam as tarefas paralelas iniciadas por <command>make</command> ou <command>ninja</command>, mas cada tarefa possivelmente ainda gere os próprios processos ou camadas dela. Por exemplo, alguns testes de pacotes podem gerar várias camadas para testar propriedades de segurança de camadas. Não existe uma maneira genérica de o sistema de construção saber o número de processos ou camadas gerados por uma tarefa. Portanto, geralmente nós não deveríamos considerar o valor passado com <option>-j</option> como um limite rígido do número de núcleos lógicos a serem usados. Leia-se <xref linkend='build-in-cgroup'/> se você quiser configurar tal limite tão rígido.
2 weeks ago
User avatar None

Changes committed
Changes committed 2 weeks ago
User avatar jamenson

Translation completed
Translation completed 2 weeks ago
User avatar jamenson

Translation changed
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
No passado, existia o LFS Reforçado, onde o gcc (uma versão muito mais antiga) era forçado a usar o reforçamento (com opções para desativar parte dele na base do por pacote). Os livros atuais do LFS e BLFS estão levando adiante uma parte do espírito dele ao habilitar PIE (<option>-fPIE -pie</option>) e SSP (<option>-fstack-protector-strong</option>) como padrões para GCC e clang. E os lincadores (<command>ld.bfd</command> e <command>ld.gold</command>) também habilitaramou <option>-Wl,-z,relro</option>, o que torna uma parte da Global Offset Table (GOT) imutável, por padrão desde Binutils 2.27. O que está sendo abordadcoberto aqui é diferente - primeiro você tem que ter certeza de que o pacote está realmente usando teus sinalizadores adicionados e não os substituindo-os.
2 weeks ago
User avatar jamenson

Translation changed
Note that the <option>-j</option> switches only limits the parallel jobs started by <command>make</command> or <command>ninja</command>, but each job may still spawn its own processes or threads. For example, some tests of packages can spawn multiple threads for testing thread safety properties. There is no generic way for the building system to know the number of processes or threads spawned by a job. So generally we should not consider the value passed with <option>-j</option> a hard limit of the number of logical cores to use. Read <xref linkend='build-in-cgroup'/> if you want to set such a hard limit.
Observe que as chaves <option>-j</option> somente limitam as tarefas paralelas iniciadas por <command>make</command> ou <command>ninja</command>, mas cada tarefa possivelmente ainda pode gerare os próprios processos ou camadas dela. Por exemplo, <command>ld.gold</command> usará várias camadas para vinculação, e alguns testes de pacotes podem gerar várias camadas para testar propriedades de segurança de camadas. Não existe uma maneira genérica de o sistema de construção saber o número de processos ou camadas gerados por uma tarefa. Portanto, geralmente nós não deveríamos considerar o valor passado com <option>-j</option> como um limite rígido do número de núcleos lógicos a serem usados. Leia-se <xref linkend='build-in-cgroup'/> se você quiser configurar tal limite tão rígido.
2 weeks ago
User avatar None

Resource updated
The “blfs/pt_BR/introduction/important/building-notes.po” file was changed. 2 weeks ago
User avatar None

String added in the repository
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
No passado, existia o LFS Reforçado, onde o gcc (uma versão muito mais antiga) era forçado a usar o reforçamento (com opções para desativar parte dele na base do por pacote). Os livros atuais do LFS e BLFS estão levando adiante uma parte do espírito dele ao habilitar PIE (<option>-fPIE -pie</option>) e SSP (<option>-fstack-protector-strong</option>) como padrões para GCC e clang. E os lincadores (<command>ld.bfd</command> e <command>ld.gold</command>) também habilitaram <option>-Wl,-z,relro</option>, o que torna uma parte da Global Offset Table (GOT) imutável, por padrão desde Binutils 2.27. O que está sendo abordado aqui é diferente - primeiro você tem que ter certeza de que o pacote está realmente usando teus sinalizadores adicionados e não os substituindo-os.
2 weeks ago
User avatar None

Source string changed
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linkers (<command>ld.bfd</command> and <command>ld.gold</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
2 weeks ago
Browse all translation changes