Opening bug to track creating a localization of the Get Involved page with Faisal as the point person.
HI pascal good to see hi-In thread... Thanks
Faisal, I have added the files to the svn repo for localization, but since you are not our usual localizer, I suggest that you take contact with the hi-IN team leader: https://wiki.mozilla.org/L10n:Teams:hi-IN Thanks
cc Vineel for co-ordination
Can someone please cc Rajesh Ranjan (email@example.com) for co-ordination.
(In reply to Faisal Aziz from comment #4) > Can someone please cc Rajesh Ranjan (firstname.lastname@example.org) for co-ordination. Done, with a different email address. I hope it is the same person!
yeah, same person :-)
Hi David, Thanks for adding Rajesh, I hope he will help us in this. I generally work with localization tools like verbatim and Pootle, so can you please tell me how i can get the strings for translation. I am not much in SVN. So can you please help .
Faisal, Thanks. http://mozilla.locamotion.org/hi_IN/mozilla_lang/ Pascal, Please check if all are here as well on pootle ^^. I think you can do here. Please start translation, I will give you required access as well. Rajesh
Rajesh, the pootle instance is a community tool maintained by Dwayne I believe, only its admins can tell if his tool is synced with data Mozilla has in its repositories. All the files have been ready for translation since October, see comment #1 :) Also note that you don't need to know svn (which is not difficult btw) to translate those files, you can perfectly attach the translated files into this bug and get the files from the Web Dashboard for your locale: http://l10n.mozilla-community.org/webdashboard/?locale=hi-IN
Hey Thanks Pascal for the updates. I think we should add Dwayne to this bug, reason is when i started working with Get Involved Page few months back i saw Dwayne already had a translated version of the file in hi-IN. I dont have link right now but i think Dwayne might help us in this matter.
Dwayne is now CCed, just remember that as long as translations stay in external tools outside of the Mozilla infrastructure or worse, on your hard drive, the translations don't exist for Mozilla, at some point you will have to send Mozilla your translation :)
Okie Thanks Pascal
6 years ago
OS: Mac OS X → All
Hardware: x86 → All
The translations of mozorg/contribute.lang have been pushed back to Mozilla repo. They get done very Friday now. It is still a partial translation with some strings untranslated so I'll leave this open. The email response, I guess are also translated. Its actually not clear from this bug or its parent which files exactly are being referred to by the page, video and email responses. So knowing that might help close out most of this bug.
The files are: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/hi-IN/mozorg/contribute.lang?view=log and http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/hi-IN/templates/mozorg/emails/ Looks like you got everything. You can view it here: https://www-dev.allizom.org/hi-IN/contribute/ Note the email responses can be customised to meet the community needs if, for example, you want to point them to resources in Mozilla India. One other thing I need is an email address that will be used with the form. I suggest for now this is an alias that more than one person is on the end to triage inquiries that come in. Some notes on process here: https://wiki.mozilla.org/Contribute/Funnels/Process
Status: NEW → ASSIGNED
Brian, The localized contribute page looks great! As of now there is no alias for the regional community but we'll create one for the use at the form. Thanks for the links.
All the emails are done, the contribute.lang is at 76% so we'll leave this open for now.
@Vineel any news about the email address?
Soumya(CC'ed) is working with the IT team to create the email address: join at mozillaindia dot org as the alias. Soumya, please update as you have information.
A very GApps specific issue - not digging details in here (quite off-topic). Although, join [at] mozillaindia [dot] org is already up & usable (without the mail-forwarding/aliasing/catch-all setup). So, I don't think that's any blocker on this. @Vineel: for the time being (till fixed), we can share the email - I don't think the traffic will be very high to overwhelm us for now. Also, (commenting without much insight) the solution we're going to have (forwarding all mails from join@mio to task-force leaders) isn't among the best of solutions. As in, I'll have to go through ALL the mails to find out the dev-specific ones to reply to, or Rajesh has to do the same for l10n. I don't know if we'll have keywords in subject-lines, based on which we can determine the forwarding email - that will be good (although, not sure it can be 1+ emails from GApps - maybe). can someone please shed some light on this? (If it's off-topic, then a email/IRC will be grand to discuss & clarify this bit!)
the subject line will give you hints: Inquiry about Mozilla add-ons Inquiry about Localization ...
As Pascal mentions, you can set up filters to search for specific functional area inquiries coming in through the localized page. Longer-term, there's bug 796845 about designating specific emails to send inquiries for different functional areas for a locale.
(In reply to Pascal Chevrel:pascalc from comment #20) > the subject line will give you hints: Very well then; can we have the full list of subject line keywords to setup the filters?
(In reply to Soumya Deb [:Debloper] from comment #22) > Very well then; can we have the full list of subject line keywords to setup > the filters? You can see the subject lines for each area at: https://github.com/mozilla/bedrock/blob/master/apps/mozorg/email_contribute.py#L18 So for example, for the 'Helping Users' category 'Support' is added to the subject line so the full subject will be 'Inquiry about Mozilla Support'. These are all in English right now and it would be good to let locales localize the subject lines but that's not something we can do right now.
Hi, do you have any update about this bug? Missing steps to close this bug (page is already on production): * complete localization of contribute.lang (http://l10n.mozilla-community.org/~pascalc/langchecker/?locale=hi-IN#mozorg/contribute.lang) * the Get involved page is currently using a new template for 15 Years, so there's another file to localize: http://svn.mozilla.org/projects/mozilla.com/trunk/locales/en-GB/mozorg/15years.lang * generate a localized banner for the 15 years template * decide the mail address to be used as a recipient for these requests (I don't see any set in Bedrock)
(In reply to Francesco Lodolo [:flod] from comment #24) > Hi, do you have any update about this bug? > > Missing steps to close this bug (page is already on production): > * complete localization of contribute.lang > (http://l10n.mozilla-community.org/~pascalc/langchecker/?locale=hi-IN#mozorg/ > contribute.lang) > * the Get involved page is currently using a new template for 15 Years, so > there's another file to localize: > http://svn.mozilla.org/projects/mozilla.com/trunk/locales/en-GB/mozorg/ > 15years.lang I've send a message via the Pootle message board to the Hindi team to look at those two files.
(In reply to Francesco Lodolo [:flod] from comment #24) > * generate a localized banner for the 15 years template Is the PSD template available? Can one post the link (if it's on assets portal) > * decide the mail address to be used as a recipient for these requests email@example.com (hoping it can be changed without much hassle; say firstname.lastname@example.org?)
(In reply to Soumya Deb [:Debloper] from comment #26) > Is the PSD template available? Can one post the link (if it's on assets > portal) There's an .ai file on assets, but we can also involve the original designer https://assets.mozillalabs.com/Projects/Mozilla%2015%20Years/Logo/Source%20File/moz15_marks.ai > email@example.com (hoping it can be changed without much hassle; say > firstname.lastname@example.org?) It can be changed later if you want, but it's not necessarily a fast process (need to request the change through Github).
(In reply to Francesco Lodolo [:flod] from comment #27) > > There's an .ai file on assets, but we can also involve the original designer Totally works - thank you! > (need to request the change through Github). So, I can send pull request that can be merged? That's definitely a fast process! Or, are there other formalities which take long time? Now, I'm not a localizer, so leaving the first two tasks on Rajesh & Faisal - can take care of the rest two & send pull request. Does that sound okay, or should there be any other SoP to move on ahead?
> So, I can send pull request that can be merged? That's definitely a fast > process! Well, it depends on the queue (it's not just localized pages, it's the entire mozilla.org website). Anyway, you'll just need to open a bug (if this one it's not still open) and I can take care of it for you ;-)
Hi, any update on this? I've added the 15years.lang file inside your locale folder in r117860. Resetting Assignee since it's too early for me to manage this bug, before that localization must be completed.
Assignee: francesco.lodolo → nobody
Yes I can see the rev... Hi Dwayne: Could you please update the rev on locamotion...would be better for consistency and memory use. Thanks!
(In reply to Rajesh Ranjan from comment #31) > Yes I can see the rev... > Hi Dwayne: Could you please update the rev on locamotion...would be better > for consistency and memory use. Thanks! The files are updated weekly, soon daily and pulled by :flod from githib repo so they should be up-to-date.
Quick update: the 15 years template is gone, now we only use contribute.lang (and no need for custom graphics). Unfortunately there are currently *a lot* of strings missing for mozilla.org http://l10n.mozilla-community.org/webdashboard/?locale=hi-IN contribute.lang is currently 12 strings behind, and using an old template because of that
Page is localized, we still need a piece to enable the new template next Wednesday (see bug 1082104).
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.