Peter wrote:
Perhaps use a path like CLFS? They provide a framework
for multiple build scenarios. It could be a way forward
that LFS could also take e.g.
1. 7 bit ASCII
2. 8 bit locales
No actual difference between (1) and (2), except setting the locale to
"C" or to something else. See LFS-6.1 and 6.0, which implemented (2).
Compare to 5.1, which implemented (1). Or even better, see my early
8-bit i18n patch in the archive:
http://archives.linuxfromscratch.org/mail-archives/lfs-dev/2004-March/043145.html
http://archives.linuxfromscratch.org/mail-archives/lfs-dev/2004-March/043146.html
http://archives.linuxfromscratch.org/mail-archives/lfs-dev/2004-April/044800.html
As you see, the 8-bit-only patch is very small, and amounts to:
1) Writing the proper "console" script
2) Setting locale
3) Using the /etc/inputrc file
4) Textual notes
3. UTF-8
4. Asian languages with SCIM or other.
Again, no big difference between (3) and (4). SCIM is already in BLFS
Wiki: http://wiki.linuxfromscratch.org/blfs/wiki/InputMethods (and in
fact someone should include it into the book)
BTW, in order to stop feeling like a n00b in i18n, you can take this
challenge: build SKIM (a Qt-based equivalent of SCIM), and test it in
Japanese or UTF-8 based locale with the same "Ctrl+Space gakkou Space
Enter Ctrl+Space" => "学校" (school) test. If it works and passes the
test, append the instructions to the Wiki or post them to the list.
etc. or edit to suit
The CLFS approach does not require that all editors
understand all architectures - they may not have the
platform to test on.
This may be a way to attract more i18n support.
I personally feel your work (mainly) for i18n is too
valuable to drop or dumb down.
Unfortunately, i18n must be a property of the entire system, not a base
LFS. Otherwise, the system is unusable. So while your "multiple books"
approach could certainly work for LFS, one must either fork BLFS
accordingly, or choose a book for BLFS to target and add a "this book is
completely unsupported" warning to other variants of LFS (the same
problem of "unable to continue" does exist with CLFS).
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
