Hi Jon,
Jon S wrote on Wed, Jan 06, 2016 at 10:56:52AM +0100:
> In an attempt to get a better idea on how to make all non-ascii chars
> appear correctly in windows/samba, ssh and the local console I get the
> impression that UTF-8 is the charset that is mostly used in general and
> also most
Hello misc!
In an attempt to get a better idea on how to make all non-ascii chars
appear correctly in windows/samba, ssh and the local console I get the
impression that UTF-8 is the charset that is mostly used in general and
also most growing.
Using UTF-8 in samba and ssh on a OpenBSD 4.9 i386
On 2016-01-06 10.56.52 +0100, Jon S wrote:
> Is this a known problem? Is there a solution to make ls print correct UTF-8?
Use colorls from packages instead.
http://marc.info/?l=openbsd-misc=142539814225472=2
On 01/06/16 11:05, Mike Burns wrote:
On 2016-01-06 10.56.52 +0100, Jon S wrote:
Is this a known problem? Is there a solution to make ls print correct UTF-8?
Use colorls from packages instead.
http://marc.info/?l=openbsd-misc=142539814225472=2
Or wait for 5.9 to come out.
> Hello misc!
>
> In an attempt to get a better idea on how to make all non-ascii chars
> appear correctly in windows/samba, ssh and the local console I get the
> impression that UTF-8 is the charset that is mostly used in general
> and
> also most growing.
>
> Using UTF-8 in samba and ssh on a
> Use -current. I fixed ls(1) recently to correctly handle UTF-8.
> On May 1, 2016, upgrade to OpenBSD 5.9 if you want to use -stable.
> Do not forget to upgrade to OpenBSD 6.0 on November 1, 2016.
> UTF-8 support is likely to improve further between 5.9 and 6.0.
>
> Yours,
> Ingo
Thanks for
6 matches
Mail list logo