Motomichi Matsuzaki wrote:
>
> The 'mandatory + recommended' object size is no more than 5 kbytes.
> The GENERIC kernel does not require necessarily
> the euc-jp support or any other charsets.
> I think the iso8859-1 support alone is sufficient for GENERIC.
>
> The custom kernels can have the euc-jp support through
> the CHARSET_EUC_JP and ENCODING_EUC kernel configure option.
> (They are currently defined at the top of the source files.)
But are they set by default to include euc-jp? Well, that's a minor
point.
> Yes. sysctl is not the best idea.
>
> I think the charset preferences should apply on per-process basis ideally.
>
> The operator mounts some disks.
> The users access the disks in their own preferred charset.
>
> The UNICODE is a multiligual codeset,
> so we shoud not suppose any specific charset on the disk.
> Therefore, a per-mount basis is not enough.
>
> If the routines can refer the users' environment 'LC_CTYPE',
> it is fine idea. But it can't, I suppose.
Yeah, Terry Lambert has preached on this before. My point is that I
can't get the patch committed with it using a sysctl node.
--
Daniel C. Sobral (8-DCS)
d...@newsguy.com
d...@freebsd.org
"Well, Windows works, using a loose definition of 'works'..."
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
