Translation status

6 Strings 33%
Browse Translate
327 Words 5%
2,016 Characters 8%

Strings status

Strings Words Characters
6 327 2,016
All strings Browse Translate Zen
2 18 165
Translated strings Browse Translate Zen
4 309 1,851
Unfinished strings Browse Translate Zen
4 309 1,851
Strings marked for edit Browse Translate Zen
4 309 1,851
Unfinished strings without suggestions Browse Translate Zen
1 103 616
Strings with any failing checks Browse Translate Zen
1 103 616
Failing check: Mismatched full stop 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 7ef1db772f3ce108a14d196d2f8faed9ae5607ad 621f4aa8f9
Julien Lepiller authored 41 minutes ago
Last commit in Weblate Automatic BLFS commit based on 7ef1db772f3ce108a14d196d2f8faed9ae5607ad 621f4aa8f9
Julien Lepiller authored 41 minutes ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/prologue/architecture.po
Translation file Download lfs/zh_CN/prologue/architecture.po
Last change Jan. 19, 2024, 4:23 a.m.
Last change made by Weblate Admin
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 1,286,095,292
Number of plurals 1
Plural type None
Plurals
Plural formula 0
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 6 327 2,016
Translated 33% 2 5% 18 8% 165
Needs editing 66% 4 94% 309 91% 1,851
Read-only 0% 0 0% 0 0% 0
Failing checks 16% 1 31% 103 30% 616
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

12 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 0 changes 0 changes 0 changes 0 changes 7 changes 0 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

327
Hosted words
6
Hosted strings
33%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+33%
—
Contributors
—
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
User avatar None

String updated in the repository
<computeroutput>Architecture Build Time Build Size
32-bit 239.9 minutes 3.6 GB
64-bit 233.2 minutes 4.4 GB</computeroutput>
<computeroutput>架构 构建时间 系统大小
32 位 239.9 分钟 3.6 GB
64 位 233.2 分钟 4.4 GB</computeroutput>
a year ago
User avatar None

String updated in the repository
The gain from building on a 64-bit system, as compared to a 32-bit system, is minimal. For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system, using 4 cores, the following statistics were measured:
对于构建 LFS 来说，构建 64 位系统相较于 32 位系统而言只会获得很小的收益。例如，在使用安装了 Core i7-4790 CPU 的系统测试构建 LFS-9.1 时，我们得到的实验数据为：
a year ago
User avatar None

String updated in the repository
The primary target architectures of LFS are the AMD/Intel x86 (32-bit) and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are also known to work, with some modifications, with the Power PC and ARM CPUs. To build a system that utilizes one of these alternative CPUs, the main prerequisite, in addition to those on the next page, is an existing Linux system such as an earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution that targets that architecture. (Note that a 32-bit distribution can be installed and used as a host system on a 64-bit AMD/Intel computer.)
LFS 的主要目标架构是 AMD/Intel 的 x86 (32 位) 和 x86_64 (64 位) CPU。此外，如果对本书中的一些指令作适当的修改，它们也应该适用于 Power PC 和 ARM 架构的 CPU。无论在其中哪种 CPU 上，构建 LFS 都至少需要一个现有的 Linux 系统，例如已经构建好的 LFS 系统，Ubuntu，Rad Hat/Fedora，SuSE，或者其他支持您的硬件架构的发行版，后文中还会介绍其他前提条件。另外，32 位发行版也能在 64 位的 AMD/Intel 计算机上正常运行，并作为 LFS 的构建环境。
a year ago
User avatar None

String updated in the repository
LFS Target Architectures
LFS 的目标架构
a year ago
User avatar None

Resource updated
File “lfs/zh_CN/prologue/architecture.po” was added. 2 years 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"/> 查阅。但这是一个比较复杂的主题。
2 years ago
User avatar None

Source string changed
The default 64-bit build that results from LFS is considered 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 straightforward baseic Linux system. Some of the LFS/BLFS editors maintain a multilib fork of LFS for multilib, which is, accessible at <ulink url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it ithat's an advanced topic.
2 years ago
Browse all translation changes