Problems with Mozilla Translator

[A. Decorte]

Hi, we are a group that works in a localization in Friulian for
Firefox. So far we did our work manually, editing the files; I've now
decided to give a try to MT, which should make more easy our work;
I've imported successfully our langpack, which is available also on
addons.mozilla.org. I can translate strings too, but I cannot export
them. The xpi exportation fails, both if selecting all platforms and
regions or just Windows. The jar exporting creates actually a jar
file, but with a different folder structure, so that the langpack
doesn't work after. I've tried also on Linux, but I get other error
messages. Any help? From what I saw MT is really a great tool

[Robert Kaiser]

A. Decorte schrieb:

Do "Export CVS directory", the .xpi and .jar generation fits well with
old-style applications (Mozilla suite, SeaMonkey 1.x) but may not work
correctly for the new generation (Firefox/Thunderbird/SeaMonkey 2/...)

Robert Kaiser

[A. Decorte]

I tried to choose Export->Export CVS translation, I chose then a local
directory and the locale fur-IT, but I get nothing in that directory,
and also no error messages. I'm using MT 5.21, btw
Thanks for your help

[Michael Wolf]

A. Decorte napisa:

Hi,

you wrote that the Friulian langpack is on addons.mozilla.org. I
downloaded it though it is for FF 2.0.0.1. I found some errors in this
langpack. Maybe you didn't find them yet.

there are following errors:

1. fu-it/global/nsProgressDialog.dtd there are some comment lines of
Localization notes repeated, but only with closing comment tag, the
start tag is missing.

2. fu-it/global/printjoboptions.dtd the text there is a wrong character
encoding, not in UTF 8. Besides in entities colorRadio.label and
grayRadio.label the closing quotes are missing.

3. /browser/preferences/fallBackEula.dtd is in wrong characcter encoding.

[Michael Wolf]

A. Decorte napisa:

I found still another error. In global/xml/prettyprint.dtd the last line
of the Licence note is double, with missing starting tag too.

I do not create xpi by MT but it may be that it would better to use the
chceckbox Neutral only because FF has only one jar file. The other
checkboxes are, AFAIK, for the Szute only, because there are separated
jar files for the platforms (win, unix, mac) and for regional contents
(region).

[Ricardo Palomares Martinez]

A. Decorte escribió:

First of all, MT XPIs can't really work with Firefox because no
install.rdf is provided by MT, just an intall.js that is not read by
Firefox AFAIK. So, you may want to stick to just JAR files and,
ideally, register as an official language for CVS access.

Other than that, I've seen Michael Wolf's comments about some problems
with your localized files. If fixing those problems doesn't solve the
issues with MT, you are welcomed to send me your Glossary.zip and I'll
try to look at it (if you choose to do so, please remove ".PUBLI" from
my name).

Ricardo

--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?

[A. Decorte]

First, thanks for your answers. I've fixed the problems reported, and
created a new project with the new jar file. Unfortunately, it still
doesn't work. Now CVS exporting works, but I get the same wrong
directory structures that I get when I chose Jar export. So I'll send
glossary.zip to Ricardo to see if we can sort out the problem.
By the way, the extension version is 2.0.0.1, but it works with
Firefox 2.0.0.*
About the registration, we wanted to do it for a long time, since the
advantages are obvious, and especially the visibility of the project.
The fact that stopped me (since the other translator is very busy now)
is that the procedure to get CVS access and everything seems a bit
complicated and long, since it also involves sending a post message to
the USA or a fax (for example, for OpenOffice, a mail with the signed
document was enough).
Thanks for your help
Andrea

[Axel Hecht]

We're in the process of shaping that process to be more stream-lined.

In the case of Friulian, I could imagine that we'd keep that in the
state of a language pack for the time being, more on that if it's not
totally within the week we're doing the process refactoring.

What you want to do though is to create a wiki page for your
localization so that everybody knows who's working on it and how to get
in touch. In your case, that should go to

http://wiki.mozilla.org/L10n:Teams:fur, similar to what we have for
http://wiki.mozilla.org/L10n:Teams:hy-AM or others. That page should be
short, but you can use the wiki to add more information of interest.

Axel