Closed Bug 482532 Opened 16 years ago Closed 16 years ago

[es-MX] Enable Spanish (Mexico) localization on SUMO

Categories

(support.mozilla.org :: Localization, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Pike, Assigned: paulc)

Details

(Whiteboard: sumo_only)

We need to enable the localization of SUMO in Spanish (Mexico) [es-MX]. Ricardo, this is one of the better places to get the community to help out directly. And, Ricardo, we'd need "Spanish (Mexico)" in Spanish (Mexico) again to set this up, please add that here, utf-8 encoded. Thanks.
Español (México)
Target Milestone: --- → 1.1
Target Milestone: 1.1 → 1.0
Assignee: nobody → paul.craciunoiu
I added this after the existing Spanish locale, but of course the strings need to be translated into Mexican Spanish. Noting that here. Also, if I should have just used the English template, please reopen and I'll do that. r23852 / r23853
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
We need someone to act as the Mexican Spanish Firefox Support locale leader. This person will be our main contact with the Mexican Spanish Firefox support community, as well as be responsible for the admin tasks for the es-MX locale, like translating the start pages and website interface. For more information, see <https://support.mozilla.com/kb/Localizing+Firefox+Support>. Ricardo, are you going to be the Mexican Spanish Firefox Support locale leader? If so, I need your support.mozilla.com username, so I can give you proper permissions. I have also enabled es-MX on our staging server, so you can test things out, find any bugs, and get familiar with the system, before we enable it on support.mozilla.com. The staging server is <http://support-stage.mozilla.org/>. To access the site, username: support password: stage The "Localizing Firefox Support" URL can also be found on the staging server: <https://support-stage.mozilla.org/kb/Localizing+Firefox+Support>
How do we ensure that we don't duplicate the efforts of locales from "major" languages. I am thinking of Spanish, English, potentially French, etc.? Would the support articles already being worked on by the es-ES locale vary that much for the es-MX users? Product localization does have specific differences in terminology, protocol handlers, search engines, RSS feeds, etc. But, I wonder how different the user support will actually be. Wondering if some of these locales should all work together? Possibly a new bug, but reopening for a quick discussion. Thoughts?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Seth, I think this is a good topic for a bigger discussion (in the newsgroups?) between localizers, the SUMO team and l10n drivers. It's true that in some (most?) cases these efforts would double, but on the other hand, if we have two localizations that use different terminology (say, a different translation for "cookies"), don't we then need two separate support articles? I think that support articles in particular need to use the same terminology that the one found in the UI, for the user to easily relate one to another. Do we have any fall-back mechanisms in place on SUMO? Meaning, if I come to es-MX version and the article I'm looking for is not available, do we suggest checking out the es-ES version?
Seth, you're raising some relevant questions indeed. Actually, we used to have the locales es-AR and es-ES separate in the past, but the two localization communities decided to join forces and merge the two (see bug 427547) to cut down on the level of work required. This seems to be going in the other direction. That is obviously fine as long as we have a group of people that want/can handle the added work, but there might be things we can do to make their work simpler. One thing that comes into mind is to have a more customized locale fallback, so es-MX would fall back to es first, before falling back to en-US. Closing this bug again though, as SUMO 1.0 is being pushed live next Tuesday. Seth, if you're planning a discussion about this topic, I'd love to participate.
Status: REOPENED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → FIXED
I talked this topic with the members of the Argentina and Spain communities and I'm totally agree to working in one "es" translation.
Okay, so I'll disable this locale on staging.
Ricardo, sounds great that you guys synced up and reached an agreement! I think it will help everyone focus on creating good Spanish support documentation with less duplicate work. I'm guessing you'll talk with the Argentina and Spain communities to get introduced, but if you have any questions or thoughts, I'd love to hear them. Just drop me a line at anytime. Welcome aboard!
Sounds like I should revert adding the locale files, yes?
Let's file a new bug to revert in 1.0.2. 1.0 is (supposed to be) tagged already, and 1.0.1 is reserved for the 3.1->3.5 update. Thanks!
Done, see bug 485644.
Resolution: FIXED → WONTFIX
Whiteboard: sumo_only
You need to log in before you can comment on or make changes to this bug.