Last Comment Bug 560810 - [an] [Fx,Tb] New localization: Aragonese
: [an] [Fx,Tb] New localization: Aragonese
Product: Mozilla Localizations
Classification: Client Software
Component: Registration & Management (show other bugs)
: unspecified
: All All
-- normal (vote)
: ---
Assigned To: Localization Registration Bugs
Depends on:
Blocks: fx-l10n-an
  Show dependency treegraph
Reported: 2010-04-21 03:48 PDT by Daniel Martinez
Modified: 2013-02-05 02:48 PST (History)
7 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

hg user repo export (797.51 KB, application/x-gzip)
2012-06-09 09:57 PDT, Daniel Martinez
no flags Details
Aurora updated l10n files (616.74 KB, application/x-gzip)
2012-07-06 07:53 PDT, Daniel Martinez
l10n: review+

Description User image Daniel Martinez 2010-04-21 03:48:53 PDT
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; an-es) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ Debian/squeeze/sid () Epiphany/2.30.2
Build Identifier: 

My name is Daniel Martinez and I'm in a group called softaragones ( that dedicate to translate software into Aragonese. My e-mail address:

The 639-1 code of the language is an
English name: Aragonese
Native name: Aragonés

We're interested in translate Firefox and we're using narro to do it.
You can view our progress at

I filed this bug to registrate Aragonese team.

Reproducible: Always
Comment 1 User image Daniel Martinez 2012-01-21 11:28:31 PST
Now we changed the way to make the translations and we're using other tools.

The result of our new work is here
Comment 2 User image Daniel Martinez 2012-01-23 09:31:03 PST

*** This bug has been marked as a duplicate of bug 720365 ***
Comment 3 User image Toni Hermoso Pulido 2012-01-23 09:34:11 PST
Ola Daniel, we'll use this bug later on (after a couple of langpacks maybe) to ask for official Aragonese Mozilla products.
Comment 4 User image Toni Hermoso Pulido 2012-03-03 12:57:14 PST

after Axel's comment in IRC, I would like to ask for a Hg personal repo for Daniel so he can start working with the strings before submitting them to the definitive repository.

Otherwise, would be other recommended way? 

Which are the steps to follow? Should he fill in and send any form?

Thanks in advance!
Comment 5 User image Toni Hermoso Pulido 2012-03-17 01:41:32 PDT
Sorry for pestering. Any recommendation? Thanks!
Comment 6 User image Axel Hecht [:Pike] 2012-03-26 12:21:38 PDT
I suggest to go for a user repo. has instructions on how to create those.

If you get to the point to want write access for Daniel, feel free to file a bug for level 1 access, and CC me to vouch.
Comment 7 User image Toni Hermoso Pulido 2012-05-24 13:31:44 PDT
Hi, Daniel has already populated his user repo with current Aurora strings: and he is generating XPI langpacks with no problems. Which would be the next steps?
Comment 8 User image Toni Hermoso Pulido 2012-06-05 23:01:01 PDT
Hi! Any direction about next steps? Thanks!
Comment 9 User image Daniel Martinez 2012-06-09 09:57:33 PDT
Created attachment 631673 [details]
hg user repo export
Comment 10 User image Daniel Martinez 2012-07-06 07:53:33 PDT
Created attachment 639669 [details]
Aurora updated l10n files

updated to aurora and now there are several searchplugins
Comment 11 User image Toni Hermoso Pulido 2012-07-19 00:10:13 PDT
Hi Axel, according to what you commented me, we cannot advance in this bug (and other candidate locales) because of the lack of clarity of certain documentation that is affected by Bedrock migration 
Could we track this in a separate bug maybe?
Comment 12 User image Axel Hecht [:Pike] 2012-10-10 07:36:42 PDT
Comment on attachment 639669 [details]
Aurora updated l10n files

Hi Daniel, sorry for the lag. The attached source is looking good, and we'd like to add you to the Firefox 18 cycle.

We'll have a few bugs and work to go through beyond the mere strings in Firefox, I'll start filing those later today.

I see that you continued to land your work on, that's great, thanks.

I see that you already landed one local search engine, we should quickly verify that, or back it out until we did. I'll detail in the bug for that.

Thanks for hanging in there, I hope that we'll be able to give you a smooth path from here on. See also on what we stream-lined in the meantime.

Note You need to log in before you can comment on or make changes to this bug.