SUSE has an in-house translations created by contracted translators in past. The work flow did not allow to merge translations between openSUSE and SLE trees up to now. It caused translation divergence. SLE Merge Robot is an output of the merge effort, and “suggests” to use SLE translation. Please review carefully, and keep standard terminology used in your language.

Initial import of yast was created from the community translations, but strings actually missing in the community translation were taken from the contracted SUSE Linux Enterprise translations. These translations are mixed in Weblate. If you are interested in the SUSE Linux Enterprise translations import review, go to <ftp://ftp.suse.com/pub/people/sbrabec/yast-translations-sle-contributions/>

Translation status

156 Strings 100%
Browse Translate
1,878 Words 100%
12,406 Characters 100%

Strings status

Strings Words Characters
156 1,878 12,406
All strings Browse Translate Zen
12 494 3,381
Approved strings Browse Translate Zen
156 1,878 12,406
Translated strings Browse Translate Zen
144 1,384 9,025
Strings waiting for review Browse Translate Zen

Overview

Project website github.com/yast/yast-bootloader
Project maintainers User avatar ancorgonzalezsosa
Translation license GNU General Public License v2.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:yast/yast-translations.git
Repository branch master
Last remote commit New POT for text domain 'kdump'. a50702c72a
YaST Jenkins authored a month ago
Last commit in Weblate Translated using Weblate (Swedish) 42718c8ecf
User avatar LunaJernbergc15bd25a134943af authored a month ago
Weblate repository https://l10n.opensuse.org/git/yast-base/master/
File mask po/bootloader/*.po
Translation file Download po/bootloader/pt_BR.po
Last change May 4, 2024, 2:32 a.m.
Last author None
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 156 1,878 12,406
Approved 7% 12 26% 494 27% 3,381
Waiting for review 92% 144 73% 1,384 72% 9,025
Translated 100% 156 100% 1,878 100% 12,406
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 3 changes 0 changes 3 changes 5 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 15 changes 1 change 2 changes 0 changes 6 changes 0 changes 0 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

1,878
Hosted words
156
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
The “/var/lib/weblate/vcs/yast-base/master/po/bootloader/pt_BR.po” file was changed. 2 months ago
User avatar samantamagalhaes

Translation approved

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
<p><b>Protect Boot Loader with Password</b>
at boot time, modifying or even booting any entry will require the password. If <b>Protect Entry Modification Only</b> is checked then booting any entry is not restricted but modifying entries requires the password (which is the way GRUB 1 behaved). As side-effect of this option, rd.shell=0 is added to kernel parameters, to prevent an unauthorized access to the initrd shell. YaST will only accept the password if you repeat it in <b>Retype Password</b>. The password applies to the GRUB2 user 'root' which is distinct from the Linux 'root'. YaST currently does not support other GRUB2 users. If you need them, use a separate GRUB2 script.</p>
<p><b>Proteger o carregador de boot com senha</b>
no momento do boot, modificando ou até mesmo fazendo o boot de qualquer entrada exigirá a senha. Se <b>Proteger somente a modificação de entrada</b> estiver marcado, o boot de qualquer entrada não será restrita, mas a modificação de entradas exigirá a senha (que é o modo como o GRUB 1 se comporta). Como efeito colateral desta opção, rd.shell = 0 é adicionado aos parâmetros do kernel, para evitar um acesso não autorizado ao shell initrd. O YaST aceitará a senha somente se você a repetir em <b> Redigitar senha </b>. A senha se aplica ao usuário do GRUB2 '"root'", que é diferente do '"root'" do Linux. O YaST atualmente não suporta outros usuários do GRUB2. Se você precisar deles, use um script separado do GRUB2.</p>
2 months ago
User avatar samantamagalhaes

Translation approved

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
<p><b>CPU Mitigations</b><br>
The option selects which default settings should be used for CPU
side channels mitigations. A highlevel description is on our Technical Information
Document TID 7023836. Following options are available:<ul>
<li><b>Auto</b>: This option enables all the mitigations needed for your CPU model.
This setting can impact performance to some degree, depending on CPU model and
workload. It provides all security mitigations, but it does not protect against
cross-CPU thread attacks.</li>
<li><b>Auto + No SMT</b>: This option enables all the above mitigations in
"Auto", and also disables Simultaneous Multithreading to avoid
side channel attacks across multiple CPU threads. This setting can
further impact performance, depending on your
workload. This setting provides the full set of available security mitigations.</li>
<li><b>Off</b>: All CPU Mitigations are disabled. This setting has no performance
impact, but side channel attacks against your CPU are possible, depending on CPU
model.</li>
<li><b>Manual</b>: This setting does not specify a mitigation level and leaves
this to be the kernel default. The administrator can add other mitigations options
in the <i>kernel command line</i> widget.
All CPU mitigation specific options can be set manually.</li></ul></p>
<p><b>Mitigações da CPU</b><br>
A opção seleciona quais configurações padrão devem ser usadas para CPU
mitigações de canais laterais. Uma descrição de alto nível está em nossas Informações Técnicas
Documento TID 7023836. As seguintes opções estão disponíveis: <ul>
<li><b>Automático</b>: essa opção ativa todas as mitigações necessárias ao seu modelo de CPU.
Essa configuração pode afetar o desempenho em algum grau, dependendo do modelo da CPU e
da carga de trabalho. Ele fornece todas as mitigações de segurança, mas não protege contra
ataques de threads da CPU cruzadas.</li>
<li><b>Automático + Sem SMT</b>: estsa opção ativa todas as mitigações acima em
"Auto"
 e também desativa o multithreading simultâneo (SMT) para evitar
ataques de canal lateral em várias
 threads da CPU. Essa configuração pode
afetar ainda mais o desempenho, dependendo da sua
carga de trabalho. Essa configuração fornece o conjunto completo de mitigações de segurança disponíveis.</li>
<li><b>Desligado</b>: todas as mitigações da CPU são desativadas. Esta configuração não afeta o
desempenho, mas os ataques do canal lateral contra a sua CPU são possíveis, dependendo do modelo
da CPU.</li>
<li><b>Manual</b>: estsa configuração não especifica um nível de mitigação e o deixa como o padrão
do kernel. O administrador pode adicionar outras opções de mitigação
no widget da <i>linha de comando do
 kernel</i>. .
Todas as opções específicas de mitigação da CPU podem ser definidas manualmente.</li></ul></p>
2 months ago
User avatar samantamagalhaes

Translation approved

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
Secure boot IPL has the following minimum system requirements,
depending on the boot device to be IPLed:
NVMe disk: IBM LinuxONE III or newer.
FC-attached SCSI disk: IBM LinuxONE III, IBM z15 or newer.
ECKD DASD with CDL layout: IBM z16, LinuxONE 4 or newer.
If these requirements are not met, the system can be IPLed in non-secure mode only.
A reinicialização (IPL) de boot seguro tem os seguintes requisitos mínimos de sistema,
dependendo do dispositivo de boot que será reinicializado (IPL):
Disco NVMe: IBM LinuxONE III ou mais recente.
Disco SCSI anexado a FC: IBM LinuxONE III, IBM z15 ou mais recente.
ECKD DASD com layout CDL: IBM z16, LinuxONE 4 ou mais recente.
Se esses requisitos não forem cumpridos, o sistema poderá ser reinicializado (IPL) somente no modo sem segurança.
2 months ago
User avatar samantamagalhaes

Translation approved

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
<p><b>Secure Boot Support</b> if checked enables Secure Boot support.<br>This does not turn on secure booting. It only switches to the new secure-boot enabled boot data format. Note that this new format works only on z15 or later and only for some disk types. For more details see the requirements at https://www.ibm.com/docs/en/linux-on-systems?topic=introduction-requirements</p>
<p><b>Suporte a boot seguro</b>: se marcado, o suporte ao boot seguro é habilitado.<br>Istso não ativa o boot seguro. Ele muda ape, apenas alternas para o novo formato de dados de boot habilitado para boot seguro. Observe que esse novo formato funciona apenas no z15 ou posterior e apenas para discos zFCP. O sistema não fará boot se esses requisitos não forem atendidos.somente para alguns tipos de disco. Para obter mais detalhes, consulte os requisitos em https://www.ibm.com/docs/en/linux-on-systems?topic=introduction-requirements</p>
2 months ago
User avatar None

Resource updated

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
The “/var/lib/weblate/vcs/yast-base/master/po/bootloader/pt_BR.po” file was changed. 2 months ago
User avatar None

Resource updated

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
The “/var/lib/weblate/vcs/yast-base/master/po/bootloader/pt_BR.po” file was changed. 3 months ago
User avatar None

Resource updated

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
The “/var/lib/weblate/vcs/yast-base/master/po/bootloader/pt_BR.po” file was changed. 4 months ago
User avatar None

Source string changed

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
<p><b>Secure Boot Support</b> if checked enables Secure Boot support.<br>This does not turn on secure booting. It only switches to the new secure-boot enabled boot data format. Note that this new format works only on z15 or later and only for zFCPsome disks. The system does not boot if types. For more details see these requirements are not met.t https://www.ibm.com/docs/en/linux-on-systems?topic=introduction-requirements</p>
4 months ago
User avatar samantamagalhaes

Translation approved

  1. yast-bootloader
  2. master
  3. Portuguese (Brazil)
Automatically boot the default entry after a timeout
Inicializar automaticamente a entrada padrão após o tempo limitede espera
4 months ago
Browse all translation changes