<div dir="ltr"><div><div><div>Given its use in "filename.ext" names, dot pretty much must be included in any list of file name characters.<br></div>It isn't used in any current distribution zone names, and its presence might cause Windows shenanigans by making it look as if a name has an extension.<br>
</div>Since we're in warning land, I'll advocate for warning about any dots in file names;<br></div><div>this eliminates the need for more specific testing.<br></div><div><br></div> --ado<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Jun 26, 2014 at 3:58 AM, Andreas Schwab <span dir="ltr"><<a href="mailto:schwab@suse.de" target="_blank">schwab@suse.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="">Tim Parenti <<a href="mailto:tim@timtimeonline.com">tim@timtimeonline.com</a>> writes:<br>
<br>
> If you allow dot, you'll want to add checks that "." and ".." are not used<br>
> as file name components.<br>
<br>
</div>And it shouldn't start with a dot.<br>
<span class="HOEnZb"><font color="#888888"><br>
Andreas.<br>
<br>
--<br>
Andreas Schwab, SUSE Labs, <a href="mailto:schwab@suse.de">schwab@suse.de</a><br>
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7<br>
"And now for something completely different."<br>
</font></span></blockquote></div><br></div>