<div dir="ltr"><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_quote">On 14 January 2013 18:50, gunther Vermeir <span dir="ltr"><<a href="mailto:gunther.vermeir@gmail.com" target="_blank">gunther.vermeir@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">>> # History of legal time in Britain<br>
>> # <a href="http://student.cusu.cam.ac.uk/%7Ejsm28/british-time/" target="_blank">http://student.cusu.cam.ac.uk/~jsm28/british-time/</a>.<br>
><br>
> Well is that punctuation at the end of your URL part of the URL or<br>
> not? It's fairly obviously not in that case, but not always so. The<br>
> brackets help to delimit the URL.<br>
><br>
</div>Thunderbird seams to think it's not part :)<br>
It is for humans in any case, maybe simply "require" to have an URL<br>
always need to be surrounded with 2 spaces (U+0020) ?</blockquote></div><br></div>+1
on "comments are for humans"; unless and until we push the comments out
into standalone documents (which I don't see as likely), we don't particularly need to use any
markup in the official database for URLs.<br><br>Honestly, all but the shortest URLs are long
enough to be given their own line anyway, so why not just do that for all of them? It's
about as unambiguous as one can reasonably get while keeping things
simple for readability's sake, and you can name links (for those that
need names) by just putting the title followed by a colon (:) on the
previous line(s). Maybe indent the URL with a couple spaces for stylistic/parsing reasons, but nothing fancier than that.<br><br><div class="gmail_quote">On 14 January 2013 18:50, gunther Vermeir <span dir="ltr"><<a href="mailto:gunther.vermeir@gmail.com" target="_blank">gunther.vermeir@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id=":2hf">+1, also for UTF-8 (no BOM) in comments only without the HTML entities /<br>
tags etc etc and non-comment parts of the files to be restricted to<br>
plain-old ASCII until there is a compelling need.</div></blockquote></div><br>+1 on UTF-8 for comments, ASCII elsewhere; if
it's feasibly implementable. I'm not certain how one would actually go
about actually supporting that, but such an approach would allow each user to choose how to
handle and/or view the non-ASCII characters in comments while not affecting how
the data/code itself is interpreted... again, unless and until there's need to support UTF-8 there, too.<br></div><div class="gmail_extra"><br clear="all"></div><div class="gmail_extra"><div>--<br>Tim Parenti<br></div>
</div></div>