First, I don't think that a new language string really makes a translation "invalid"; it just means there's a gap. The translation will still work for most things, and new strings have (or should have) a fall back. (Does phpBB 3.1 still show the variable name?)arod-1 wrote:(truncated for brevity - quoting just to make it clear which post i'm responding to. post itself is 2 above)DavidIQ wrote:One possible solution would be....
as far as i understand what you are saying, i think it's an excellent solution.
one unanswered question (or at least, one question i did not understand the answer to) is how extension upgrades should be handled:
what happens when the extension author publishes a new version, which includes a new language variable? does this automatically renders all existing translations "invalid"? and when someone (either the original translator or someone else) wants to fix it by translating the extra variable, what is the process? do users have access to "unapproved" translations so they can correct the problem(s), or will every translator need to start from scratch?
Second, if anybody can upload translations to the CDB, can't somebody take an existing translation, modify it and upload the new version to the CDB?
Did you read my proposed solution? If so, how did that sound?arod-1 wrote:except for this one point, and as far as i understand what you said, it sounds to me like a good solution.
once this (or something else) becomes the "official guideline", it would be nice it it can be advertised to the localized communities.