Translation status

13 Strings 100%
Browse Translate
742 Words 100%
5,094 Characters 100%

Strings status

Strings Words Characters
13 742 5,094
All strings Browse Translate Zen
13 742 5,094
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
postlfs_filesystems_fuse3 0 0 0 0 10 0 0
pst_printing_gs 0 0 0 0 19 0 0
xincludes_use-unzip 0 0 0 0 0 0 0
x_installing_xorg7 0 0 0 0 8 0 0
x_icons_oxygen-icons5 0 0 0 0 7 0 0
postlfs_security_ssh-askpass 0 0 0 0 10 0 0
networking_netprogs_samba 98% 5 184 2,536 1 130 0 0
multimedia_videoutils_transcode 0 0 0 0 41 0 0
multimedia_audioutils_cdparanoia 0 0 0 0 15 0 0
multimedia_libdriv_liba52 0 0 0 0 8 0 0
Browse all components

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 211f21160f55871124b7a32e5fa0b7586e2945f3 e0f0c98b7d
Julien Lepiller authored 10 hours ago
Last commit in Weblate Translated using Weblate (French) 7b1fe78058
Weblate Admin authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/introduction/important/libraries.po
Translation file Download blfs/fr/introduction/important/libraries.po
Last change Sept. 20, 2023, 4:20 a.m.
Last author Weblate Admin
13 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 13 742 5,094
Translated 100% 13 100% 742 100% 5,094
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 1 change 0 changes 0 changes 0 changes 18 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 15 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

742
Hosted words
13
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 admin

Resource updated

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
The "blfs/fr/introduction/important/libraries.po" file was changed. 7 months ago
User avatar None

Changes committed

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
Changes committed 7 months ago
User avatar admin

Translation changed

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
libraries
bibliothèqulibraries
7 months ago
User avatar admin

Translation changed

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
libraries
libraribibliothèques
7 months ago
User avatar admin

Resource updated

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
The "blfs/fr/introduction/important/libraries.po" file was changed. 7 months ago
User avatar None

String updated in the repository

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
Sometimes, deciding to use system libraries is an easy decision. Other times it may require you to alter the system version (e.g. for <xref linkend="libpng"/> if used for <xref linkend="firefox"/>). Occasionally, a package ships an old library and can no longer link to the current version, but can link to an older version. In this case, BLFS will usually just use the shipped version. Sometimes the included library is no longer developed separately, or its upstream is now the same as the package&apos;s upstream and you have no other packages which will use it. In those cases, you'll be lead to use the included library even if you usually prefer to use system libraries.
Parfois, il est facile de décider d'utiliser les bibliothèques du système. D'autres fois il se peut que vous deviez modifier la version du système (c'est le cas pour <xref linkend="libpng"/> si on l'utilise pour <xref linkend="firefox"/>). Parfois, un paquet contient une ancienne bibliothèque et ne peut plus se lier à la version actuelle, mais il peut se lier à une version plus ancienne. Dans ce cas, BLFS utilisera généralement la version incluse. Parfois, la bibliothèque incluse n'est plus développée de son côté, ou ses responsables en amont sont les mêmes que celles et ceux du paquet et vous n'avez aucun autre paquet qui l'utilisera. Dans ces cas, vous pourriez décider d'utiliser la bibliothèque incluse même si vous préférez généralement utiliser les bibliothèques du système.
7 months ago
User avatar None

String updated in the repository

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
When BLFS mentions system libraries, it means shared versions of libraries. Some packages such as <xref linkend="firefox"/> and <xref linkend="gs"/> bundle many other libraries in their build tree. The version they ship is often older than the version used in the system, so it may contain bugs &ndash; sometimes developers go to the trouble of fixing bugs in their included libraries, other times they do not.
Quand BLFS indique des bibliothèques système, cela signifie les versions partagées. Certains paquets tels que <xref linkend="firefox"/> et <xref linkend="gs"/> embarquent beaucoup d'autres bibliothèques dans leur arborescence de construction. La version incluse est souvent plus ancienne que la version utilisée dans le système, donc il se peut qu'elle comporte des bogues. Parfois les développeurs prennent la peine de corriger les bogues dans les bibliothèques qu'ils incluent, mais pas toujours.
7 months ago
User avatar None

String updated in the repository

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
Many packages put some of their common functions into a static library which is only used by the programs within the package and, crucially, the library is <emphasis>not</emphasis> installed as a standalone library. These internal libraries are not a problem &ndash; if the package has to be rebuilt to fix a bug or vulnerability, nothing else is linked to them.
De nombreux paquets mettent certaines de leurs fonctions courantes dans une bibliothèque qui n'est utilisée que par les programmes du paquet et qui, surtout, <emphasis>n'est pas</emphasis> installée en tant que bibliothèque autonome. Ces bibliothèques internes ne posent pas problème — si le paquet doit être reconstruit pour corriger un bogue ou une faille de sécurité, rien de plus n'y est lié.
7 months ago
User avatar None

String updated in the repository

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
If you use this approach, you may discover that more packages than you were expecting use a static library. That was the case with <application>nettle-2.4</application> in its default static-only configuration: It was required by <application>GnuTLS-3.0.19</application>, but also linked into package(s) which used <application>GnuTLS</application>, such as <application>glib-networking-2.32.3</application>.
Si vous faites cela, il se peut que vous trouviez que plus de paquets que vous ne le pensiez utilisent une bibliothèque statique. C'était le cas avec <application>nettle-2.4</application> dans sa configuration par défaut en statique seulement&nbsp;: il était requis par <application>GnuTLS-3.0.19</application>, mais aussi lié à des paquets qui utilisaient <application>GnuTLS-3.0.19</application>, tels que <application>glib-networking-2.32.3</application>.
7 months ago
User avatar None

String updated in the repository

  1. Beyond Linux From Scratch
  2. introduction_important_libraries
  3. French
One way to identify when a static library is used, is to deal with it at the end of the installation of every package. Write a script to find all the static libraries in <filename class="directory">/usr/lib</filename> or wherever you are installing to, and either move them to another directory so that they are no longer found by the linker, or rename them so that <filename>libfoo.a</filename> becomes e.g. <filename>libfoo.a.hidden</filename>. The static library can then be temporarily restored if it is ever needed, and the package needing it can be identified. This shouldn't be done blindly since many libraries only exist in a static version. For example, some libraries from the <application>glibc</application> and <application>gcc</application> packages should always be present on the system (<filename>libc_nonshared.a, libg.a, libpthread_nonshared.a, libssp_nonshared.a, libsupc++.a</filename> as of glibc-2.36 and gcc-12.2).
Une manière d'identifier si une bibliothèque statique est utilisée est de s'en préoccuper à la fin de l'installation de chaque paquet. Écrivez un script pour trouver toutes les bibliothèques statiques dans <filename class="directory">/usr/lib</filename> ou bien là où vous installez, puis déplacez-les dans un autre répertoire de sorte que l'éditeur de liens ne les trouve plus ou renommez-les pour que <filename>libtoto.a</filename> devienne par exemple <filename>libtoto.a.hidden</filename>. Vous pouvez alors restaurer temporairement une bibliothèque statique si nécessaire, et identifier les paquets qui en ont besoin. Vous ne devriez pas le faire sans réfléchir car de nombreuses bibliothèques n'existent qu'en version statique. Par exemple, certaines bibliothèques des paquets <application>glibc</application> et <application>gcc</application> devraient toujours être présentes sur le système (<filename>libc_nonshared.a, libg.a, libpthread_nonshared.a, libssp_nonshared.a, libsupc++.a</filename> pour glibc-2.36 et gcc-12.2).
7 months ago
Browse all translation changes