Translation status

122 Strings 100%
Browse Translate
732 Words 100%
6,385 Characters 100%

Strings status

Strings Words Characters
122 732 6,385
All strings Browse Translate Zen
122 732 6,385
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 12.1
Last remote commit Add pt_BR translation e751a3b16e
Julien Lepiller authored 8 months ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 345a919031
User avatar jamenson authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask lfs/*/chapter08/binutils.po
Translation file Download lfs/fr/chapter08/binutils.po
Last change March 30, 2024, 8:14 a.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 122 732 6,385
Translated 100% 122 100% 732 100% 6,385
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 127 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 0 changes 0 changes
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Quick numbers

732
Hosted words
122
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed 9 months ago
User avatar admin

Suggestion accepted
Normally, the tooldir (the directory where the executables will ultimately be located) is set to <filename class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, x86_64 machines would expand that to <filename class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is a custom system, this target-specific directory in <filename class="directory">/usr</filename> is not required. <filename class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the system were used to cross-compile (for example, compiling a package on an Intel machine that generates code that can be executed on PowerPC machines).
Normalement, le nom du répertoire tooldir (où seront situés les exécutables) est configuré de cette manière&nbsp;: <filename class="directory">$(exec_prefix)/$(target_alias)</filename>. Les machines x86_64 y ajouteront <filename class="directory">/usr/x86_64-pc-linux-gnu</filename>. Comme il s'agit d'un système personnalisé, il n'est pas nécessaire d'avoir un répertoire spécifique à la cible dans <filename class="directory">/usr</filename>. Si le système était utilisé pour la compilation croisée (par exemple pour compiler un paquet sur une machine Intel qui génère du code pouvant être exécuté sur des machines PowerPC), le répertoire s’appellerait <filename class="directory">$(exec_prefix)/$(target_alias)</filename>.
9 months ago
User avatar admin

Contributor joined
Contributor joined 9 months ago
User avatar anonymous

Suggestion added
Normally, the tooldir (the directory where the executables will ultimately be located) is set to <filename class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, x86_64 machines would expand that to <filename class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is a custom system, this target-specific directory in <filename class="directory">/usr</filename> is not required. <filename class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the system were used to cross-compile (for example, compiling a package on an Intel machine that generates code that can be executed on PowerPC machines).
Normalement, le nom du répertoire tooldir (où seront situés les exécutables) est configuré de cette manière&nbsp;: <filename class="directory">$(exec_prefix)/$(target_alias)</filename>. Les machines x86_64 y ajouteront <filename class="directory">/usr/x86_64-pc-linux-gnu</filename>. Comme il s'agit d'un système personnalisé, il n'est pas nécessaire d'avoir un répertoire spécifique à la cible dans <filename class="directory">/usr</filename>. Si le système était utilisé pour la compilation croisée (par exemple pour compiler un paquet sur une machine Intel qui génère du code pouvant être exécuté sur des machines PowerPC), le répertoire s’appellerait <filename class="directory">$(exec_prefix)/$(target_alias)</filename>.
10 months ago
User avatar None

Resource updated
File “lfs/fr/chapter08/binutils.po” was added. 10 months ago
User avatar None

String updated in the repository
libsframe
libsframe
10 months ago
User avatar None

String updated in the repository
A library to support online backtracing using a simple unwinder
Une bibliothèque pour prendre en charge le bactracking en ligne avec un simple dérouleur
10 months ago
User avatar None

String updated in the repository
<filename class="libraryfile">libsframe</filename>
<filename class="libraryfile">libsframe</filename>
10 months ago
User avatar None

String updated in the repository
libopcodes
libopcodes
10 months ago
User avatar None

String updated in the repository
A library for dealing with opcodes&mdash;the <quote>readable text</quote> versions of instructions for the processor; it is used for building utilities like <command>objdump</command>
Une bibliothèque de gestion des codes opération, la <quote>version lisible</quote> des instructions du processeur. Elle est utilisée pour construire des utilitaires comme <command>objdump</command>
10 months ago
Browse all translation changes