Alexander E. Patrakov <patrakov <at> ums.usu.ru> writes: > > (sorry, today I am in a very bad mood. Bad moods happen :)
> > > You obviously didn't read the "35 patches and counting" thread. The > roadmap may or may not be to drop UTF-8 support completely to be > consistent with other parts of LFS project and with unpatched upstream I did read it - understanding is another issue! > Exactly people with native English viewpoint are the most active UTF-8 > supporters because they don't see bugs (and the bugs are avoidable by > using 8-bit locales like ru_RU.KOI8-R). This is my point. > From my viewpoint, the project > is dead exactly because of recent additions like Udev and UTF-8 support, > because only one or two editors understand the issues. To revive itself, > the project must drop my "featurism" and the book should be dumbed down > so that all editors understand all of it. > 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 3. UTF-8 4. Asian languages with SCIM or other. 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. Thanks, Peter -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
