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 growing. We agree with that. UTF-8 and US-ASCII are the only charsets that are supported in -current and in the upcoming OpenBSD 5.9, and there are no plans to support any other charsets in the future. > Using UTF-8 in samba and ssh on a OpenBSD 4.9 i386 generic machine > that is about to retire You should have retired that machine three years ago. 4.9 went EOL on May 1, 2012. I have no idea why anything worked or did not work there. > works as expected, tested with swedish and icelandish > letters outside the 7bit ascii range. > > However, the new machine to replace the 4.9-box, running OpenBSD 5.6 That makes no sense. 5.6 is not new at all. It went EOL more than two months ago, on October 18, 2015. > on amd64 generic.mp #333, shows questionmarks when doing ls in ssh > (using PuTTY set to UTF-8 in translation). Yes, ls(1) replaces unknown characters by question marks when the locale(1) is set to something that is not supported. I'm no longer sure what 5.6 supported because it's too old. > The funny thing is that autocomplete using tab shows the expected > letters. pwd shows expected letters Yes, the shells do less sanitation than ls(1). > and even ls | cat shows correct letters. No sure what that does in 5.6. > Is this a known problem? > Is there a solution to make ls print correct UTF-8? 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
