[121204] trunk/dports

[David Strubbe]

How does one make XQuartz's xterm support UTF-8?

David


On Sun, Jun 22, 2014 at 11:26 PM, Mihai Moldovan <ionic at ionic.de> wrote:

> * On 23.06.2014 02:12 am, Michael Dickens wrote:
> > That said, it's quite possible that I've messed up my xterm settings
> > somehow, which is causing the locking (me, and David apparently).  I
> > believe this has to do with how the xterm interprets the streamed
> > characters (sort of like setting LANG="C" to get SED to work), but since
> > it happens rarely with the ports I use regularly I've never really
> > investigated.
>
> Sarcasm by me aside, I'd really invite to you to try rxvt-unicode, if
> you're in
> need of an X11-based terminal. xterm is quite old, not so well maintained
> and
> lacks many features.
>
> If you're adding an item for urxvt in the X11 "Applications" menu, it's
> just as
> easily accessible as xterm. Not to mention faster and richer in features.
>
> Or is there any specific reason why GNU radio needs xterm I've been
> missing?
> (Certainly possible, I'm really just asking.)
>
>
> > I don't see this as a critical issue with MacPorts.  I was more agreeing
> > with David's comment that although using UTF-8, as Ryan wrote: "should
> > not be a problem", it can be a problem for some users -- including some
> > who are not average users; I hope I'm not considered just an average
> > user! - MLD
>
> No, you're not. I didn't mean to imply that. :)
> If stuff is breaking with UTF-8, it's better to handle/fix the baseline
> issue
> and be "future-proof", instead of limiting UTF-8 usage because of bugs.
> (And I'd
> rather see UTF-8 a "current" technology, than a "future" one.)
>
> I've even seen compilers and GNU tools spit out UTF-8 characters, like
> those
> "smart quotes" Ryan mentioned.
> xterm does have (maybe incomplete?) support for UTF-8, but it seems to be
> optional and may have to be turned of specifically. In any case, software
> seeing
> a UTF-8 locale has a "right" to make use of that, even if it means
> crashing xterm.
>
> In spite of that, maybe MacPorts should ship an
> ${prefix}/etc/X11/Xresources
> file enabling Unicode support by default? UTF-8 locales are the default on
> OS X
> anyway.
>
>
>
> Mihai
>
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140622/30522bdb/attachment.html>