Translation status

20 Strings 100%
Browse Translate
614 Words 100%
4,191 Characters 100%

Strings status

Strings Words Characters
20 614 4,191
All strings Browse Translate Zen
20 614 4,191
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 9166af53de96dd822e35386ef6a1929ac480970a d6d7f172dd
Julien Lepiller authored 11 hours ago
Last commit in Weblate Automatic BLFS commit based on 9166af53de96dd822e35386ef6a1929ac480970a d6d7f172dd
Julien Lepiller authored 11 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter03/introduction.po
Translation file Download lfs/fr/chapter03/introduction.po
Last change Dec. 12, 2024, 2:23 p.m.
Last author None
9 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 20 614 4,191
Translated 100% 20 100% 614 100% 4,191
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 21 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 45 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

614
Hosted words
20
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed 9 days ago
User avatar admin

Translation completed
Translation completed 9 days ago
User avatar admin

Translation changed
For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar or even identical file names. But the release tarball may contain some files which are essential despite not stored in the repository (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.
Pour certains paquets, l'archive de version et l'instantané du dépôt (Git ou SVN) pour cette version peuvent être publiés avec des noms similaires. Ude fichiers similaires, voire identiques. Cependant, une archive de version publiée peut contientir des fichiers générésessentiels bien que non présents dans le dépôt (par exemple, un script <command>configure</command> généré par <command>autoconf</command>) en plus du contenu de l'instantané du dépôt. Le livre utilise les archives de version chaque fois que cela est possible. Utiliser des instantanés de dépôt au lieu des archives de version spécifiées dans le livre causera des problèmes.
9 days ago
User avatar None

Resource updated
The “lfs/fr/chapter03/introduction.po” file was changed. 9 days ago
User avatar None

String added in the repository
For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar or even identical file names. But the release tarball may contain some files which are essential despite not stored in the repository (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.
Pour certains paquets, l'archive de version et l'instantané du dépôt (Git ou SVN) pour cette version peuvent être publiés avec des noms similaires. Une archive de version contient des fichiers générés (par exemple, un script <command>configure</command> généré par <command>autoconf</command>) en plus du contenu de l'instantané du dépôt. Le livre utilise les archives de version chaque fois que cela est possible. Utiliser des instantanés de dépôt au lieu des archives de version spécifiées dans le livre causera des problèmes.
9 days ago
User avatar None

Source string changed
For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar or even identical file names. ABut the release tarball may contains generated files some files which are essential despite not stored in the repository (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.
9 days ago
User avatar admin

Resource updated
The “lfs/fr/chapter03/introduction.po” file was changed. a year ago
User avatar None

String updated in the repository
<userinput>chown root:root $LFS/sources/*</userinput>
<userinput>chown root:root $LFS/sources/*</userinput>
a year ago
User avatar None

String updated in the repository
If the packages and patches are downloaded as a non-&root; user, these files will be owned by the user. The file system records the owner by its UID, and the UID of a normal user in the host distro is not assigned in LFS. So the files will be left owned by an unnamed UID in the final LFS system. If you won't assign the same UID for your user in the LFS system, change the owners of these files to &root; now to avoid this issue:
Si vous téléchargez les paquets et les correctifs en tant qu’utilisateur non-&root;, ces fichiers appartiendront à l’utilisateur. Le système de fichiers identifie le propriétaire par son UID et l’UID d’un utilisateur normal dans la distribution hôte n’est pas attribué dans LFS. Dans ce cas, le propriétaire par défaut des fichiers sera un UID sans nom dans le système LFS final. Si vous n’attribuez pas le même UID à votre utilisateur dans le système LFS, changez dès maintenant les propriétaires de ces fichiers à &root; afin d’éviter le problème suivant&nbsp;:
a year ago
User avatar None

String updated in the repository
This check can be used after retrieving the needed files with any of the methods listed above.
Vous pouvez utiliser cette vérification après avoir récupéré les fichiers nécessaires avec une des méthodes proposées plus haut.
a year ago
Browse all translation changes