That's probably the best way for now. It's the author's Extension and he should decide whether a translation should be added or not.Marshalrusty wrote:The alternative, as you say, is for translators to submit their translations directly to the extension author. While this isn't perfect, it at least ensures that the two things are packaged together and easily installable. It also lets the author decide how to handle multiple translations in the same language and so on.
I would handle this the same way that I would handle extensions. An extension would list the earliest version of phpBB that it was compatible with in its "manifest" (or whatever you want to call it). I would also add that version as a search criterion, so that when somebody was searching for extensions, they could specify their version of phpBB and filter out extensions that didn't work with their version (by default, those extensions would show up, but with a Warning next to them to encourage them to upgrade phpBB).Marshalrusty wrote:So if you have a viable solution that doesn't result in a giant database of outdated extension language packs that nobody can make heads or tails of, I would be most interested. If you would be interested in helping set something like this up, for example, I'm sure we would eagerly provide you with any necessary assistance.
Most of us have our contributions on github where the flow is pretty much this. Others will simply email or PM the translation to the author as well in which case it just gets added to the repo. So really this is already in place. Not sure it's the ideal solution though but I think it's as good as it gets especially if they send in pull requests, which makes it easier.Ger wrote:Would it be possible to add a tab to the extensions DB called "translations" where a user can upload their translation? Uploading would result in sending a notification to the extension author an a list of uploaded translations in the translations tab. The author can choose whether or not to include the translation in the package. Of course, it would be nice if the author can indicate the change is just the addition of a translation, thereby making the validation quick and easy.
who do you mean when you say "most of us"? are you a translator, and this "us" means "the translators"?DavidIQ wrote:Most of us have our contributions on github where the flow is pretty much this.
arod-1 wrote:Who do you mean when you say "most of us"? are you a translator, and this "us" means "the translators"?
if so, i do not think you have your facts right. i do not believe most translators have github account
if this "us" means anything other than "the translators", then i think your response is simply irrelevant. this thread deals with translations of extensions - i'd appreciate it if you can stay on-topic, or rather, i'd appreciate it if people will avoid making off-topic comments.
 as always, i might be wrong here: do you have any evidence or statistics showing that most translators, or rather, translators to most languages, are indeed using github?).
I also assumed that since I posted as the "Extensions Team Leader" that you'd surmise that I was talking about extension authors.arod-1 wrote:so i could not find any "official" way to add a new language to an existing extension.
I can see this being a gigantic burden on the extension author. If the author makes a change/adds to a lang var then the lang pack would have to be updated too. I can't speak for anyone else but my Estonian, French, Spanish...basically everything that isn't en is right up there with non-existent. This is why I am telling users to not push to my github repos as it won't get merged into the extension but, rather, translate it and place in a topic in the support area.Marshalrusty wrote:The alternative, as you say, is for translators to submit their translations directly to the extension author. While this isn't perfect, it at least ensures that the two things are packaged together and easily installable. It also lets the author decide how to handle multiple translations in the same language and so on.
asking you to not go off-topic is not "back seat moderation".DavidIQ wrote: [*]Don't back-seat moderate. It's against the rules.
this is a simple stumble in reading comprehension: i did not talk about "extension authors".DavidIQ wrote: [*]You're way off. When I said "Us" I meant extension authors as extensions are what I assume you're talking about here, an assumption I made after you said this:arod-1 wrote:so i could not find any "official" way to add a new language to an existing extension.
It is. Let's leave it at that since no infractions are being given out at this time.arod-1 wrote:asking you to not go off-topic is not "back seat moderation".
There aren't any guidelines unfortunately. We've never really found a good way to deal with this. Github doesn't seem to have anything viable at the moment for dealing with translations and using github to accept translations is a bit tedious anyways as stated by Rich. There are other translation services that might help with this but we haven't found any that can be used properly.arod-1 wrote:are there any guidelines for the distribution of translations to extensions?
how should these translation be consumed by forum operators?
how does it mesh with consuming the extensions themselves?
(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....