Closed Bug 1167272 Opened 9 years ago Closed 9 years ago

[es] Localization of snippets - Deadline June 14

Categories

(Mozilla Localizations :: es / International Spanish, defect)

Product:
Mozilla Localizations
Component:
es / International Spanish
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: flod, Assigned: inma.barrios)

References

Details

I don't usually file bugs for snippets, but this is the first time we do snippets as 'es' and not 'es-ES', and I want to be sure the team is aware of the request.

Is anyone currently tracking this dashboard?
https://l10n.mozilla-community.org/webdashboard/?locale=es

You can also subscribe to the RSS feed.

As explained, deadline is in 3 weeks, so there's plenty of time.
Hi Francesco,

I'm kinda lost here, why should we need a specific International Spanish localization for snippets when there's no browser in that locale yet?
Because Spanish snippets are actually enabled for all 4 locales, so doing them as 'es' seems the most logical solution.

You can get an idea by browsing the list of snippets here
https://snippets.mozilla.com/

One snippet is not bound to a single locale.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #2)
> Because Spanish snippets are actually enabled for all 4 locales, so doing
> them as 'es' seems the most logical solution.
> 
> You can get an idea by browsing the list of snippets here
> https://snippets.mozilla.com/
> 
> One snippet is not bound to a single locale.

Jumping in here directed by Inma. :-)

I've been taking a quick look to the strings and I haven't found any word that obviously reminds me of different translations depending of the locale.

However, what I wonder is whether a Firefox for Android and Firefox Desktop built with es-AR or es-ES will fall back to "es" or instead to "en-US". Does this depend on the preferred languages set by the user in intl.accept_languages preference? If so, if the user has, for instance, "es-ar, en-us", I guess he will get the English page instead. IMHO, that's suboptimal.

Francesco, can you confirm if that would be the expected behavior? TIA
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #2)
> Because Spanish snippets are actually enabled for all 4 locales, so doing
> them as 'es' seems the most logical solution.
> 
> You can get an idea by browsing the list of snippets here
> https://snippets.mozilla.com/
> 
> One snippet is not bound to a single locale.

Jumping in here directed by Inma. :-)

I've been taking a quick look to the strings and I haven't found any word that obviously reminds me of different translations depending of the locale.

However, what I wonder is whether a Firefox for Android and Firefox Desktop built with es-AR or es-ES will fall back to "es" or instead to "en-US". Does this depend on the preferred languages set by the user in intl.accept_languages preference? If so, if the user has, for instance, "es-ar, en-us", I guess he will get the English page instead. IMHO, that's suboptimal.

Francesco, can you confirm if that would be the expected behavior? TIA
Flags: needinfo?(francesco.lodolo)
Sorry for the duplicated comment. :-)
(In reply to Ricardo Palomares from comment #4)
> However, what I wonder is whether a Firefox for Android and Firefox Desktop
> built with es-AR or es-ES will fall back to "es" or instead to "en-US". Does
> this depend on the preferred languages set by the user in
> intl.accept_languages preference? 

I think the relevant language for snippets is the chrome's language, not accept languages like web pages.

@giorgos
Can you confirm my impression?

As far as I can tell, snippets have all 5 of them (es, es-*), so there would be no fallback anyway.
Flags: needinfo?(francesco.lodolo) → needinfo?(giorgos)
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #6)
> (In reply to Ricardo Palomares from comment #4)
> > However, what I wonder is whether a Firefox for Android and Firefox Desktop
> > built with es-AR or es-ES will fall back to "es" or instead to "en-US". Does
> > this depend on the preferred languages set by the user in
> > intl.accept_languages preference? 
> 
> I think the relevant language for snippets is the chrome's language, not
> accept languages like web pages.
> 
> @giorgos
> Can you confirm my impression?

That is correct.
Flags: needinfo?(giorgos)
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #2)
> Because Spanish snippets are actually enabled for all 4 locales, so doing
> them as 'es' seems the most logical solution.
> 
Well, product web pages are also enabled for all 4 locales, and we're not doing them as 'es'. I'd jut like to know if es-ES snippets will be moved from the current 'es-ES' web dashboard to the new 'es' web dashboard.

Additionally, as a linguistic side note, snippets are mainly marketing content. This means that when translating a snippet for es-ES, I have European Spanish users in mind, so I actually localize, and sometimes transcreate, these pieces of content. For an Argentinian user they may not sound good at all.

I know this kind of linguistic nuances are difficult to understand for non-Spanish speakers. Bear in mind, though, that Spanish is spoken by nearly 500 million people around the world.
(In reply to inma_610 from comment #8)
> Well, product web pages are also enabled for all 4 locales, and we're not
> doing them as 'es'. I'd jut like to know if es-ES snippets will be moved
> from the current 'es-ES' web dashboard to the new 'es' web dashboard.

Moving snippets from es-ES to es is basically a try, because I noticed that, while we requested snippets for es-ES, they were actually used for all Spanish variants.

These are the alternatives in my opinion:

1. Go back to the request as es-ES but use snippets only for es-ES. I don't think this would work for the snippets team, so we'd need a separate localization for each Spanish. But I don't think that all 4 Spanishes have resources to keep up with the number of requests for snippets.

2. Go back to the request as es-ES and use it for all es-* (like it happened so far).

3. Localize snippets as 'es', assuming that's possible.

CCing also Jean to make sure he's aware of the discussion.
Hi,

I didn't know that, wasn't told that es-ES snippets were being used for all Spanish variants. And that's because those variants have no localizers to keep up with those requests, right?

I don't like the idea of having to "sacrifice" the local flavor of snippets, just because other Spanish locales don't have enough resources. 

All in all, if everybody at the team agrees, I can continue translating this content... this time knowing that my audience is more international.
(In reply to inma_610 from comment #10)
> I didn't know that, wasn't told that es-ES snippets were being used for all
> Spanish variants. And that's because those variants have no localizers to
> keep up with those requests, right?

Mostly yes. Also, we normally have so many snippets requests only for locales that have newsletter enabled, and as far as I know that's 'es' too.
Hi,

Me again... One last thing before SVN committing the snippet translations for June, and closing this bug: should the External Web Projects section be removed from the 'es-ES' dashboard[1]?

[1]https://l10n.mozilla-community.org/webdashboard/?locale=es-ES#web_projects.
Good question. I think it makes sense at this point to display it on the actual 'es' dashboard.

Also, just noticed that there is a project with es-ES in it, not sure it makes a lot of sense (but that would be a question for the Fx Account owners)
https://l10n.mozilla-community.org/~flod/webstatus/?locale=es-ES
r141840. 

Subscribed to the RSS feed for this new locale, so hopefully no need to open any bugs for 'es' snippets in the future!
Thanks Inma, we should build you a monument :-)

I think that we can close this, I'll work to fix the dashboard and display web projects in the right 'es'.
Assignee: mautematico → inma.barrios
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #15)
> I think that we can close this, I'll work to fix the dashboard and display
> web projects in the right 'es'.

Fixed as well
https://l10n.mozilla-community.org/webdashboard/?locale=es-ES#web_projects
You need to log in before you can comment on or make changes to this bug.