Language pack tracker

[GoogleCodeExporter]

Current plans:
- Incorporate Japanese, French, Spanish and German locales built-in: recruit 
developers for string freeze (strings guaranteed to be frozen until 9.3.2)
- Additional language packs offered as options
- For 9.3.2 start new policy of English-only release candidate for translators 
pending complete release following

Original issue reported on code.google.com by classi...@floodgap.com on 29 Aug 2010 at 5:43

[GoogleCodeExporter]

This bug will also become the tracker for each release, and will be left 
"Critical". It should never be "Fixed" -- it will just be updated.

Original comment by classi...@floodgap.com on 9 Sep 2010 at 3:43

• Changed title: [i18n] Language pack tracker
• Changed state: Rolling

[GoogleCodeExporter]

Original comment by classi...@floodgap.com on 9 Sep 2010 at 3:52

• Changed title: Language pack tracker
• Added labels: Internationalization

[GoogleCodeExporter]

I haven't gotten any replies back from the Spanish or French translators, so 
I'm just going to assume we launch with Italian, German and Japanese as seed 
translations and see if we can get any other languages on board for 9.3.x since 
this needs to get rolling.

Here is my anticipated schedule; please advise if you believe these milestones 
are not achievable:

- Translation first drafts made available to me for tree integration by 
November 1st

- Code freeze (on my part) of bugs to make 9.2.2 by November 15th, with release 
candidate available as soon as possible after for testing in your language

- Release week of November 22nd

Comments?

Original comment by classi...@floodgap.com on 28 Sep 2010 at 1:40

[GoogleCodeExporter]

How are we doing? Since we have a couple more weeks towards (provisional) first 
draft, anyone not going to make it?

Original comment by classi...@floodgap.com on 18 Oct 2010 at 5:38

[GoogleCodeExporter]

I've uploaded a new version of the Japanese translation to my site.
I released it as an alpha version to get feedback from other Japanese users.
Here is the urls:
http://page.freett.com/macos9/classilla/alpha.html
http://big.freett.com/macos9/Classilla921ja_a01.smi.sit

I've not translated the JavaScript Debugger and LDAP, and I'm not sure that 
will happen...

Original comment by wabisukenohana on 18 Oct 2010 at 2:51

[GoogleCodeExporter]

Is it difficult for you to translate those modules? I could stub them out with 
English temporarily.

Original comment by classi...@floodgap.com on 22 Oct 2010 at 6:44

[GoogleCodeExporter]

I will not be ready with the german translation at 15th of November. At least 
it will take two weeks more for me. But Release in Q4 is still possible.

Original comment by wit...@gmx.net on 3 Nov 2010 at 2:33

[GoogleCodeExporter]

Would December 1st be okay?

Original comment by classi...@floodgap.com on 3 Nov 2010 at 2:49

[GoogleCodeExporter]

Yes, December 1st should be ok, from my side. I'll give an update mid of 
November.

Original comment by wit...@gmx.net on 5 Nov 2010 at 12:30

[GoogleCodeExporter]

The localisation work is taking me longer than I originally thought, but it 
should definitely be completed by the end of November.

Cheers,
RM

Original comment by riccardo...@gmail.com on 13 Nov 2010 at 1:46

[GoogleCodeExporter]

Mathias needs more time as well, and I'm trying to get TenFourFox beta 8 
rolling and out the door, so we'll set this forward two weeks.

Original comment by classi...@floodgap.com on 2 Dec 2010 at 4:02

[GoogleCodeExporter]

10.4Fx beta 8 is out, so I want to get back to this. How are we? I have w's 
translation and I'm going to start integrating that. Riccardo and Mathias?

Original comment by classi...@floodgap.com on 17 Dec 2010 at 6:49

[GoogleCodeExporter]

Working hard, after composer took me two weeks, what I didn´t expect, as I 
nerver used it myselve. Now I got around 100 more files, to do for the next 
days. So it seems to become a "New Year's Eve-release" from my side. My german 
files will be ready at Sunday evening. And than a few days for eleminating some 
bugs and your integration, is this realistic?

Original comment by wit...@gmx.net on 21 Dec 2010 at 6:25

[GoogleCodeExporter]

I have Mathias' and Wabisukenohana's. Riccardo, what's your status?

Original comment by classi...@floodgap.com on 30 Dec 2010 at 3:46

[GoogleCodeExporter]

I'm awfully sorry for the delay. In December I got sidetracked due to other two 
overlapping translation assignments, then I had to rest for a few days because 
I had lost too much sleep. I believe I can resume work and have it finished for 
next week (around January 11). I do hope it's not too late and I apologise 
again for the delay.

RM

Original comment by riccardo...@gmail.com on 4 Jan 2011 at 3:26

[GoogleCodeExporter]

Update: regretfully, work assignments keep overlapping, and I had to put on 
temporary hold my Classilla localisation work. The good news is that starting 
January 25 I'll have a few days where I can work on this full-time. The 
translation/revision is almost done, so next week I should be able to finally 
send the files! Thanks in advance for the patience & understanding. / RM

Original comment by riccardo...@gmail.com on 19 Jan 2011 at 9:33

[GoogleCodeExporter]

After some experimentation with packaging methods, I'm going to simply manually 
spike the generated Classilla folder with the new locales instead of trying to 
integrate them with the build system. This also keeps them all in one place. I 
have successfully hooked wabisukenohana's ja-JP translation and JP locale in 
this way, and can switch back and forth between Japanese and English at will.

The sole glitch is that the default language where a profile is not loaded is 
going to have to be English. This affects the profile manager, for example, if 
you have that loaded, since preferences (and the selected language and locale) 
are stored by profile and one isn't active yet. At some point I should provide 
a way to set the default locale, but I'll spin that off as a separate issue. 

Original comment by classi...@floodgap.com on 6 Feb 2011 at 5:06

[GoogleCodeExporter]

In fact, what do you guys think about adding a blurb to the respective READ ME 
for your language explaining to the user how to switch languages?

I did have to add two strings on an emergency basis. We're too far along to 
rewind back to fix these and they are unlikely to occur in practice, but I'll 
correct these later. They are in sidebar/customize.js to solve issue 128 which 
can only be fixed by blocking the user from inadvertently corrupting their 
sidebar. I'll create properties for that file for our next scheduled string 
update and post the file here.

Original comment by classi...@floodgap.com on 6 Feb 2011 at 7:47

[GoogleCodeExporter]

I've already notified Cameron privately, but to keep everyone updated: 
yesterday I finished the Italian localisation and sent the relevant files to 
the Classilla HQ. If all works well, I might try to take care of the Spanish 
localisation in the future, if no one's up to it. But – let's proceed one 
step at a time... -RM

Original comment by riccardo...@gmail.com on 15 Feb 2011 at 8:02

[GoogleCodeExporter]

We could save Spanish for 9.3.0. Hopefully this will jumpstart interest and we 
can include some other language packs at the same time.

I've got the rest of the fixes for 9.2.2 done that I want to have in this 
release. I'm trying to match TenFourFox beta 12 this week, but after that I'd 
like to push the button depending on Mathias' timeframe.

What do you guys think about customizing the README for your respective 
language to explain to people how to change the language and locale? It would 
basically just have to say to go to Preferences, etc.

Original comment by classi...@floodgap.com on 15 Feb 2011 at 8:12

[GoogleCodeExporter]

Regarding the localisation of the README file, it's fine by me. I'll see if I 
can do it tomorrow. -RM

Original comment by riccardo...@gmail.com on 16 Feb 2011 at 2:18

[GoogleCodeExporter]

"I'd like to push the button depending on Mathias' timeframe"

Maybe we have a communication problem. My translation is ready since the 
beginning of the year. But there seem to be some technical reasons why parts do 
not work. Cameron, I need you (!) to install the german translation and 
investigate about the issues I sent you - as I am no developer. I am just 
waiting for informations about what could be wrong, or how to improve the 
situation.

If helpful, I can start to describe them one by one here at the wiki, to let 
Riccardo and wabisukenohana participate and see if problems occured in other 
languages too, and if not what are the differences.

Original comment by wit...@gmx.net on 19 Feb 2011 at 9:37

[GoogleCodeExporter]

I apologize, Mathias, I completely misunderstood. I thought you had a partial 
translation only.

Glancing at my mailbox, I think I still have your .jars (I will check this). 
The timeframe is no longer as acute since I picked up issue 156 which I want to 
get in as part of 9.2.2 also (it also needs strings, but this should be 
infrequent, so I'm okay shipping stringless and adding it to 9.3.x). TenFourFox 
b12 is looming, probably Tues or Weds, so I will deal with this after that. In 
the meantime I will install your jars when I get a free moment and will 
validate them manually.

Original comment by classi...@floodgap.com on 20 Feb 2011 at 5:06

[GoogleCodeExporter]

I sat down with the locales last week and discovered a number of errors, so I 
finally got an automated checker done to compare the new locales with the old 
ones. (It also found a couple small glitches in the Japanese locale, but I can 
fix those myself.)

Attached is the edited output from the locale checker, with irrelevant output 
removed. It flags missing DTDs and properties, and any syntax errors it finds 
in the DTDs and properties it is able to compare.

There were a number of critically missing files; for NoScript in particular, 
which is definitely a showstopper since NoScript is a core part of Classilla.

For Mathias, its major objection was using ' ' as delimeters in the DTD 
entities.

For Riccardo, it seems to be disagreeing with quite a few keys, which look like 
they might be from a later Mozilla?

Let me know if you disagree with the errors it found.

Original comment by classi...@floodgap.com on 6 Mar 2011 at 10:19

Attachments:

• de_errors.txt
• it_errors.txt

[GoogleCodeExporter]

I should add a note about the output: NOT IN MASTER says a key was expected in 
the master locale, but not found in the copy (i.e., the locale being tested).

The extraneous key error is mostly a warning and might help you to find typos. 
Those don't need to be removed necessarily; the other error is the more 
concerning one.

Original comment by classi...@floodgap.com on 6 Mar 2011 at 10:22

[GoogleCodeExporter]

I'll do a full review in a few days, and hopefully resend the IT packages next 
week. Cameron, if I find problems or things I don't understand in the error 
output, I'll ask for your help.

Very sorry for the inconvenience. 
RM

Original comment by riccardo...@gmail.com on 6 Mar 2011 at 10:41

[GoogleCodeExporter]

No worries :) I'm going to bang out issue 156 in the meantime. Plus someone on 
68KMLA is complaining captchas weren't showing up, which is kind of a biggie. 
That we should fix here if I can.

Original comment by classi...@floodgap.com on 7 Mar 2011 at 12:05

[GoogleCodeExporter]

Issue 156 is fixed. That brings the fixes in this release to issue 74, issue 
80, issue 85, issue 128, issue 149, issue 150, issue 151 (this one :), issue 
152, issue 153 and issue 156. That is quite a few fixes in the can, and some 
like issue 156 are significant. The other problem is that I'll be probably 
looking for a new place to live come April and that means a lot of my projects 
including Classilla will be sidelined somewhat.

So I'm going to assign a hard deadline of 20 March for the locales. Whatever is 
working at that point (i.e., so far Japanese) will be shipped, because if I 
don't ship Classilla 9.2.2 then I may not be able to ship it at all until 
summertime and I think these fixes need to be released to users. Plus, I want 
the summer to finish the 9.3.0 branch because this is important to keeping 
Classilla current.

Whatever is not working by that date will be included instead with 9.3.0. I 
want these locales in there, but I think we need to get 9.2.2 out the door.

If you already know you can't make this deadline, say so; this one is an 
absolute deadline and can't slip.

Original comment by classi...@floodgap.com on 7 Mar 2011 at 3:27

[GoogleCodeExporter]

I have Mathias and wabi's locales installed and am certifying them. Planning 
for final release 9.2.2 build tomorrow.

Original comment by classi...@floodgap.com on 20 Mar 2011 at 8:50

[GoogleCodeExporter]

I had a last minute chemspill on TenFourFox and spent Monday cleaning that up 
instead of building Classilla. I'm going to do it this afternoon, however, and 
hopefully get it out next week once I have it certified. Riccardo, I'll take 
Italian into 9.3.0. No hurry/worry.

Original comment by classi...@floodgap.com on 23 Mar 2011 at 2:18

[GoogleCodeExporter]

Okay, it's out.

A couple notes so that there are no surprises:

Instead of folders, I am using modified .jars. You should use the ja-JP.jar and 
de-AT.jars in this release for future translations. Send me single files so I 
can build them into the jars from here on out.

I was able to get the Japanese locale working fine on my 9.2.2 G4, but it seems 
to crash under 10.4 Classic and I don't know why. I suspect this is a Classic 
bug.

The German locale works fine except that it overflows some prompts in 
preferences, which cannot be resized since we support 800x600 Macs. I modified 
them to the best of my ability, and all of them work, but some are not pixel 
perfect and I couldn't think of a good way to rewrite some of them (my German 
isn't THAT good ;). It still mostly works, so it's still shippable, and I'll 
defer to Mathias and Friederike in issue 159.

Original comment by classi...@floodgap.com on 30 Mar 2011 at 6:16

[GoogleCodeExporter]

Ok. These days I've been investigating the errors in the report you previously 
attached, and I may have understood part of what went wrong. Too bad I couldn't 
fix the problems in time for 9.2.2 as I wanted. "So much to do, so little time" 
as usual. But everything will be fine for 9.3.0, I'm sure. -RM

Original comment by riccardo...@gmail.com on 30 Mar 2011 at 11:07

[GoogleCodeExporter]

No worries at all. I'll give you a heads up when I can start forecasting a hard 
date (and this is a big update, too -- the long awaited layout transplant). 
Right now, Q3 sometime.

Original comment by classi...@floodgap.com on 30 Mar 2011 at 12:50

[GoogleCodeExporter]

"The German locale works fine except that it overflows some prompts in 
preferences, which cannot be resized since we support 800x600 Macs."

Haha, and I even resized some windows, ... while translating everything in 
November/December. We should start a page with some do and don´ts for 
translation. Our communication has definitely to improove ;)

"I modified them to the best of my ability, and all of them work, but some are 
not pixel perfect and I couldn't think of a good way to rewrite some of them 
(my German isn't THAT good ;). It still mostly works, so it's still shippable, "

Let´s see what you did. In every case Friederike and I have a alibi now, as 
every mistake was done by Cameron in the last minutes himselve ;)

"and I'll defer to Mathias and Friederike in issue 159." Ja bitte, Fehler aller 
Art die die Deutsche Übersetzung betreffen, dort posten!

Original comment by wit...@gmx.net on 30 Mar 2011 at 4:57

[GoogleCodeExporter]

Changing priority and dropping milestone since language strings remain frozen 
until 9.3.2. Still use this bug as a rolling thread for concerns and progress, 
of course. It will return to critical once 9.3.2 is in progress.

Original comment by classi...@floodgap.com on 6 Apr 2011 at 1:32

• Added labels: Priority-Medium
• Removed labels: Milestone-Release9.2.2, Priority-Critical

[GoogleCodeExporter]

Hi.

I'm up to make a french translation. Cameron told me I should use the same 
format as the de-AT.jar and ja-JP.jar files. Where can I get thoses in english? 
Or if any of you can tell me how they did theirs, tips or some general 
guidelines, it would be appreciated.

Thanks.

Original comment by Barma...@gmail.com on 7 Apr 2011 at 11:29

[GoogleCodeExporter]

Hi!

Barma... ? What´s your name, or how shall we call you?

Well let´s start:
Just get the latest Classilla 9.2.2 binary.
Inside the folder "Classilla", there is the folder "Chrome". There inside you 
will find the files en-mac.jar, en-US.jar and US.jar for the beginning these 
are the most important ones. These "jar files" are normal zip files, so unpack 
them, and find inside the textfiles you have to translate. These textfiles are 
UTF-8 (and have to be stored as UTF-8). Do you work with MacOS 9?

I will start a complete howto.

Mathias

Original comment by wit...@gmx.net on 7 Apr 2011 at 3:30

[GoogleCodeExporter]

Sorry, now I understood comment 31 in this issue here:

Cameron changed the jars, and we should use the de-AT.jar, and AT.jar (or the 
japaneese ones) for future translations. But It seems very complicated to 
translate from a language one doesn´t understand. 
Cameron, could you please explain exactly what you did and how you think 
translations should be done now. Am I right, that French translation shold now 
use a German or Japanese jar? If so, than we should use english Classilla 9.2.1 
jars for new translations.

Original comment by wit...@gmx.net on 7 Apr 2011 at 3:48

[GoogleCodeExporter]

This is my procedure for creating locale files:

1. Take a look the "installed-chrome.txt" in the Chrome folder of the
original Classilla
and find all lines that start with "locale" for English

2. Unzip .jar files indicated by step 1, and make two folders named
"ja-JP" and "JP" in the Chrome folder.

3. Move the folders indicated by step 1 to "ja-JP" or "JP"
appropriately. ("inspector",
"venkman" or "noscript" folder will be moved into "ja-JP")

4. Replace inside all the contents.rdf files "en-US" with "ja-JP", and
"US" with "JP"
by following the http://www-archive.mozilla.org/projects/l10n/mlp_what2.html

5. Add lines to the "installed-chrome.txt" like
locale,install,url,resource:/chrome/ja-JP/global/
locale,install,url,resource:/chrome/ja-JP/communicator/
locale,install,url,resource:/chrome/ja-JP/navigator/
[...]
locale,install,url,resource:/chrome/ja-JP/noscript/
locale,install,select,ja-JP
locale,install,url,resource:/chrome/JP/global-region/
[...]
locale,install,select,JP

6. Restart Classilla

and Voila! You've got ja-JP pack.
Now you can easily edit and debug locale files. Changes will take
effect after restarting Classilla.

Original comment by wabisukenohana on 7 Apr 2011 at 4:34

[GoogleCodeExporter]

wabisuke got to this first. Basically, I want the files structured the way he 
did it -- this means I can just zip up the ja-JP (or fr-FR, de-AT, etc.) folder 
into a single jar instead of having all the .jars of the English version, which 
eventually one day I will similarly consolidate. However, the fr-FR folder is 
fine too. The only difference between wabisukenohana's ja-JP folder and the 
ja-JP.jar in the released Classilla is that 1) the folder is now zipped up into 
a .jar, and 2) installed_chrome.txt and the languages RDF point to the jar 
instead of the individual folders.

I assume Barma* is mx-v from 68KMLA, but I'll need a name for the credits :)

Original comment by classi...@floodgap.com on 7 Apr 2011 at 7:58

[GoogleCodeExporter]

Cameron, does this mean, that we have no correct english version, like the 
translated files should be organised right now? Does this really mean people 
have to translate from japaneese or german right now? That may be impossible. 
So we need english files for translation.

Can you please be as precices as possible which files have now to be 
translated. Do we start at 9.2.2 with new tranlations (like French), or go back 
to 9.2.1 english files?

Which files do we take recently?

Sorry for being annoying, but I just got 2 weeks before the last release the 
informationa about venkman and noscript.

Original comment by wit...@gmx.net on 12 Apr 2011 at 12:06

[GoogleCodeExporter]

I don't follow. All they have to do is make sure they are organized in the same 
way as the ja-JP or de-AT translations. The filenames are all still the same as 
they were in en-US, they're just in more systematic places.

Eventually I will redo the en-US, but I'm not doing that until all the kinks 
are worked out of the other translations so that en-US will remain as a 
fallback. It's a bigger job anyway because I have to rewrite the build system 
to do it.

Original comment by classi...@floodgap.com on 12 Apr 2011 at 3:11

[GoogleCodeExporter]

Hi everyone. I am working on a Spanish translation of Classilla, but I've 
problems to test it.
I created the es-ES.jar and ES.jar with a modified contents.rdf file. I 
modified installed-chrome.txt, adding:
locale,install,url,resource:/chrome/es-ES/global/
...
but Spanish doesn't appear in the list. What am I doing wrong? Do I need to 
append "locale,install,select,ES" at the end of installed-chrome.txt?

Oh, by the way. Is someone working in the Spanish translation? I can help 
him/her. Regards

Original comment by nicoluna...@gmail.com on 28 Apr 2011 at 2:11

[GoogleCodeExporter]

Mathias and wabisuke, thanks for your input. Following this, I believe I'll 
manage.

I plan on using OS 9 yes, seems the easiest way. Or is it?

I am indeed mx-v on 68kmla.  Sorry about the confusion. You can call me 
Jean-Claude. (or just JC) :)

Cameron, now I get it. I thought the files themselves were different. It's just 
how they're organized, right? So I can translate from the english ones as long 
as I save the whole thing in the new format. (like wabisuke said.)

Oh and since I'm in Canada, I guess it should be fr_CA? There are differences 
and I wouldn't want to confuse my fellow French from oversea. :)

And sorry for the long delay... I thought I was going to get an email when 
someone posted here. That'll teach me. ;)

JC

Original comment by Barma...@gmail.com on 6 Jun 2011 at 3:26

[GoogleCodeExporter]

That's okay, because it looks like mail wasn't getting out for some reason. I 
missed nicoluna's post -- sorry. In answer to his question, there needs to be 
an entry for each and every subdirectory. Example:

locale,install,url,jar:resource:/chrome/ja-JP.jar!/ja-JP/global/
locale,install,url,jar:resource:/chrome/ja-JP.jar!/ja-JP/communicator/
locale,install,url,jar:resource:/chrome/ja-JP.jar!/ja-JP/navigator/
locale,install,url,jar:resource:/chrome/ja-JP.jar!/ja-JP/necko/
... etc. Ditto for contents.rdf.

JC, yes, fr-CA probably is best. And yes, you just use the current format.

Original comment by classi...@floodgap.com on 6 Jun 2011 at 3:30

[GoogleCodeExporter]

Okay, I'll try next week (after some exams). Should I create es-ES (Spain) and 
another es-AR (Argentina, my country), or just es-ES? I am writing the files in 
neutral spanish, but I want to create an argentinian version too. What should I 
do?

Original comment by nicoluna...@gmail.com on 15 Jun 2011 at 9:54

[GoogleCodeExporter]

es-ES would be better. Remember that each pack is included with the distro 
currently, so this incurs more and more space to have locale-specific language 
variants. However, if there is a big difference and you're not sure that your 
translations wouldn't have regionalisms, then es-AR. I'd prefer only one or the 
other.

There is going to be a 9.2.3, but this is going to be a fast pushout to cover a 
couple of specific bugs since 9.3.0 is getting bogged down. If you have point 
changes to make, shout them out today as I'll be moving and the build MDD will 
be out of commission for a few weeks starting this week.

Original comment by classi...@floodgap.com on 3 Jul 2011 at 6:10

[GoogleCodeExporter]

I want to contribute to the spanish language.
My mail: gmail.com [at-inverse] abarcabahamondes

Original comment by abarcaba...@gmail.com on 6 Nov 2012 at 12:25

[GoogleCodeExporter]

Hi,
I would like to contribute to Classilla by translating it in Turkish. My e-mail 
address is: efnansekerogluu@gmail.com

Original comment by efnansek...@gmail.com on 13 Jun 2013 at 10:32