<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="ltr"></div>
<div dir="ltr">I believe the plan is to have Windows and Visual C&#43;&#43; support useful UTF-8 pathnames. &nbsp;I can’t say anything about release dates, etc. But, please do keep Roy (in CC:) and myself informed of any related issues you run into.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">— Gaby</div>
<div dir="ltr"><br>
On Feb 26, 2019, at 3:30 AM, Steve Downey &lt;<a href="mailto:sdowney@gmail.com">sdowney@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm pretty sure compilation DB totally ignores this, and is easy to get invalid json in. Makefile syntax would care somewhat less.&nbsp;
<div><br>
</div>
<div>I don't think it would be the worst thing for these tools to require Unicode without any normalization. You have to be able to fopen, and that means an exact match. I don't know the state of the world for Windows for utf-8 vs ucs2. Can we reliably get
 the file open?&nbsp;</div>
<div><br>
</div>
<div>I think the TR can place more requirements than the IS can on file names.&nbsp;<br>
<div dir="auto"><br>
<div class="gmail_quote">
<div dir="ltr">On Tue, Feb 26, 2019, 04:50 Manuel Klimek &lt;<a href="mailto:klimek@google.com">klimek@google.com</a>&gt; wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Feb 26, 2019 at 4:01 AM Ben Boeckel &lt;<a href="mailto:ben.boeckel@kitware.com" target="_blank">ben.boeckel@kitware.com</a>&gt; wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Mon, Feb 25, 2019 at 09:52:34 &#43;0100, Manuel Klimek wrote:<br>
&gt; In the compilation database (<br>
&gt; <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclang.llvm.org%2Fdocs%2FJSONCompilationDatabase.html&amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488500443&amp;sdata=CorqQwp20HXVHjavBly%2Brq3gpElInvQDftma%2Fe%2BYnzI%3D&amp;reserved=0" originalsrc="https://clang.llvm.org/docs/JSONCompilationDatabase.html" shash="ZibV1XyPM1HAUBweKXdtC4yIK3U5Tld5p7h8Yf&#43;Vg&#43;hZ3UWofqJ&#43;s1dDyiVxTxs5VryoCSHrWD3H3npXdj0qNBRJzzS&#43;zGRmU&#43;AIhrpRWVGSFN&#43;TN/tEcHktR7XvpzdnOJy96ZTFnu1jzXofl0onL&#43;kdR&#43;w0cMuTueGV9slDoVc=" rel="noreferrer" target="_blank">
https://clang.llvm.org/docs/JSONCompilationDatabase.html</a>) we specify the<br>
&gt; build dir for each file.<br>
<br>
But that is (generally) output from the build system, not the compiler.<br>
The build system knows because…well, it does. The compiler is just<br>
invoked in a working directory and given no indication of where a &quot;root&quot;<br>
directory is (and I think it might be silly to pass it on the command<br>
line just to have it in this file, but maybe not).</blockquote>
<div><br>
</div>
<div>Can't the compiler put in the current work directory it's been called with?&nbsp; That's what I'd expect.</div>
</div>
</div>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.open-std.org%2Fmailman%2Flistinfo%2Ftooling&amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488510838&amp;sdata=DtIbuyEnipgahSMOZOOfQzhERDx9s%2FoOsXSRnqPUloc%3D&amp;reserved=0" originalsrc="http://www.open-std.org/mailman/listinfo/tooling" shash="l52aBHXAH0OzpcggrDsPgxxJnKwdvlNFibdwoSwIzojtADp5Cr3O&#43;DSfJzulxDW7RCgaT7GUEjSIdciEfga8UpK0VNKPuIHNtzUh1YRmiRmyi3EcaFIW0b2JODOkCs063SOVXARSn0ZBc4ZUj/fxLY3r222lmPRFw8iNhpoBuGA=" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>Modules mailing list</span><br>
<span><a href="mailto:Modules@lists.isocpp.org">Modules@lists.isocpp.org</a></span><br>
<span>Subscription: <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fmodules&amp;amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488520853&amp;amp;sdata=wDbeZoFkUTvGKDYVi9HowzdlN7LCuFQEZ8Cq9pX0dHE%3D&amp;amp;reserved=0">
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fmodules&amp;amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488520853&amp;amp;sdata=wDbeZoFkUTvGKDYVi9HowzdlN7LCuFQEZ8Cq9pX0dHE%3D&amp;amp;reserved=0</a></span><br>
<span>Link to this post: <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fmodules%2F2019%2F02%2F0105.php&amp;amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488530462&amp;amp;sdata=VugT4VetiLu1ndkQWi0hYv1lFXMDWxPPT67Ou%2FF6cCE%3D&amp;amp;reserved=0">
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fmodules%2F2019%2F02%2F0105.php&amp;amp;data=02%7C01%7Cgdr%40microsoft.com%7C1713ebab01f64789483f08d69bee9d5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636867846488530462&amp;amp;sdata=VugT4VetiLu1ndkQWi0hYv1lFXMDWxPPT67Ou%2FF6cCE%3D&amp;amp;reserved=0</a></span><br>
</div>
</blockquote>
</body>
</html>