Learn about being a contributor or becoming a committer here.
The Flex SDK patch submission process has been suspended at the current time as the process is being reviewed.
We are accepting patches against the /flex/sdk/branches/3.x branch. If you have an awesome bug fix, then you can submit a patch by following these easy steps!
The trunk currently has runtime resources for 16 locales:
In most cases, these translations were done by Adobe translators using Adobe glossaries for product consistency, and have shipped with LiveCycle Data Services.
If you have suggestions about improving the translations, please do not submit a patch. The Flex team engineers who know what to do with a patch file don't have the language proficiency to evaluate which translation is better, and the translators who are language proficient don't know what to do with a Subversion patch file. Instead, please file a bug and say something like
The resource 'invalidCharError' in validators.properties, which in English is "The input contains invalid characters.", was translated as "..." in Swedish. A better translation would be "...".
Be sure to specify
so that a translator has all the necessary information simply by reading the bug.
If you'd like to submit a new locale that we don't already have, please file an enhancement request and upload a ZIP file with a complete set of
.properties files for
rpc.swc. If Adobe considers the language to be important to Flex's success -- no Klingon, please! -- Adobe will arrange for a translator proficient in that language to review and possibly edit your submission before we accept it.
Note: Tom Chiverton has a related blog entry that describes submitting a patch to the SDK here: http://rachaelandtom.info/content/submitting-patch-flex-sdk