W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2013

Re: Web Audio API uses British spelling

From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date: Wed, 5 Jun 2013 17:17:41 -0400
Message-ID: <CANTur_7m4=KaL-DzavBGTh+kS0RQim9Udz+MFVKtEyuSUcLjbg@mail.gmail.com>
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: "public-audio@w3.org" <public-audio@w3.org>
I would be more than happy to change Gecko here, but given our past
experience, it seems impossible to change WebKit/Blink, so this ship has
probably sailed already. :(

Cheers,

--
Ehsan
<http://ehsanakhgari.org/>


On Tue, Jun 4, 2013 at 7:44 AM, Dominique Hazael-Massieux <dom@w3.org>wrote:

> Hi,
>
> While taking a glance at
> https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html ,
> I found a number of instance of British spellings — which in most cases
> is a purely editorial "bug" given W3C's policy to use US English as its
> official language.
>
> Where it is more annoying is that there are exposed methods that uses
> the British spelling; at the very least, createAnalyser() (but there may
> be others).
>
> The trouble is that future APIs that would provide similar methods for
> other fields are likely to use US spelling, creating a fairly annoying
> discrepancy for developers. Is there any chance this could be changed to
> use the US spelling? I understand the API is already deployed in a
> number of browsers, but maybe is there still time to get that fixed?
>
> Dom
>
>
>
>
Received on Wednesday, 5 June 2013 21:18:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:18 UTC