Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
chapter08_gettext 94% 6 80 753 1 0 0 0
chapter08_glibc 79% 47 1,085 9,329 8 11 0 0
chapter08_gmp 90% 4 120 877 1 3 0 0
chapter08_gperf 96% 1 4 70 1 0 0 0
chapter08_grep 82% 6 57 508 2 2 0 0
chapter08_groff 93% 11 113 848 3 2 0 0
chapter08_grub 74% 28 360 2,596 9 3 0 0
chapter08_gzip 98% 1 4 70 1 0 0 0
chapter08_iana-etc 95% 1 4 70 1 0 0 0
chapter08_inetutils 93% 4 36 559 2 2 0 0
chapter08_intltool 97% 1 4 70 1 0 0 0
chapter08_introduction 36% 7 422 2,831 1 0 0 0
chapter08_iproute2 76% 19 229 1,873 3 3 0 0
chapter08_jinja2 0% 17 55 654 17 0 0 0
chapter08_kbd 97% 3 38 319 1 1 0 0
chapter08_kmod 86% 7 78 878 2 2 0 0
chapter08_less 91% 3 12 143 2 1 0 0
chapter08_libcap 78% 10 86 785 1 0 0 0
chapter08_libelf 72% 8 50 623 4 1 0 0
chapter08_libffi 76% 7 188 1,437 2 2 0 0
chapter08_libpipeline 96% 1 4 70 1 0 0 0
chapter08_libtool 80% 8 128 943 2 0 0 0
chapter08_libxcrypt 0% 35 233 2,391 35 0 0 0
chapter08_m4 92% 2 74 545 1 1 0 0
chapter08_make 92% 2 15 161 1 1 0 0
chapter08_man-db 91% 11 90 1,509 5 1 0 0
chapter08_man-pages 77% 5 38 377 2 0 0 0
chapter08_markupsafe 0% 18 67 781 18 0 0 0
chapter08_meson 65% 10 80 966 5 0 0 0
chapter08_mpc 96% 1 4 70 1 1 0 0
chapter08_mpfr 87% 4 37 311 3 0 0 0
chapter08_ncurses 82% 17 188 2,154 4 3 0 0
chapter08_ninja 80% 6 143 1,067 1 4 0 0
chapter08_openssl 72% 13 399 3,210 6 6 0 0
chapter08_patch 96% 1 4 70 1 0 0 0
chapter08_perl 91% 11 235 1,578 1 0 0 0
chapter08_pkgconf 0% 36 155 1,616 36 0 0 0
chapter08_pkgmgt 35% 33 1,966 13,922 8 0 0 0
chapter08_procps 88% 9 50 899 1 2 0 0
chapter08_psmisc 93% 3 13 143 2 0 0 0
chapter08_python 62% 22 659 5,169 9 4 0 0
chapter08_readline 83% 7 81 615 3 3 0 0
chapter08_sed 92% 2 7 136 1 0 0 0
chapter08_shadow 77% 37 778 6,335 9 10 0 0
chapter08_stripping 0% 10 525 4,396 10 0 0 0
chapter08_sysklogd 90% 3 44 325 1 0 0 0
chapter08_systemd 69% 65 934 8,093 12 14 0 0
chapter08_sysvinit 88% 6 108 758 1 0 0 0
chapter08_tar 81% 6 136 986 3 2 0 0
chapter08_tcl 78% 11 170 1,472 2 3 0 0
chapter08_texinfo 96% 2 7 136 1 0 0 0
chapter08_udev 0% 66 515 5,661 66 0 0 0
chapter08_util-linux 87% 46 647 5,564 12 3 0 0
chapter08_vim 86% 10 266 2,173 2 2 0 0
chapter08_wheel 0% 22 84 936 22 0 0 0
chapter08_xml-parser 96% 1 4 70 1 0 0 0
chapter08_xz 96% 3 10 141 1 0 0 0
chapter08_zlib 85% 4 14 170 2 1 0 0
chapter08_zstd 81% 7 51 447 4 1 0 0
chapter09_bootscripts 92% 7 125 1,027 1 0 0 0
chapter09_chapter09 50% 1 1 14 1 0 0 0
chapter09_clock 96% 1 25 165 0 0 0 0
chapter09_consoled 93% 2 78 692 0 1 0 0
chapter09_etcshells 0 0 0 0 0 0 0
chapter09_inputrc 85% 1 126 928 0 0 0 0
chapter09_introduction 60% 6 248 1,563 0 0 0 0
chapter09_introductiond 100% 0 0 0 0 10 0 0
chapter09_locale 93% 2 96 571 0 0 0 0
chapter09_network 83% 7 337 2,315 1 0 0 0
chapter09_networkd 85% 9 280 2,473 5 2 0 0
chapter09_profile 79% 6 278 2,017 1 2 0 0
chapter09_symlinks 58% 17 845 5,454 0 0 0 0
chapter09_systemd-custom 94% 3 65 554 0 2 0 0
chapter09_udev 66% 18 723 5,607 0 2 0 0
chapter09_usage 70% 30 1,929 14,044 2 3 0 0
chapter10_chapter10 50% 1 1 15 1 0 0 0
chapter10_fstab 93% 1 76 962 0 1 0 0
chapter10_grub 62% 11 701 5,695 5 4 0 0
chapter10_introduction 0 0 0 0 0 0 0
chapter10_kernel 67% 32 804 5,704 17 3 0 0
chapter10_kernel_highmem 0% 2 18 280 2 0 0 0
chapter10_kernel_nvme 0% 2 18 266 2 0 0 0
chapter10_kernel_systemd 0% 2 292 4,159 2 0 0 0
chapter10_kernel_sysv 0% 2 193 2,641 2 0 0 0
chapter10_kernel_x2apic 0% 2 47 736 2 0 0 0
chapter11_afterlfs 0% 24 987 7,407 24 0 0 0
chapter11_chapter11 50% 1 1 15 1 0 0 0
chapter11_getcounted 0 0 0 0 0 0 0
chapter11_reboot 57% 12 201 1,429 5 4 0 0
chapter11_theend 92% 1 15 108 0 1 0 0
chapter11_whatnow 60% 6 82 611 5 0 0 0
index CC-BY-NC-2.0 0 0 0 0 0 0 0
Glossary Linux From Scratch 12.0 CC-BY-NC-2.0 0 0 0 0 0 0 0
part3intro_generalinstructions 54% 11 279 1,826 4 1 0 0
part3intro_introduction 25% 3 177 1,118 0 0 0 0
part3intro_part3intro 0 0 0 0 0 0 0
part3intro_toolchaintechnotes 32% 44 2,211 14,748 9 14 0 0
prologue_architecture 33% 4 309 1,851 0 1 0 0
prologue_audience 37% 5 299 1,780 0 1 0 0
prologue_bookinfo 0 0 0 0 0 0 0

Overview

Project website www.linuxfromscratch.org
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
an hour ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 8,952 85,476 719,763
Translated 78% 7,016 51% 44,186 53% 387,037
Needs editing 13% 1,188 32% 27,875 30% 220,744
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 285 9% 7,790 9% 69,990
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 8% 748 15% 13,415 15% 111,982
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 0 changes 0 changes 0 changes 0 changes 0 changes 10,520 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

85,476
Hosted words
8,952
Hosted strings
78%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

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

Resource updated
File “lfs/zh_CN/part3intro/toolchaintechnotes.po” was added. a year ago
User avatar None

String updated in the repository
Upon entering the chroot environment in <xref linkend="chapter-chroot-temporary-tools"/>, the temporary installations of programs needed for the proper operation of the toolchain are performed. From this point onwards, the core toolchain is self-contained and self-hosted. In <xref linkend="chapter-building-system"/>, final versions of all the packages needed for a fully functional system are built, tested, and installed.
在<xref linkend="chapter-chroot-temporary-tools"/>中，进入 chroot 环境后，首先安装 libstdc++。之后临时性地安装工具链的正常工作所必须的程序。还要构建测试其他程序时必须的程序。此后，核心工具链成为自包含的本地工具链。在<xref linkend="chapter-building-system"/>中，构建、测试并最后一次安装所有软件包，它们组成功能完整的系统。
a year ago
User avatar None

Source string changed
Upon entering the chroot environment in <xref linkend="chapter-chroot-temporary-tools"/>, the first task is to install libstdc++. Then temporary installations of programs needed for the proper operation of the toolchain are performed. Programs needed for testing other programs are also built. From this point onwards, the core toolchain is self-contained and self-hosted. In <xref linkend="chapter-building-system"/>, final versions of all the packages needed for a fully functional system are built, tested, and installed.
a year ago
User avatar None

String updated in the repository
At the end of <xref linkend="chapter-temporary-tools"/> the native LFS compiler is installed. First binutils-pass2 is built, in the same <envar>DESTDIR</envar> directory as the other programs, then the second pass of gcc is constructed, omitting some non-critical libraries. Due to some weird logic in gcc's configure script, <envar>CC_FOR_TARGET</envar> ends up as <command>cc</command> when the host is the same as the target, but different from the build system. This is why <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is declared explicitly as one of the configuration options.
在<xref linkend="chapter-temporary-tools"/>一节的末尾，构建 lfs 本地编译器。首先使用和其他程序相同的 <envar>DESTDIR</envar> 第二次构建 binutils，然后第二次构建 GCC，构建时忽略 libstdc++ 和其他不重要的库。由于 GCC 配置脚本的一些奇怪逻辑，<envar>CC_FOR_TARGET</envar> 变量在 host 系统和 target 相同，但与 build 不同时，被设定为 <command>cc</command>。因此我们必须显式地在配置选项中指定 <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter>。
a year ago
User avatar None

Source string changed
At the end of <xref linkend="chapter-temporary-tools"/> the native lfsLFS compiler is installed. First binutils-pass2 is built, within the same <envar>DESTDIR</envar> installdirectory as the other programs, then the second pass of GCCgcc is constructed, omitting libstdc++ and other non-importantsome non-critical libraries. Due to some weird logic in GCCgcc's configure script, <envar>CC_FOR_TARGET</envar> ends up as <command>cc</command> when the host is the same as the target, but is different from the build system. This is why <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is putdeclared explicitly intoas one of the configureation options.
a year ago
User avatar None

String updated in the repository
As mentioned above, the standard C++ library is compiled next, followed in <xref linkend="chapter-temporary-tools"/> by other programs that must be cross-compiled to break circular dependencies at build time. The install step of all those packages uses the <envar>DESTDIR</envar> variable to force installation in the LFS filesystem.
正如前文所述，接下来构建 C++ 标准库，然后是<xref linkend="chapter-temporary-tools"/>中那些需要自身才能构建的程序后。在安装这些软件包时使用 <envar>DESTDIR</envar> 变量，将它安装到 LFS 文件系统中。
a year ago
User avatar None

Source string changed
As saimentioned above, the standard C++ library is compiled next, followed in <xref linkend="chapter-temporary-tools"/> by all other programs that need themselves to be built.must be cross-compiled to break circular dependencies at build time. The install step of all those packages uses the <envar>DESTDIR</envar> variable to have the programs landforce installation into the LFS filesystem.
a year ago
User avatar None

String updated in the repository
Next comes glibc. The most important considerations for building glibc are the compiler, binary tools, and kernel headers. The compiler is generally not an issue since glibc will always use the compiler relating to the <parameter>--host</parameter> parameter passed to its configure script; e.g., in our case, the compiler will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel headers can be a bit more complicated. Therefore, we take no risks and use the available configure switches to enforce the correct selections. After the run of <command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">build</filename> directory for all important details. Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with <envar>$LFS_TGT</envar> expanded) to control which binary tools are used and the use of the <parameter>-nostdinc</parameter> and <parameter>-isystem</parameter> flags to control the compiler's include search path. These items highlight an important aspect of the glibc package&mdash;it is very self-sufficient in terms of its build machinery, and generally does not rely on toolchain defaults.
下一步安装 Glibc。在构建 Glibc 时需要着重考虑编译器，二进制工具，以及内核头文件。编译器一般不成问题，Glibc 总是使用传递给配置脚本的 <parameter>--host</parameter> 参数相关的编译器。例如，在我们的例子中，使用的编译器是 <command>$LFS_TGT-gcc</command>。但二进制工具和内核头文件的问题比较复杂。安全起见，我们使用配置脚本提供的开关，保证正确的选择。在 <command>configure</command> 脚本运行完成后，可以检查 <filename>build</filename> 目录中的 <filename>config.make</filename> 文件，了解全部重要的细节。注意参数 <parameter>CC="$LFS_TGT-gcc"</parameter> (其中 <envar>$LFS_TGT</envar> 会被展开) 控制构建系统使用正确的二进制工具，而参数 <parameter>-nostdinc</parameter> 和 <parameter>-isystem</parameter> 控制编译器的包含文件搜索路径。这些事项凸显了 Glibc 软件包的一个重要性质 —— 它的构建机制是相当自给自足的，通常不依赖于工具链默认值。
a year ago
User avatar None

Source string changed
The next package installed is GNext comes glibc. The most important considerations for building Gglibc are the compiler, binary tools, and kernel headers. The compiler is generally not an issue since Gglibc will always use the compiler relating to the <parameter>--host</parameter> parameter passed to its configure script; e.g., in our case, the compiler will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel headers can be a bit more complicated. Therefore, we take no risks and use the available configure switches to enforce the correct selections. After the run of <command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">build</filename> directory for all important details. Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with <envar>$LFS_TGT</envar> expanded) to control which binary tools are used and the use of the <parameter>-nostdinc</parameter> and <parameter>-isystem</parameter> flags to control the compiler's include search path. These items highlight an important aspect of the Gglibc package&mdash;it is very self-sufficient in terms of its build machinery, and generally does not rely on toolchain defaults.
a year ago
Browse all changes for this language