From 3809f0163bd0db9ad9e209b39a636f7e49a6f56b Mon Sep 17 00:00:00 2001 From: Colin Watson Date: Wed, 13 Nov 2013 02:08:50 +0000 Subject: [PATCH] * docs/grub.texi (Internationalisation, Supported kernels): Fix sectioning. --- ChangeLog | 5 +++++ docs/grub.texi | 18 ++++++++++-------- 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/ChangeLog b/ChangeLog index 804e721c3..22b20d280 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2013-11-13 Colin Watson + + * docs/grub.texi (Internationalisation, Supported kernels): Fix + sectioning. + 2013-11-13 Josh Triplett * grub-core/normal/term.c (grub_set_more): Use bool logic rather than diff --git a/docs/grub.texi b/docs/grub.texi index 8ef4e96af..0a9670f5b 100644 --- a/docs/grub.texi +++ b/docs/grub.texi @@ -5205,12 +5205,14 @@ is given, use default list of servers. @node Internationalisation -@chapter Charset +@chapter Internationalisation + +@section Charset GRUB uses UTF-8 internally other than in rendering where some GRUB-specific appropriate representation is used. All text files (including config) are assumed to be encoded in UTF-8. -@chapter Filesystems +@section Filesystems NTFS, JFS, UDF, HFS+, exFAT, long filenames in FAT, Joliet part of ISO9660 are treated as UTF-16 as per specification. AFS and BFS are read as UTF-8, again according to specification. BtrFS, cpio, tar, squash4, minix, @@ -5244,7 +5246,7 @@ treated as distinct from u+combining diaresis. This however means that in order to access file on HFS+ its name must be specified in normalisation form D. On normalized ZFS subvolumes filenames out of normalisation are inaccessible. -@chapter Output terminal +@section Output terminal Firmware output console ``console'' on ARC and IEEE1275 are limited to ASCII. BIOS firmware console and VGA text are limited to ASCII and some pseudographics. @@ -5278,7 +5280,7 @@ called ``annotation characters'' If you can complete either of two lists or, better, propose a patch to improve rendering, please contact developer team. -@chapter Input terminal +@section Input terminal Firmware console on BIOS, IEEE1275 and ARC doesn't allow you to enter non-ASCII characters. EFI specification allows for such but author is unaware of any actual implementations. Serial input is currently limited for latin1 (unlikely @@ -5288,15 +5290,15 @@ So no dead keys or advanced input method. Also there is no keymap change hotkey. In practice it makes difficult to enter any text using non-Latin alphabet. Moreover all current input consumers are limited to ASCII. -@chapter Gettext +@section Gettext GRUB supports being translated. For this you need to have language *.mo files in $prefix/locale, load gettext module and set ``lang'' variable. -@chapter Regexp +@section Regexp Regexps work on unicode characters, however no attempt at checking cannonical equivalence has been made. Moreover the classes like [:alpha:] match only ASCII subset. -@chapter Other +@section Other Currently GRUB always uses YEAR-MONTH-DAY HOUR:MINUTE:SECOND [WEEKDAY] 24-hour datetime format but weekdays are translated. GRUB always uses the decimal number format with [0-9] as digits and . as @@ -5766,7 +5768,7 @@ X86 support is summarised in the following table. ``Yes'' means that the kernel PowerPC, IA64 and Sparc64 ports support only Linux. MIPS port supports Linux and multiboot2. -@chapter Boot tests +@section Boot tests As you have seen in previous chapter the support matrix is pretty big and some of the configurations are only rarely used. To ensure the quality bootchecks are available for all x86 targets except EFI chainloader, Appleloader and XNU. All x86 platforms have bootcheck facility except ieee1275. Multiboot, multiboot2, BIOS chainloader, ntldr and freebsd-bootloader boot targets are tested only with a fake kernel images. Only Linux is tested among the payloads using Linux protocols.