Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Firefox localization. Some more questions :)

0 views
Skip to first unread message

NGUYEN Manh Hung

unread,
Jul 19, 2008, 11:10:43 AM7/19/08
to dev-...@lists.mozilla.org
Thanks to Alexandru Szasz for his Narro project, my team has completed translating the FF 3 CVS tree into Vietnamese.
 
With the help of Axel's guide ("Create en-X-dude"), I could create the language pack. But why was it named "firefox-3.0.2pre.vi-VN.langpack.xpi" and couldn't be installed to FF 3.0 or 3.0.1? I even tried editing the "install.rdf" file, these two versions still reported that the langpack was not compatible.
 
So, I downloaded and installed FF 3.0.2pre. The langpack then could be installed, but it couldn't work: after I modified the general.user.locale to vi-VN, and restart FF, the application then just poped-up an error dialog with this message or something like that:
"XML Parsing Error: chrome://browser/content/browser.xul
Line: 28 Character/Column: 1
%placesDTD"
I tried looking at browser.xul, and I didn't know if there was something wrong there.
 
So, what should I do to test the langpack? And why could the langpack - though didnt work - be installed only in FF 3.0.2pre, whereas we imported the CVS tree from the TRUNK (where Axel said the FF 3 source was put in)?
 
And I noticed that the .xpi or .jar langpack files are just archive files (aren't they?!). So, instead of going through many steps to setup the prerequisites and build the langpack, will it be ok if I just collect the necessary files and use a file archiver to package them?
 -----
NGUYEN Manh Hùng



Alexandru Szasz

unread,
Jul 19, 2008, 12:11:22 PM7/19/08
to dev-...@lists.mozilla.org
2008/7/19 NGUYEN Manh Hung <lovelee...@yahoo.com>:

> Thanks to Alexandru Szasz for his Narro project, my team has completed translating the FF 3 CVS tree into Vietnamese.
>
> With the help of Axel's guide ("Create en-X-dude"), I could create the language pack. But why was it named "firefox-3.0.2pre.vi-VN.langpack.xpi" and couldn't be installed to FF 3.0 or 3.0.1? I even tried editing the "install.rdf" file, these two versions still reported that the langpack was not compatible.
>
> So, I downloaded and installed FF 3.0.2pre. The langpack then could be installed, but it couldn't work: after I modified the general.user.locale to vi-VN, and restart FF, the application then just poped-up an error dialog with this message or something like that:
> "XML Parsing Error: chrome://browser/content/browser.xul
> Line: 28 Character/Column: 1
> %placesDTD"
> I tried looking at browser.xul, and I didn't know if there was something wrong there.

Please correct this text:
https://l10n.mozilla.org/narro/narro_context_suggest.php?p=2&f=23&c=278&tf=1&st=1&s=&ci=18&cc=128&o=-1&a=0

It has an & that should be &amp;. That's where the error comes from.
I should add some checks on this on export.

>
> So, what should I do to test the langpack? And why could the langpack - though didnt work - be installed only in FF 3.0.2pre, whereas we imported the CVS tree from the TRUNK (where Axel said the FF 3 source was put in)?
>
> And I noticed that the .xpi or .jar langpack files are just archive files (aren't they?!). So, instead of going through many steps to setup the prerequisites and build the langpack, will it be ok if I just collect the necessary files and use a file archiver to package them?

I'm working on exporting language packes from Narro, you could use
that in the future.

Right now, you could edit install.rdf and replace 3.0.2pre with 3.0.1
or 3.0.0, the version you're using.

--
Alexandru Szasz

Axel Hecht

unread,
Jul 19, 2008, 6:52:04 PM7/19/08
to NGUYEN Manh Hung
NGUYEN Manh Hung wrote:
> Thanks to Alexandru Szasz for his Narro project, my team has completed translating the FF 3 CVS tree into Vietnamese.
>
> With the help of Axel's guide ("Create en-X-dude"), I could create the language pack. But why was it named "firefox-3.0.2pre.vi-VN.langpack.xpi" and couldn't be installed to FF 3.0 or 3.0.1? I even tried editing the "install.rdf" file, these two versions still reported that the langpack was not compatible.
>

Great to see you guys making progress.

On top of what Alexandru said, the compat problem is
https://bugzilla.mozilla.org/show_bug.cgi?id=442652. Sadly I didn't get
approval to land that yet.


Axel

NGUYEN Manh Hung

unread,
Jul 21, 2008, 1:29:16 PM7/21/08
to dev-...@lists.mozilla.org
Thank you Alexandru and Axel,
Sorry for my late reply, I just wanted to have the langpack fully tested before replying to your messages! :)
 
Well, because of having the langpack successfully checked with compare-locales, I hadn't thought that "little bug" was from Narro. So, after taking notice of your suggestions, I could get the langpack installed and worked right away :D
However, it took me all last Sunday to test the "accesskey" stuff - well, you don't know if you chose the right keys until you install the langpack! I had to modify the translations for quite a lot of accesskey strings.
 
 
Now, there is one more issue, may someone please advise me! :)
 
One month ago, as stated on "Create_a_new_localization" page about how to join a translation team, I firstly contacted Jasper, the vi-VN browser owner. Jasper said he usually did the work alone and was busy at that time, and if he had free time and free will, it would be at least until October. And more important, Jasper said he didn't have intentions of localizing the CVS tree and would stick to the langpack (he uses 7-zip). So, he just advised me to set a new team to translate FF 3 and "freely contact Mozilla contributors for any requests".
 
So, I already set up my own team and informed about us on the L10N:Team page. Now, as you can see in recent discussions, we're making good progress here. 
1) And I'd like to ask that if I could upload the langpack to AMO? Will it make a conflict with the FF2 langpack of Jasper? What will Mozilla do to manage these langpacks: two seperate links for two langpack addons of different authors; or ours will be an update for Jasper's?
2) In any case, will the langpack be in the experimental stage for a long time? What should be done to have the langpack released to public soon?
3) When may I request a CVS account? Will it be ok if the vi-VN browser owner doesn't have a CVS account, while the peers (me, my team, etc...) have? Then will I need Jasper's voucher and what if he doesn't want to vouch? What if Jasper also requests for CVS access at the same time, will we have to wait until he gets permissions and agrees to vouch for us?!

Sorry for so many questions, I just didn't get enough info from the wiki documentation, and it's because I & my team are attempting to have official installers of Mozilla products for Vietnamese ASAP, so we want to do the work as fast as we can.
 
PS: We have sent and installed the langpack for some in my family, friends, etc... They were excited about using FF 3 in our mother language, which made us feel more fun to do the translating! :p
 
Thanks for all your help! :)
 -----
NGUYEN Manh Hùng


Axel Hecht

unread,
Jul 21, 2008, 2:06:16 PM7/21/08
to jaspe...@gmail.com, Gen Kanai

So, looking at a recent comment from Jasper,
https://bugzilla.mozilla.org/show_bug.cgi?id=432406#c64, he's interested
in getting a cvs account.

I'd love for Jasper to comment. It'd be really cool to get a team
formed, there are various areas that benefit splitting up work and from
mutual reviews.

I'll follow up on the technicalities after that.

Axel

0 new messages