Re: [Devil-linux-develop] Re: [Devil-linux-commit] build/scripts/config config_linux,1.66,1.67

[<hzu...@ra...>]

On 01/06/2004 09:58:31 AM Diego Torres wrote:
>On Tue, Jan 06, 2004 at 09:36:33AM -0500, hzu...@ra...
>wrote:
>
>> >CONFIG_NLS_DEFAULT="iso8859-15"
>> >CONFIG_NLS_CODEPAGE_437=m
>> >CONFIG_NLS_CODEPAGE_850=m
>> >CONFIG_NLS_ISO8859_1=m
>> >CONFIG_NLS_ISO8859_15=y
>> >CONFIG_NLS_UTF8=m
>
>> >that is, everything as modules, and only 8859-15 inside the kernel.
>> >heiko, if everything is ok for you, say something :)
>>
>> I thought UTF-8 is the new standard?
>
>yes, but after a lot of testing & reading i've changed my mind. with
>utf-8
>you have multibyte characters representation (>127), and for example
>midnightcommander is not ready. redhat has done a lot of work on
>improving that, and they have patched versions of mc, mutt, etc, but
>i don't like using them on dl. so lets clean things on 8859-15 (that
>supports everyone using devil-linux) and leave utf-8 for dl2.0 :)
>
>also samba provides "unix charset" so the utf-8 default can be changed.
>
>This are the best documents i've found about utf-8 and 8859-15 support.
>http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/howto.html
>http://www.debian.org/doc/manuals/debian-euro-support/ch-configure.en.ht
>ml

Doesn't look like we got much of a choice... ;-)

>> >more things: our glibc is updated?
>>
>> No, why?
>
>utf-8 needs the latests glibc available, i mean, latests glibc is needed
>to use utf-8 :)

We switch to the new glibc, once it comes out.

>> >CONFIG_CODA_FS=m
>> >
>> >i'll start doing some tests. the beauty of coda is that near
>everything
>> >is in userspace.
>>
>> That change you can do.
>
>but i don't promise anything, since there is no beer :)

The first step is getting the Kernel support up and running, then you can
get a beer and work on the rest.

Heiko