<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 9/6/19 4:09 PM, Tony V E wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOHCbita=XCVevGpprHFKbXDzL2gU2jyBcOnHvobM1tmC1Fxtw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Fri, Sep 6, 2019 at 3:52
            PM Thiago Macieira &lt;<a href="mailto:thiago@macieira.org"
              moz-do-not-send="true">thiago@macieira.org</a>&gt; wrote:<br>
          </div>
          <div> <br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <br>
            &gt; Are there systems where filenames *that developers use*
            can't be found via<br>
            &gt; UTF8?<br>
            <br>
            The problem is what happens when the locale isn't UTF-8,
            which is common <br>
            enough when LC_ALL=C was set in the environment.<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>And how common is that (besides you :-)</div>
        </div>
      </div>
    </blockquote>
    <p>It is relatively common for me too.  I sometimes use it in
      scripts to maintain consistent output across systems with
      different locale settings.<br>
    </p>
    <p>Tom.</p>
  </body>
</html>