Proposal: Require internationalization for "automatic distribution"
Currently the review requirements state that internationalization (i18n) is suggested, but not required.
I propose that we change this to required.
- CiviCRM is difficult enough as it is, and it's even more difficult to get started with for non-English users, let's remove any barrier we can, by making sure code supports i18n out of the box.
- It creates an extra incentive to send a merge-request to improve i18n, if a bug is found, knowing that the maintain must work towards a fix.
- Incorrect use of strings that do not translate well are often "code smells", clever hacks that often don't age well.
- When extensions are made available for automatic distribution, the strings are automatically extracted and sent to Transifex. For developers, it's fairly easy to wrap strings in
E::ts
& JS/tpl equivalents.
cc @AllenShaw @MikeyMJCO