Changeset b32e803


Ignore:
Timestamp:
05/06/2004 04:22:04 PM (20 years ago)
Author:
Zack Winkles <winkie@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
32220fb
Parents:
4dc8dc6
Message:

Committed Alexander's i18n patch

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3489 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
2 added
7 edited

Legend:

Unmodified
Added
Removed

  • chapter06/glibc.xml

    r4dc8dc6 rb32e803  
    112112localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen>
    113113
     114<para>In fact, some locales installed by the
     115<command>make localedata/install-locales</command>
     116command above are not properly
     117supported by some applications that are in LFS and BLFS books. Because
     118of various problems that arise
     119due to application programmers making
     120assumptions that break in such locales, LFS <emphasis>should not</emphasis>
     121be used in locales that utilize
     122multibyte character sets (including UTF-8) or
     123right-to-left writing order.
     124Numerous unofficial and unstable patches are required to fix these problems,
     125and it has been decided not to support such complex locales.
     126This applies to the ja_JP and fa_IR locales as well:
     127they have been installed only
     128for gcc and gettext tests to pass, and e.g. <application>vim</application>
     129compiled according to this book doesn't work properly in them.
     130Various attempts to circumvent these
     131restrictions are documented in internationalization-related hints.</para>
     132
    114133<para>Finally, build the linuxthreads man pages, which are a great reference
    115134on the threading API (applicable to NPTL as well):</para>

  • chapter06/kbd.xml

    r4dc8dc6 rb32e803  
    3737</sect2>
    3838
    39 <sect2 id="conf-kbd"><title>Configuring your keyboard</title>
    40 <indexterm zone="conf-kbd">
    41 <primary sortas="a-Kbd">Kbd</primary>
    42 <secondary>configuring</secondary></indexterm>
    43 
    44 <para>Few things are more annoying than using Linux while a wrong keymap
    45 for your keyboard is loaded. If you have a standard US keyboard, however, you
    46 can skip this section, as the US keymap is the default as long as you don't
    47 change it.</para>
    48 
    49 <para>To change the default keymap, create the
    50 <filename class="symlink">/usr/share/kbd/keymaps/defkeymap.map.gz</filename>
    51 symlink by running the following command:</para>
    52 
    53 <screen><userinput>ln -s path/to/keymap /usr/share/kbd/keymaps/defkeymap.map.gz</userinput></screen>
    54 
    55 <para>Of course, replace <filename>path/to/keymap</filename> with the path and
    56 name of your keyboard's map file. For example, if you have a Dutch keyboard,
    57 you would use <filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
    58 
    59 <para>Another way to set your keyboard's layout is to compile the keymap
    60 into the kernel. This ensures that your keyboard will always work as expected,
    61 even when you boot into maintenance mode (by passing `init=/bin/sh' to the
    62 kernel), as then the bootscript that normally sets up your keymap isn't run.</para>
    63 
    64 <para>When in <xref linkend="chapter-bootable"/> you're ready to compile the
    65 kernel, run the following command to patch the current default keymap into the
    66 source (you will have to repeat this command whenever you unpack a new
    67 kernel):</para>
    68 
    69 <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/defkeymap.map.gz &gt; \
    70     /usr/src/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen>
    71 
    72 </sect2>
    73 
     39<!-- The "Configuring your keyboard" section has been moved to
     40Chapter 7 and renamed to "Configuring Linux console" -->
    7441
    7542<sect2 id="contents-kbd"><title>Contents of Kbd</title>
    … …  
    164131<indexterm zone="ch-system-kbd unicode_start"><primary sortas="b-unicode_start">unicode_start</primary></indexterm>
    165132<para id="unicode_start"><command>unicode_start</command> puts the keyboard and console in
    166 unicode mode.</para>
     133UNICODE mode. Never use it on LFS, because applications are not
     134configured to support UNICODE.</para>
    167135
    168136<indexterm zone="ch-system-kbd unicode_stop"><primary sortas="b-unicode_stop">unicode_stop</primary></indexterm>
    169137<para id="unicode_stop"><command>unicode_stop</command> reverts keyboard and console from
    170 unicode mode.</para>
     138UNICODE mode.</para>
    171139
    172140</sect2>

  • chapter06/man.xml

    r4dc8dc6 rb32e803  
    7474to NROFF.</para></note>
    7575
     76<para>If your character set uses 8-bit characters, search for the line
     77beginning with "NROFF" in /etc/man.conf, and verify that it coincides
     78with the following:</para>
     79
     80<screen>NROFF  /usr/bin/nroff -Tlatin1 -mandoc</screen>
     81
     82<para>Note that you should use "latin1" even if it is not the character set
     83of your locale. The reason is that,
     84according to the specification, <application>groff</application> has
     85no means of typesetting characters outside ISO-8859-1
     86without some strange escape codes, and localized manual
     87pages are therefore really a hack. When formatting manual pages,
     88<application>groff</application> thinks that they are in the ISO-8859-1
     89encoding and this <emphasis>-Tlatin1</emphasis> switch tells
     90<application>groff</application> to use the same encoding for output.
     91Since <application>groff</application> does no recoding of input characters,
     92the formatted result is really in the same encoding as input (although
     93<application>groff</application> doesn't know that it is not ISO-8859-1)
     94and therefore it is usable as the input for a pager.</para>
     95
     96<para>Of course, this hack does not solve the problem of non-working
     97<command>man2dvi</command> program for localized manual
     98pages in non-ISO-8859-1 locales.
     99Also, it does not work at all with multibyte character sets.
     100The first problem does not have a solution currently. The second
     101one is not of a concern because the LFS installation does not support
     102multibyte character sets properly anyway. You may want to look at
     103internationalization related hints, though.</para>
     104
    76105<para>You may want to also take a look at the BLFS page at
    77106<ulink url="&blfs-root;view/cvs/postlfs/compressdoc.html"/> which deals with

  • chapter06/sysvinit.xml

    r4dc8dc6 rb32e803  
    7575su:S016:once:/sbin/sulogin
    7676
    77 1:2345:respawn:/sbin/agetty tty1 9600
    78 2:2345:respawn:/sbin/agetty tty2 9600
    79 3:2345:respawn:/sbin/agetty tty3 9600
    80 4:2345:respawn:/sbin/agetty tty4 9600
    81 5:2345:respawn:/sbin/agetty tty5 9600
    82 6:2345:respawn:/sbin/agetty tty6 9600
     771:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600
     782:2345:respawn:/sbin/agetty -I '\033(K' tty2 9600
     793:2345:respawn:/sbin/agetty -I '\033(K' tty3 9600
     804:2345:respawn:/sbin/agetty -I '\033(K' tty4 9600
     815:2345:respawn:/sbin/agetty -I '\033(K' tty5 9600
     826:2345:respawn:/sbin/agetty -I '\033(K' tty6 9600
    8383
    8484# End /etc/inittab
    8585<userinput>EOF</userinput></screen>
     86
     87<para> The -I '\033(K' switch tells agetty to send this escape sequence to
     88the terminal before doing anything else. This escape sequence switches the
     89console character set to a user-defined one, which can be modified by
     90running the <command>setfont</command> program.
     91Actually, the <command>console</command> initscript from the LFS-Bootscripts
     92package calls the <command>setfont</command> program during system
     93startup. Sending this escape sequence is necessary for
     94people who use non-ISO-8859-1 screen font, but does not hurt native English
     95speakers.</para>
    8696
    8797</sect2>

  • chapter07/bootscripts.xml

    r4dc8dc6 rb32e803  
    3131<sect2 id="contents-bootscripts"><title>Contents of LFS-bootscripts</title>
    3232
    33 <para><emphasis>Installed scripts</emphasis>: checkfs, cleanfs, functions,
    34 halt, ifdown, ifup, loadkeys, localnet, mountfs, mountkernfs, network, rc,
     33<para><emphasis>Installed scripts</emphasis>: checkfs, cleanfs,
     34console,
     35functions, halt, ifdown, ifup,
     36localnet, mountfs, mountkernfs, network, rc,
    3537reboot, sendsignals, setclock, static, swap, sysklogd and template</para>
    3638
    … …  
    5254<filename>/fastboot</filename> and <filename>/forcefsck</filename> files.</para>
    5355
     56<indexterm zone="ch-scripts-bootscripts console-bootscripts"><primary sortas="d-console">console</primary></indexterm>
     57<para id="console-bootscripts">The <command>console</command> script
     58loads the keymap table you
     59specified as proper for your keyboard layout.
     60It also sets the screen font.</para>
     61
    5462<indexterm zone="ch-scripts-bootscripts functions-bootscripts"><primary sortas="d-functions">functions</primary></indexterm>
    5563<para id="functions-bootscripts">The <command>functions</command> script contains functions shared among
    … …  
    6270<para id="ifdown-bootscripts">The <command>ifdown</command> and <command>ifup</command> scripts assist
    6371the network script with network devices.</para>
    64 
    65 <indexterm zone="ch-scripts-bootscripts loadkeys-bootscripts"><primary sortas="d-loadkeys">loadkeys</primary></indexterm>
    66 <para id="loadkeys-bootscripts">The <command>loadkeys</command> script loads the keymap table you
    67 specified as proper for your keyboard layout.</para>
    6872
    6973<indexterm zone="ch-scripts-bootscripts localnet-bootscripts"><primary sortas="d-localnet">localnet</primary></indexterm>

  • chapter07/chapter07.xml

    r4dc8dc6 rb32e803  
    1414<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="setclock.xml"/>
    1515<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="console.xml"/>
     16<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="inputrc.xml"/>
     17<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="profile.xml"/>
    1618<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="sysklogd.xml"/>
    1719<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="hostname.xml"/>

  • chapter07/console.xml

    r4dc8dc6 rb32e803  
    55]>
    66<sect1 id="ch-scripts-console">
    7 <title>Do I need the console script?</title>
     7<title>Configuring the Linux console</title>
    88<?dbhtml filename="console.html"?>
    99
    … …  
    1212<secondary>configuring</secondary></indexterm>
    1313
    14 <para>If you plan to compile the keymap directly in the kernel during <xref
    15 linkend="chapter-bootable"/> (see <xref linkend="ch-system-kbd"/>), then strictly
    16 speaking you don't need to run this loadkeys script, since the kernel will set
    17 up the keymap for you. If you wish, you can still run the script, it isn't going
    18 to hurt you. Keeping it could even be beneficial, in case you run a lot of
    19 different kernels and can't be sure that the keymap is compiled into every one
    20 of them.</para>
     14<para>In this section we will configure the <command>console</command>
     15initscript that sets up the keyboard
     16map and the console font. If you are a native English speaker so that you
     17don't need to use any non-ASCII characters, and your keyboard is a US one,
     18skip this section. Without the configuration file,
     19the <command>console</command> initscript will do nothing.</para>
    2120
    22 <para>If you decided you don't need or don't want to use the console script,
    23 remove the <filename class="symlink">/etc/rc.d/rcsysinit.d/S70console</filename> symlink.</para>
     21<para>The <command>console</command> script uses the
     22<filename>/etc/sysconfig/console</filename>
     23as a configuration file. You need to decide which keymap and screen font you
     24will use. The language-specific HOWTO can help you.
     25In the future releases of LFS-Bootscripts, there will be a pre-made
     26<filename>/etc/sysconfig/console</filename> file with known
     27good settings for several countries, and you will just have to uncomment
     28the relevant section.
     29If still in doubt,
     30look into <filename class="directory">/usr/share/kbd</filename>
     31for valid keymaps and screen fonts. Then read the <command>loadkeys</command>
     32and <command>setfont</command> manual pages and figure out the correct
     33arguments for these programs.
     34Once you decided, create the
     35configuration file with the following command:</para>
     36
     37<screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"</userinput>
     38KEYMAP="<emphasis>arguments for loadkeys</emphasis>"
     39FONT="<emphasis>arguments for setfont</emphasis>"
     40<userinput>EOF</userinput></screen>
     41
     42<para>E.g., for Spanish users who also want to use the Euro character
     43(accessible by pressing Alt+E),
     44the following settings are correct:</para>
     45
     46<screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"</userinput>
     47KEYMAP="es euro"
     48FONT="lat9-16 -u iso01"
     49<userinput>EOF</userinput></screen>
     50
     51<para>If the KEYMAP or FONT variable is not set, the console initscript
     52will not run the corresponding program.</para>
     53
     54<para>In some keymaps, the Backspace and Delete keys send characters
     55different form ones in the default keymap built into the kernel.
     56This confuses some applications, e.g. <application>Emacs</application>
     57displays its help (instead of erasing the character before the cursor)
     58when you press Backspace. To check if your keymap is affected (this works
     59only for i386 keymaps):</para>
     60
     61<screen><userinput>zgrep '\W14\W' <emphasis>/path/to/your/keymap</emphasis></userinput></screen>
     62
     63<para>If you see that keycode 14 is Backspace and not Delete,
     64create the following keymap snippet to fix this issue:</para>
     65
     66<screen><userinput>mkdir -p /etc/kbd &amp; &amp; cat &gt;/etc/kbd/bs-sends-del &lt;&lt;"EOF"</userinput>
     67                keycode 14 =    Delete  Delete          Delete  Delete
     68        alt     keycode 14 =    Meta_Delete
     69altgr   alt     keycode 14 =    Meta_Delete
     70                keycode 111 =   Remove
     71altgr   control keycode 111 =   Boot
     72control alt     keycode 111 =   Boot
     73altgr   control alt keycode 111 = Boot
     74<userinput>EOF</userinput></screen>
     75
     76<para>Then tell the <command>console</command> script to load this snippet
     77after the main keymap:</para>
     78
     79<screen><userinput>cat &gt;&gt;/etc/sysconfig/console &lt;&lt;EOF</userinput>
     80KEYMAP_CORRECTION="/etc/kbd/bs-sends-del"
     81<userinput>EOF</userinput></screen>
     82
     83<para>If back in <xref linkend="chapter-building-system"/> you decided to go
     84compile your keymap directly into the kernel (later on in <xref
     85linkend="chapter-bootable"/>), then strictly speaking you don't need to run the
     86loadkeys program, since the kernel will set up the keymap for you,
     87and thus you may omit the KEYMAP variable from the
     88<filename>/etc/sysconfig/console</filename>
     89configuration file. If you wish,
     90you can still have it, this isn't going to hurt you. Keeping it could even
     91be beneficial, in case you run a lot of different kernels and can't be sure
     92that the keymap is compiled into every one of them.</para>
    2493
    2594</sect1>
     95
Note: See TracChangeset for help on using the changeset viewer.