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