Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 100% 0 0 0 0 1 0 0
Chinese (Simplified Han script) 33% 4 309 1,851 0 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 trunk
Last remote commit Automatic BLFS commit based on 0f8d3a0501f2c0daba177f874b995170e779591e 08a7650aa1
Julien Lepiller authored 7 hours ago
Last commit in Weblate Automatic BLFS commit based on 0f8d3a0501f2c0daba177f874b995170e779591e 08a7650aa1
Julien Lepiller authored 7 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/prologue/architecture.po
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 24 1,308 8,064
Source 6 327 2,016
Translated 83% 20 76% 999 77% 6,213
Needs editing 16% 4 23% 309 22% 1,851
Read-only 25% 6 25% 327 25% 2,016
Failing checks 8% 2 15% 206 15% 1,232
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

30 changes 1 change 13 changes 0 changes 7 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 15 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 17 changes 0 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

1,308
Hosted words
24
Hosted strings
83%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+83%
—
Contributors
—
User avatar admin

Changes committed
Changes committed 3 months ago
User avatar jamenson

Translation changed
As you can see, on the same hardware, the 64-bit build is only 3% faster (and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP server, or a firewall, a 32-bit CPU may be good enough. On the other hand, several packages in BLFS now need more than 4 GB of RAM to be built and/or to run; if you plan to use LFS as a desktop, the LFS authors recommend building a 64-bit system.
Como você pode ver, no mesmo hardware, a construção de 64 bits é somente 3% mais rápida (e 22% mais largaor) que a construção de 32 bits. Se você planeja usar o LFS como um servidor LAMP, ou como um firewall, [então] uma CPU de 32 bits possivelmente seja boa o suficiente. Por outro lado, vários pacotes no BLFS atualmente precisam de mais que 4 GB de RAM para serem construídos e (ou) para executarem; se você planeja usar o LFS como um desktop, [então] os(as) autores(as) do LFS recomendam construir um sistema de 64 bits.
3 months ago
User avatar jamenson

Contributor joined
Contributor joined 3 months ago
User avatar None

Component unlocked
Fixing an alert automatically unlocked the component. 7 months ago
User avatar None

Component locked
The component was automatically locked because of an alert. 7 months ago
User avatar None

Alert triggered
Could not update the repository. 7 months ago
User avatar None

Alert triggered
Component seems unused. a year ago
User avatar admin

Resource updated
The “lfs/zh_CN/prologue/architecture.po” file was changed. a year ago
User avatar None

String updated in the repository
The default 64-bit build that results from LFS is a <quote>pure</quote> 64-bit system. That is, it supports 64-bit executables only. Building a <quote>multi-lib</quote> system requires compiling many applications twice, once for a 32-bit system and once for a 64-bit system. This is not directly supported in LFS because it would interfere with the educational objective of providing the minimal instructions needed for a basic Linux system. Some of the LFS/BLFS editors maintain a multilib fork of LFS, accessible at <ulink url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But that's an advanced topic.
完全按照本书构建的 LFS 系统是一个<quote>纯粹的</quote> 64 位系统。换句话说，它只能运行 64 位可执行程序。构建一个<quote>multi-lib</quote> 系统需要将许多应用程序编译两次，一次编译为 32 位，另一次编译为 64 位。本书不提供这方面的内容，因为本书的教学目的是提供简洁的基本 Linux 系统的构建方法，讨论 multilib 会和这一目标发生冲突。一些 LFS/BLFS 编辑维护了 LFS 的 multilib 版本，可以在 <ulink url="http://www.linuxfromscratch.org/~thomas/multilib/index.html"/> 查阅。但这是一个比较复杂的主题。
a year ago
User avatar None

String updated in the repository
As you can see, on the same hardware, the 64-bit build is only 3% faster (and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP server, or a firewall, a 32-bit CPU may be good enough. On the other hand, several packages in BLFS now need more than 4 GB of RAM to be built and/or to run; if you plan to use LFS as a desktop, the LFS authors recommend building a 64-bit system.
可以看出，在相同的硬件上，64 位系统的构建仅仅比 32 位快 3%，但占用的磁盘空间却比 32 位系统大 22%。如果您准备用 LFS 系统运行 LAMP 服务器，或者防火墙，那么 32 位 CPU 足以满足需求。然而，BLFS 中的一些软件包在构建或运行过程中可能需要超过 4GB 的内存，因此如果您准备将 LFS 作为桌面系统，LFS 作者推荐构建 64 位系统。
a year ago
Browse all component changes