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 d6cda5163a2b191bd1f67b49f251a5eb1157701a a7505c5cf4
Julien Lepiller authored 21 minutes ago
Last commit in Weblate Automatic BLFS commit based on d6cda5163a2b191bd1f67b49f251a5eb1157701a a7505c5cf4
Julien Lepiller authored 21 minutes ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/postlfs/config/firmware.po
Translation file Download blfs/fr/postlfs/config/firmware.po
Last change Nov. 4, 2024, 4:20 p.m.
Last author None
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 101 3,533 25,040
Translated 100% 101 100% 3,533 100% 25,040
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 4% 5 7% 254 7% 1,934
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 17 changes 0 changes 12 changes 0 changes 5 changes 0 changes 10 changes 99 changes 14 changes 9 changes 0 changes 7 changes 5 changes 10 changes 3 changes 10 changes 7 changes 67 changes 28 changes 121 changes 6 changes 0 changes 7 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

3,533
Hosted words
101
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “blfs/fr/postlfs/config/firmware.po” file was changed. 4 days ago
User avatar None

String updated in the repository
In some rare cases a microcode update from the kernel can be ineffective. For example, despite intel-microcode-20241029 contains the Raptor Lake microcode revision 0x12b which is intended to fix a notorious excessive voltage issue causing stability issues and even permanent CPU damages, when the kernel boots it's already <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>too late</ulink> for the microcode to fix the issue. The only way to fix this issue is updating the BIOS.
Dans de rares cas la mise à jour du micrologiciel à partir du noyau peut ne pas fonctionner. Par exemple, bien que intel-microcode-20241029 contienne le micrologiciel de Raptor Lake révision 0x12b qui doit corriger un problème de voltage excessif notoire qui cause des problèmes de stabilité et endommage même le CPU de manière permanente, lorsque le noyau démarre il est déjà <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>trop tard</ulink> pour que le micrologiciel puisse corriger le problème. Le seul moyen de corriger le problème est de mettre à jour le BIOS.
4 days ago
User avatar None

Changes committed
Changes committed 4 days ago
User avatar admin

Translation completed
Translation completed 4 days ago
User avatar admin

Translation changed
In some rare cases a microcode update from the kernel can be ineffective. For example, despite intel-microcode-20241029 contains the Raptor Lake microcode revision 0x12b which is intended to fix a notorious excessive voltage issue causing stability issues and even permanent CPU damages, when the kernel boots it's already <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>too late</ulink> for the microcode to fix the issue. The only way to fix this issue is updating the BIOS.
Dans de rares cas la mise à jour du micrologiciel à partir du noyau peut ne pas fonctionner. Par exemple, bien que intel-microcode-2024091029 contienne le micrologiciel de Raptor Lake révision 0x129b qui doit corriger un problème de voltage excessif notoire qui cause des problèmes de stabilité et endommage même le CPU de manière permanente, lorsque le noyau démarre il est déjà <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>trop tard</ulink> pour que le micrologiciel puisse corriger le problème. Le seul moyen de corriger le problème est de mettre à jour le BIOS.
4 days ago
User avatar None

Resource updated
The “blfs/fr/postlfs/config/firmware.po” file was changed. 9 days ago
User avatar None

String added in the repository
In some rare cases a microcode update from the kernel can be ineffective. For example, despite intel-microcode-20241029 contains the Raptor Lake microcode revision 0x12b which is intended to fix a notorious excessive voltage issue causing stability issues and even permanent CPU damages, when the kernel boots it's already <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>too late</ulink> for the microcode to fix the issue. The only way to fix this issue is updating the BIOS.
Dans de rares cas la mise à jour du micrologiciel à partir du noyau peut ne pas fonctionner. Par exemple, bien que intel-microcode-20240910 contienne le micrologiciel de Raptor Lake révision 0x129 qui doit corriger un problème de voltage excessif notoire qui cause des problèmes de stabilité et endommage même le CPU de manière permanente, lorsque le noyau démarre il est déjà <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>trop tard</ulink> pour que le micrologiciel puisse corriger le problème. Le seul moyen de corriger le problème est de mettre à jour le BIOS.
9 days ago
User avatar None

Source string changed
In some rare cases a microcode update from the kernel can be ineffective. For example, despite intel-microcode-2024091029 contains the Raptor Lake microcode revision 0x129b which is intended to fix a notorious excessive voltage issue causing stability issues and even permanent CPU damages, when the kernel boots it's already <ulink url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/78#issuecomment-2286857023'>too late</ulink> for the microcode to fix the issue. The only way to fix this issue is updating the BIOS.
9 days ago
User avatar admin

Resource updated
The “blfs/fr/postlfs/config/firmware.po” file was changed. a month ago
User avatar admin

Changes committed
Changes committed a month ago
Browse all translation changes