I do agree that we should use American English spelling, it gets confusing (and looks bad) when we have all sorts of different spellings in the same code base<div><br></div><div>Regards</div><div>Filippos<br><br><div class="gmail_quote">
On Thu, Apr 14, 2011 at 2:56 PM, Johannes Schickel <span dir="ltr"><<a href="mailto:lordhoto@scummvm.org">lordhoto@scummvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 04/14/2011 01:48 PM, Max Horn wrote:<br>
> Hi folks,<br>
><br>
> could we please agree on one way to spell things (American or British English) and then stick to that? I find it highly irritating (and having quite an error potential) that e.g. the new TsAGE engine defines a class "Serialiser" which is a subclass from Common::Serializer.<br>
><br>
> In general, I wouldn't mind so much, but this example really tripped me up. Personally, I am all for AE. Actually, I kind of always operated under the implicit assumption that this was our standard; but after just checking, this is not the case, as is seen by grepping for various terms. I did a count on the matching lines for some terms, using<br>
> gg -i TERM | wc -k<br>
> and got these results for AE vs BE spellings:<br>
> color vs. colour: 9799 vs. 1209<br>
> alize vs. alise (as in serialize, initialize, normalize, ...): 1434 vs. 509<br>
> behavior vs. behaviour: 122 vs. 63<br>
> synchronize vs. synchronise: 17 vs. 203 (without tsage: 8)<br>
><br>
><br>
> Unless I hear strong reasons otherwise, I would like to ask all developers to try to stick to American English spelling whenever sensibly possible. Of course original game content is an exceptions. Also, for our GUI, I wouldn't mind if we offered both an AE and a BE translation (and if desired, also Australian, Canadian, etc.)<br>
<br>
</div>I am all for sticking to American English too.<br>
<font color="#888888"><br>
// Johannes<br>
</font><div><div></div><div class="h5"><br>
------------------------------------------------------------------------------<br>
Benefiting from Server Virtualization: Beyond Initial Workload<br>
Consolidation -- Increasing the use of server virtualization is a top<br>
priority.Virtualization can reduce costs, simplify management, and improve<br>
application availability and disaster protection. Learn more about boosting<br>
the value of server virtualization. <a href="http://p.sf.net/sfu/vmware-sfdev2dev" target="_blank">http://p.sf.net/sfu/vmware-sfdev2dev</a><br>
_______________________________________________<br>
Scummvm-devel mailing list<br>
<a href="mailto:Scummvm-devel@lists.sourceforge.net">Scummvm-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/scummvm-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/scummvm-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>"Experience is the name every one gives to their mistakes" - Oscar Wilde <br>
</div>