|
发表于 2010-6-3 15:33:48
|
显示全部楼层
我的一些翻译异议
我会持续把自己的一些翻译上的异议提交在这个回帖中供译者参考。
1、 http://www.linuxfromscratch.org/ ... ogue/standards.html
the user has complete control over what packages are desired(用户可以完全控制想要安装的软件包)
2、 http://www.linuxfromscratch.org/ ... ackage-choices.html
Iana-etc It is needed to enable proper networking capabilities(启用正确的网络功能需要它).
3、 http://www.linuxfromscratch.org/ ... atingpartition.html
/usr/src – This partition is very useful for providing a location to store BLFS source files and share them across LFS builds.(参考的中文译文译者认为是保存LFS源码,我认为就是本意的BLFS 源码,因为LFS源码不多,没有必要用几十个G的空间来保存源码)
4、 http://www.linuxfromscratch.org/ ... er04/aboutsbus.html
Analyzing the output of the build process will also be more difficult because the lines of different processes will be interleaved. (因为不同进程的编译输出行将相互交错,所以分析编译过程的输出也将更加困难。注:我也拿不准的 :-( )
5、http://www.linuxfromscratch.org/ ... alinstructions.html
Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. (因此,不要在意似乎缺失了针对一个下载了的补丁的指令。)
6、 http://www.linuxfromscratch.org/ ... /linux-headers.html
The Linux API Headers expose the kernel's API for use by Glibc. (Linux API Headers 提供内核的 API 给 Glibc 使用。)
7、 http://www.linuxfromscratch.org/ ... binutils-pass1.html
In order for the SBU values listed in the rest of the book to be of any use, measure the time it takes to build this package from the configuration, up to and including the first install.( 为了这本书余下部分列出的 SBU 值有用,测量从配置直到并包括第一次安装所用的编译这个软件包的时间。 )
8、 http://www.linuxfromscratch.org/ ... pter05/ncurses.html
The Ncurses package contains libraries for terminal-independent handling of character screens. ( Ncurses 程序包提供与终端无关的字符屏幕处理库。 )
9、 http://www.linuxfromscratch.org/ ... 6/introduction.html
For the same reason, do not compile packages in parallel. Compiling in parallel may save time (especially on dual-CPU machines),(同样的原因,不要同时编译多个软件包。多个软件包同时编译可能节约时间(尤其是在双CPU机器上),)注:因为与“4.5. About SBUs”中的“parallel make"有可能混淆,所以加了“多个软件包”几个字,以示区别。
10、 http://www.linuxfromscratch.org/lfs/view/6.6/chapter06/vim.html
By default, vim runs in vi-incompatible mode.
在默认情况下,vim是以与 vi 不兼容的模式运行。
11、 http://www.linuxfromscratch.org/lfs/view/6.6/chapter06/vim.html
The set nocompatible setting makes vim behave in a more useful way (the default) than the vi-compatible manner. Remove the “no” to keep the old vi behavior.
set nocompatible将使 vim 默认以比 vi 兼容模式功能更强的方式运行。你可以去掉“no” 来保持旧的 vi 模式 。
12、http://www.linuxfromscratch.org/ ... pter07/profile.html
The “C” (default) and “en_US” (the recommended one for United States English users) locales are different. “C” uses the US-ASCII 7-bit character set, and treats bytes with the high bit set as invalid characters. That's why, e.g., the ls command substitutes them with question marks in that locale. Also, an attempt to send mail with such characters from Mutt or Pine results in non-RFC-conforming messages being sent (the charset in the outgoing mail is indicated as “unknown 8-bit”). So you can use the “C” locale only if you are sure that you will never need 8-bit characters.
“C“(默认) 和 “en_US“(推荐美国英语用户使用) locale 是不同的。“C” 使用 US-ASCII 7-bit 字符集,把含有高位的字节视为无效字符。这就是像 ls 命令在那种 locale 里面用问号代替它们的原因。而且,试图从 Mutt 或者 Pine 发送这种字符集的邮件会导致发送不符合 RFC 规范的信息(发出邮件的字符集被标示为"unknown 8-bit")。所以,只有你确定你永远不需要 8-bit 字符才可以使用 “C“ locale。 |
|