again, please stop top-posting. See my response inline, as usual. On Mon, Jul 9, 2012 at 8:50 PM, Klaus Silveira <cont...@klaussilveira.com> wrote: > pt_BR is completely out of sync with EN, making the entire translation > effort volatile. The current focus of the translation is syncing "language" > and "security", as well other crucial parts. "reference" is our last > priority right now. > > If someone syncs "reference", either cURL or any other part of the > reference, the chance that the build will break due to non-existing entities > or references is huge. If we focus on crucial parts of the manual that are > outdated, this chance is almost none. This minimizes the effort of the
Thats not entirely true. Most extensions are fairly self contained, especially the ones that aren't consider _core_ functionality. As long as the entity files (language-defs.ent and friends) are translated there should be no risks, especially for an extension that doesn't get changed frequently like cURL. > entire translation group. Accepting patches blindly and thinking any commit > is good has caused the mess that pt_BR encounters itself right now. Ofcourse. That is way there is a mailinglists which all commits are sent to so they can undergo yet another review. -Hannes
