On Sat, Jun 17, 2006 at 04:28:45PM +0900, TAKAHASHI Tamotsu wrote: > On 6/13/06, Zvezdan Petkovic <[EMAIL PROTECTED]> wrote: > >I believe we should at least recompile mutt port --without-wc-funcs to > >get a part of functionality back. Something else needs to be done to > >get all back the way it used to be. Any ideas? Suggestions? > > You are right. OpenBSD's locale implementation does not > support UTF-8 (nor Japanese).
OpenBSD works fine with UTF-8 despite not having support for locales. As already described in my previous message, Vim, XTerm, and KMail work just fine with these messages. It's a mutt port issue. > So, we have two ways to use UTF-8 on mutt: > (1) Use mutt's wc-funcs. i.e. build it with --without-wc-funcs. As shown in my examples this solves one big part of the problem. The message can be read correctly most of the time, and the subject in UTF-8 is accepted correctly. Can we get this into port? However, this still leaves an issue of a strange behaviour with mixed Latin (ASCII, probably) and non-Latin (non-ASCII) characters. Also, the input of subject line in UTF-8 used to be visible as you type it, as opposed to the current port where it looks mangled until Enter is pressed. This _worked_ in mutt before. I don't see why it doesn't any more. Perhaps something else should be declared --without-... Notice that the version of mutt did not change (except security patches) between the time when it worked and now. Thus, it's all in configuration of mutt. I'll continue to experiment with configuration options. I'd appreciate if other porters who are mutt users (I believe there are many) take a look at it and try. We might come up with something. > (2) Implement a full CITRUS, for example, > http://sigsegv.s25.xrea.com/distfiles/citrus/OpenBSD/ No, thank you. When it's officially in OpenBSD (I think Espie works on this), then it will be OK. Till then, I'd prefer fixing mutt port only. Best regards, Zvezdan Petkovic
