<div dir="ltr">Hi Ryan,<div><br></div><div>I agree that it "should" not be a problem, but it actually crashed both 'port search' and 'svn diff' commands for me which seemed like a pretty significant problem. Also that character renders in various different ways (for cat, emacs, etc.), mostly erroneous, so it fails in the goal of communication if you get <span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">Ã or ? instead of the desired character.</span><div>
<span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">David</span></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Jun 21, 2014 at 7:12 PM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
On Jun 19, 2014, at 9:51 PM, <a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a> wrote:<br>
<br>
> czmq, crossroads, py-zmq: changed references to 0MQ that used the O with slash special character. This was displayed as à in commands such as 'port search' and indeed crashed the command so that no further output would be shown after it (at least on my machines). Same happened for 'svn diff' even for this commit. By contrast, in other places this library is referred to as 0MQ or ZeroMQ, which does not cause such problems.<br>
<br>
</div>Use of non-ASCII characters in portfiles should not be a problem. Portfiles are defined as being UTF-8 files and they display fine for me as such in the terminal. Many other ports use UTF-8 characters, such as smart quotes, and I don't think we should attempt to go back to using ASCII only because it's just so limiting.<br>
<br>
<br>
<br>
</blockquote></div><br></div>