<br><br><div class="gmail_quote">2009/3/16 Arjen de Korte <span dir="ltr"><<a href="mailto:nut%2Bdevel@de-korte.org">nut+devel@de-korte.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Citeren Arnaud Quette <<a href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>>:<br>
<div class="im"><br>
>> I can't remember, were we moving towards or away from UTF-8?<br>
> I can't recall any such move, but toward UTF-8 would be a better bet for the<br>
> future!<br>
<br>
</div>The latter is probably true for the documentation, but I'm reluctant<br>
to state so for the C sources. We're at the mercy of whatever editor<br>
developers choose to use, since as far as I know there is no standard<br>
way of telling an editor to use UTF-8.<br>
<br>
So whatever we get here, largely depends on what developers are using<br>
at the time they write/submit code. We should really discourage people<br>
from using anything else but US-ASCII in source files, especially in<br>
comment lines.<br>
</blockquote></div><br>though I perfectly understand your point of view, I strongly disagree with US-ASCII being the standard here.<br>UTF is there so that everybody can play on the same ground, wherever he's located and whatever is mother tong is.<br>
<br>moreover, since the comments are (well, should be at least) in english, that leaves only first/last names that need the i18n support. So going to US-ASCII means that we'll have to rename contributors. I personally don't feel that respelling the name of our team members or contributors is the path forward!<br>
<br>that said, I'm opened to general feedback, and whatever the final decision is, this will have to go into the developers doc...<br><br>cheers,<br>Arnaud<br>