Translation status

12 Strings 100%
Browse Translate
665 Words 100%
4,424 Characters 100%

Strings status

Strings Words Characters
12 665 4,424
All strings Browse Translate Zen
12 665 4,424
Translated strings Browse Translate Zen
1 229 1,666
Strings with any failing checks Browse Translate Zen
1 229 1,666
Translated strings with any failing checks Browse Translate Zen
1 229 1,666
Failing check: Punctuation spacing 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 11.3
Last remote commit Update translations for 11.3 6bfb71d1dc
Julien Lepiller authored a year ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 84a1614077
User avatar jamenson authored a year ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-11-3/index/
File mask blfs/*/introduction/important/la-files.po
Translation file Download blfs/fr/introduction/important/la-files.po
Last change March 11, 2023, 9:26 a.m.
Last author None
3 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 12 665 4,424
Translated 100% 12 100% 665 100% 4,424
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 8% 1 34% 229 37% 1,666
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 0 changes 13 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
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

665
Hosted words
12
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

Resource updated
File “blfs/fr/introduction/important/la-files.po” was added. a year ago
User avatar None

String updated in the repository
User Notes: <ulink url="&blfs-wiki;/la-files"/>
Notes utilisateur&nbsp;: <ulink url="&blfs-wiki;/la-files"/>
a year ago
User avatar None

String updated in the repository
<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF"
<literal>#!/bin/bash

# /usr/sbin/remove-la-files.sh
# Written for Beyond Linux From Scratch
# by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt;

# Make sure we are running with root privs
if test "${EUID}" -ne 0; then
echo "Error: $(basename ${0}) must be run as the root user! Exiting..."
exit 1
fi

# Make sure PKG_CONFIG_PATH is set if discarded by sudo
source /etc/profile

OLD_LA_DIR=/var/local/la-files

mkdir -p $OLD_LA_DIR

# Only search directories in /opt, but not symlinks to directories
OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d)

# Move any found .la files to a directory out of the way
find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \
-exec mv -fv {} $OLD_LA_DIR \;
###############

# Fix any .pc files that may have .la references

STD_PC_PATH='/usr/lib/pkgconfig
/usr/share/pkgconfig
/usr/local/lib/pkgconfig
/usr/local/share/pkgconfig'

# For each directory that can have .pc files
for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do

# For each pc file
for pc in $d/*.pc ; do
if [ $pc == "$d/*.pc" ]; then continue; fi

# Check each word in a line with a .la reference
for word in $(grep '\.la' $pc); do
if $(echo $word | grep -q '.la$' ); then
mkdir -p $d/la-backup
cp -fv $pc $d/la-backup

basename=$(basename $word )
libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//')

# Fix the .pc file
sed -i "s:$word:$libref:" $pc
fi
done
done
done</literal>

EOF

chmod +x /usr/sbin/remove-la-files.sh</userinput>
<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF"
<literal>#!/bin/bash

# /usr/sbin/remove-la-files.sh
# Written for Beyond Linux From Scratch
# by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt;

# Make sure we are running with root privs
if test "${EUID}" -ne 0; then
echo "Error: $(basename ${0}) must be run as the root user! Exiting..."
exit 1
fi

# Make sure PKG_CONFIG_PATH is set if discarded by sudo
source /etc/profile

OLD_LA_DIR=/var/local/la-files

mkdir -p $OLD_LA_DIR

# Only search directories in /opt, but not symlinks to directories
OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d)

# Move any found .la files to a directory out of the way
find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \
-exec mv -fv {} $OLD_LA_DIR \;
###############

# Fix any .pc files that may have .la references

STD_PC_PATH='/usr/lib/pkgconfig
/usr/share/pkgconfig
/usr/local/lib/pkgconfig
/usr/local/share/pkgconfig'

# For each directory that can have .pc files
for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do

# For each pc file
for pc in $d/*.pc ; do
if [ $pc == "$d/*.pc" ]; then continue; fi

# Check each word in a line with a .la reference
for word in $(grep '\.la' $pc); do
if $(echo $word | grep -q '.la$' ); then
mkdir -p $d/la-backup
cp -fv $pc $d/la-backup

basename=$(basename $word )
libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//')

# Fix the .pc file
sed -i "s:$word:$libref:" $pc
fi
done
done
done</literal>

EOF

chmod +x /usr/sbin/remove-la-files.sh</userinput>
a year ago
User avatar None

String updated in the repository
The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.
Le script ci-dessous supprime tous les fichiers .la inutiles et les sauvegarde dans un répertoire, /var/local/la-files par défaut, qui ne se trouve pas dans le chemin de recherche habituel des bibliothèques. Il recherche également les références à des fichiers .la dans les fichiers pkg-config (.pc) et les transforme en références de bibliothèques conventionnelles qui sont nécessaires lors de la construction d'une application ou d'une bibliothèque. Il peut être lancé au besoin pour nettoyer les répertoires qui causent des problèmes.
a year ago
User avatar None

String updated in the repository
The solution is to remove the .la files. However there is a catch. Some packages, such as <xref linkend='imagemagick'/>, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.
La solution consiste à supprimer les fichiers .la, mais il y a un inconvénient. Certains paquets, comme <xref linkend='imagemagick'/>, utilisent une fonction de libtool, lt_dlopen, pour charger les bibliothèques requises pendant l'exécution et résoudre leurs dépendances à l'exécution. Dans ce cas, les fichiers .la ne doivent pas être supprimés.
a year ago
User avatar None

String updated in the repository
The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extension and contain information that is similar to that embedded in the libraries or pkg-config files. When building a package that uses libtool, the process automatically looks for these files. Sometimes a .la file can contains the name or path of a static library used during build but not installed, then the build process will break because the .la file refers to something nonexistent on the system. Similarly, if a package is updated and no longer uses the .la file, then the build process can break with the old .la files.
Le problème est que libtool crée typiquement un ou plusieurs fichiers texte pour les paquets de bibliothèques appelés archives libtool. Ces petits fichiers ont l'extension «&nbsp;.la&nbsp;» et contiennent des informations identiques à celles incluses dans les bibliothèques ou les fichiers pkg-config. Lors de la construction d'un paquet qui utilise libtool, le processus cherche automatiquement ces fichiers. Parfois un fichier .la peut contenir le nom ou le chemin d'une bibliothèque statique utilisée pendant la construction mais jamais installée, et le processus de construction échoue car le fichier .la se réfère à un objet inexistant sur le système. De même, si un paquet est mis à jour et n'utilise plus de fichier .la, le processus de construction peut échouer à cause de l'ancien fichier .la.
a year ago
User avatar None

String updated in the repository
Static libraries are rarely used in LFS and BLFS. And, nowadays most packages store the information needed for linking against a static library into a .pc file, instead of relying on libtool. A <command>pkg-config --static --libs</command> command will output the sufficient flags for the linker to link against a static library without any libtool magic.
Le bibliothèques statiques sont rarement utilisées dans LFS et BLFS. De nos jours la plupart des paquets stockent les informations requises pour la liaisons aux bibliothèques statiques dans un fichier .pc, au lieu de s'appuyer sur libtool. La commande <command>pkg-config --static --libs</command> affichera les drapeaux nécessaires à l'éditeur des liens pour se lier à une bibliothèque statique sans la magie de libtool.
a year ago
User avatar None

String updated in the repository
On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> Executable and Linkable Format (ELF)</ulink> for executables and dynamic libraries, information needed to complete the task is embedded in the files. Both the linker and the program loader can query the appropriate files and properly link or execute the program.
Sur un système Linux, les fichiers spécifiques à libtool sont généralement inutiles. En temps normal, les bibliothèques sont spécifiées dans le processus de construction pendant l'édition des liens. Comme un système Linux utilise le <ulink url="https://fr.wikipedia.org/wiki/Executable_and_Linkable_Format">format exécutable et liable (ELF)</ulink> pour les exécutables et les bibliothèques, les informations nécessaires à cette tâche sont incluses dans les fichiers. Aussi bien le chargeur de programme que l'éditeur des liens peuvent demander les fichiers requis, ainsi que charger et exécuter correctement le programme.
a year ago
User avatar None

String updated in the repository
In LFS and BLFS, many packages use a internally shipped libtool copy to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.
Dans LFS et BLFS, de nombreux paquets utilisent une copie interne de libtool pour se construire sur diverses plateformes Unix. Cela comprend des plateformes comme AIX, Solaris, IRIX, HP-UX et Cygwin, ainsi que Linux. Les origines de cet outil sont assez anciennes. Son objectif premier était de gérer les bibliothèques sur des systèmes aux capacités moins avancées qu'un système Linux moderne.
a year ago
User avatar None

String updated in the repository
Files with a .la extension
Fichiers avec une extension .la
a year ago
Browse all translation changes