On 11/23/14, 12:24 AM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >It boils down to this: About 60-70% of our users understand International >English, only minor changes are required to accommodate that and be more >inclusive, why wouldn't we do that? If we get complaints, we should try to find neutral words, but keep in mind that the Apache LICENSE itself contains words with “ize” like “authorize”. I don’t see how you’ll be able to remove all US English from our release packages. I would need to see a clear picture on how changing spellings based on user demographics is going to help the community. If we were adopt such a policy, we might just finish migrating to Int’l English when we find Flex has suddenly become more popular in the US and have to migrate back. What if it is a tie? Or so close it changes week to week? What if Flex becomes most popular in China? > >Other PMC members made a big deal about spelling errors in the readme / >release notes, even saying that it is a release blocker. But we've not >any any user say that's a significant issue have we? For the current >releases 60-70% of user will see what they consider as spelling errors. >Doesn't anyone else see this as a bit inconsistent? For the record, I asked for another release candidate for Squiggly because you misspelled “Apache” as “Apche”. It was not an issue of US vs Int’l English. Remember that over 800 folks are theoretically reading these emails. The math from [1] says that even if those 800 folks spend 10 seconds reading each of these posts, that is over 2 hours of community time per post. We have spent over 20 emails or 40 hours of community time on your quest to choose different spellings. There is no support so far. Let’s focus on localization and not on choosing one spelling vs another. -Alex [1] http://bikeshed.com
