Proposal: ditch pre-made "console" and "network" scripts

Alexander E. Patrakov patrakov at ums.usu.ru
Wed Jan 5 21:09:33 PST 2005


Steve Crosby wrote:

> hmm...
> 
> Currently internationalisation (known as i18n) is not supported in LFS,
> due to the complex nature of the necessary infrastructure. Some pointers
> to documentation on cofiguring i18n are shown above, and your host
> distribution may have some configuration information you can copy.
> 
> Please note that the LFS support forums have limited resources to assist
> you with i18n questions, and as such you should have already exhausted
> all other support forums and read the appropriate documentation before
> approaching them with questions.

Could you please reword that? "s/not supported/???/", "s/due to.*
infrastructure/???/"

Programs are generally expected to "just work" in 8-bit LeftToRight
non-Turkish locales, that's the upstream fact since year 2000. But, in LFS,
the editors of course can't test correctness, and therefore can provide
instructions that break the program (e.g. that happened with xorg on early
versions of the bootcd) - but that's called "silent miscompilation" and
would be, as any other miscompilation, a bug in LFS.

Non-support for UTF-8 is not a bug in LFS because not all upstream packages
support UTF-8, and some packages in their UTF-8 support rely upon
RedHat-patched programs that don't support UTF-8 out of the box.

-- 
Alexander E. Patrakov



More information about the lfs-dev mailing list