everson at evertype.com
Mon Nov 30 23:43:13 CET 2015
On 30 Nov 2015, at 22:34, Shawn Steele <Shawn.Steele at microsoft.com> wrote:
> That's too specific.
How does it differ from OED spelling?
> The *ONLY* reason that this tag might be interesting is for interchange. (Otherwise they just go -x-pirate on it). And my users aren't going to set their language to en-US-wpsimple, but they *might* change to en-US-simple if they needed that extra assistance.
> We shouldn't be encoding one-off proprietary tags here. People can make their own private use tags if they want to talk to themselves (after all, that's what they're for).
The audience for the Wikipedia is pretty large.
> If they tried -simple and discovered a need to distinguish simplea from simpleb, then I might be interested, but I don't see a case or scenario where that even begins to make sense. They're not asking for -wpsimple and -wphard and -wpmedium.
They have en.wikipedia.org and simple.wikipedia.org and the latter cause them problems.
> Note that this isn't like an OED standard that's used by multiple organizations in an open interchange-y way. At best it's used by vendors of a single organization (and then they could go with the private tags).
I don’t know if anyone else uses the Wikipedia’s definitions for Simple English, but it’s the definitions that specify something taggable, no?
> How does -simple not solve Wikipedia's immediate problem of providing normal and simplified versions of English?
It might, but it could be used by anybody claiming “simplicity” that had nothing to do with the well-defined language Wikipedia uses. Why isn’t that a problem?
Michael Everson * http://www.evertype.com/
More information about the Ietf-languages