Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
Chinese (Simplified Han script) 36% 7 422 2,831 1 1 0 0
French 0 0 0 0 0 0 0
Portuguese (Brazil) 0 0 0 0 0 0 0
Please sign in to see the alerts.

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 5 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask lfs/*/chapter08/introduction.po
3 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 44 2,236 14,820
Source 11 559 3,705
Translated 84% 37 81% 1,814 80% 11,989
Needs editing 13% 6 15% 338 15% 2,257
Read-only 25% 11 25% 559 25% 3,705
Failing checks 2% 1 1% 1 1% 12
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 2% 1 3% 84 3% 574
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 0 changes 56 changes 0 changes 0 changes 0 changes 1 change 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

2,236
Hosted words
44
Hosted strings
84%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Alert triggered
Repository has changes. 5 months ago
User avatar admin

Suggestion removed
We do not recommend using customized optimizations. They can make a program run slightly faster, but they may also cause compilation difficulties, and problems when running the program. If a package refuses to compile with a customized optimization, try to compile it without optimization and see if that fixes the problem. Even if the package does compile when using a customized optimization, there is the risk it may have been compiled incorrectly because of the complex interactions between the code and the build tools. Also note that the <option>-march</option> and <option>-mtune</option> options using values not specified in the book have not been tested. This may cause problems with the toolchain packages (Binutils, GCC and Glibc). The small potential gains achieved by customizing compiler optimizations are often outweighed by the risks. First-time builders of LFS are encouraged to build without custom optimizations.
L'utilisation d'optimisations personnalisées est déconseillée. Bien qu'elles puissent accélérer légèrement l'exécution des programmes, elles peuvent aussi poser des problèmes lors de leur compilation ou leur exécution. Si un paquet refuse de se compiler lors de l'utilisation d'optimisations, essayez de le compiler sans optimisation pour voir si cela corrige le problème. Même si le paquet parvient à se compiler avec les optimisations, il risque de mal se compiler à cause des interactions complexes entre le code et les outils de construction. Remarquez aussi que l'utilisation des options <option>-march</option> et <option>-mtune</option> avec des valeurs non indiquées dans LFS n'a pas été testée. Cela peut entrainer des problèmes avec les paquets de la chaîne d'outils (Binutils, GCC et Glibc). Le petit potentiel de gains obtenus en utilisant les optimisations de compilation est souvent minime comparé aux risques. Les utilisateurs construisant un système LFS pour la première fois sont encouragés à construire sans optimisations personnalisées.
7 months ago
User avatar anonymous

Suggestion added
We do not recommend using customized optimizations. They can make a program run slightly faster, but they may also cause compilation difficulties, and problems when running the program. If a package refuses to compile with a customized optimization, try to compile it without optimization and see if that fixes the problem. Even if the package does compile when using a customized optimization, there is the risk it may have been compiled incorrectly because of the complex interactions between the code and the build tools. Also note that the <option>-march</option> and <option>-mtune</option> options using values not specified in the book have not been tested. This may cause problems with the toolchain packages (Binutils, GCC and Glibc). The small potential gains achieved by customizing compiler optimizations are often outweighed by the risks. First-time builders of LFS are encouraged to build without custom optimizations.
L'utilisation d'optimisations personnalisées est déconseillée. Bien qu'elles puissent accélérer légèrement l'exécution des programmes, elles peuvent aussi poser des problèmes lors de leur compilation ou leur exécution. Si un paquet refuse de se compiler lors de l'utilisation d'optimisations, essayez de le compiler sans optimisation pour voir si cela corrige le problème. Même si le paquet parvient à se compiler avec les optimisations, il risque de mal se compiler à cause des interactions complexes entre le code et les outils de construction. Remarquez aussi que l'utilisation des options <option>-march</option> et <option>-mtune</option> avec des valeurs non indiquées dans LFS n'a pas été testée. Cela peut entrainer des problèmes avec les paquets de la chaîne d'outils (Binutils, GCC et Glibc). Le petit potentiel de gains obtenus en utilisant les optimisations de compilation est souvent minime comparé aux risques. Les utilisateurs construisant un système LFS pour la première fois sont encouragés à construire sans optimisations personnalisées.
7 months ago
User avatar None

Resource updated
File “lfs/zh_CN/chapter08/introduction.po” was added. 8 months ago
User avatar None

String updated in the repository
For a more complete discussion of libraries, see <ulink url="&blfs-book;introduction/libraries.html"> Libraries: Static or shared?</ulink> in the BLFS book.
关于库的更详细讨论，可以参阅 BLFS 手册中的 <ulink url="&blfs-root;/view/&short-version;/introduction/libraries.html">Libraries: Static or shared?</ulink> 一节。
8 months ago
User avatar None

Source string changed
For a more complete discussion of libraries, see the discussion <ulink url="&blfs-root;/view/&short-version;/book;introduction/libraries.html"> Libraries: Static or shared?</ulink> in the BLFS book.
8 months ago
User avatar None

String updated in the repository
The procedures in this chapter remove or disable installation of most static libraries. Usually this is done by passing a <option>--disable-static</option> option to <command>configure</command>. In other cases, alternate means are needed. In a few cases, especially Glibc and GCC, the use of static libraries remains an essential feature of the package building process.
在本章的安装过程中，我们删除或者禁止安装多数静态库。一般来说，传递 <option>--disable-static</option> 选项给 <command>configure</command> 就可以禁用静态库。然而，某些情况下需要其他手段。在极个别情况下，特别是对于 Glibc 和 GCC，静态库对于一般的软件包构建过程仍然很关键，就不能禁用静态库。
8 months ago
User avatar None

Source string changed
In tThe procedures in this chapter, we remove or disable installation of most static libraries. Usually this is done by passing a <option>--disable-static</option> option to <command>configure</command>. In other cases, alternate means are needed. In a few cases, especially gGlibc and gccGCC, the use of static libraries remains an essential to the generalfeature of the package building process.
8 months ago
User avatar None

String updated in the repository
In general, the LFS editors discourage building and installing static libraries. Most static libraries have been made obsolete in a modern Linux system. In addition, linking a static library into a program can be detrimental. If an update to the library is needed to remove a security problem, every program that uses the static library will need to be relinked with the new library. Since the use of static libraries is not always obvious, the relevant programs (and the procedures needed to do the linking) may not even be known.
一般来说，LFS 作者不推荐构建和安装静态库。它们是为了某些在现代 Linux 系统中早已过时的原因而存在的。另外，将静态库链接到程序中可能是有害的。如果需要更新这个库以解决安全问题，所有使用该静态库的程序都要重新链接到新版本的库。程序对静态库的使用并不总是显然的，甚至可能无法查明有哪些程序需要重新链接 (以及如何重新链接)。
8 months ago
User avatar None

Source string changed
In general, the LFS editors discourage building and installing static libraries. The original purpose for mMost static libraries hasve been made obsolete in a modern Linux system. In addition, linking a static library into a program can be detrimental. If an update to the library is needed to remove a security problem, allevery programs that uses the static library will need to be relinked towith the new library. Since the use of static libraries is not always obvious, the relevant programs (and the procedures needed to do the linking) may not even be known.
8 months ago
Browse all component changes