Hi, > IMO, we should not be trying to decide between US and Int’l English.
And nor should we be using US English for an international audience given who are the majority of our users. > For example, I don’t know if our documentation actually contains the > phrase “your email address is missing a period”, It's doesn't but our resource files did, and that was handled by the locales, I don't think we need to go than the path of making different versions of the release notes / readme however. The differences are reasonable minor. > Before we go off spending energy rewriting the doc, I would like to see > evidence that folks are finding it confusing and that some change is going > to make a difference. I don’t recall very many JIRA issues about > confusing documentation or threads on the mailing list. Over the years I've had numerous people complained to me about this, but them I'm based outside the US and the issue is a lot more visible there. > Adobe put a stake in the ground by creating classes like ColorPicker and > SolidColor that goes in the “color” property. I would be against renaming > these classes. No we wouldn't do that as that would not be backwards compatible. This is more about the documentation. > And thus, I would not be in favor of our default documentation saying things > like “Use > the ColorPicker to select a colour”. I don't see any problem with that, it's actually correct. > We’ve localized the Installer Well some of it. The ant for air component isn't localise, so you get a mix of local language and US english in the install log. > Do we know if any other Apache projects localize all of their content? A lot do - Open Office be probably the best example, but it's audience is different to ours. > I also thought of a variant: would there be an issue if individual > committers built out their own website (hosted on their own domain) that > had a translated copy of flex.a.o and we offered links to it on the home > page? While that would work it would be better if the content was at Apache, that was several people can work on it or take over if the original author decided to abandon it. > I don’t know how hard it would be to do, but visitors from other locales > would be offered maybe a popup Popups are annoying. We can detect the browser locale (geoip) or better still it's preferred language and/or provide links if required. Thanks, Justin
