[Caminol10n] status on camino 2

[Smokey Ardisson]

At 11:09 PM +0200 on  6/17/09, Stefan Livens wrote:

>Another question regarding the enormous amount of new strings in all 
>the global_locale_ .strings files. Do we realy need to translate 
>them all? Things like "Parsing an XSLT stylesheet failed." and 
>"Error in parsing value for property '%1$S'." (for css) have never 
>been visible to me in Camino. They are visible in Firefox, if you 
>have the error panel open.

The CSS and JavaScript errors show up in the Console if you have the 
hidden pref 
http://caminobrowser.org/documentation/hiddenprefs/#LogJStoConsole 
set, or if you're using a third-party add-on like ChimericalConsole.

The CSS errors, however, don't appear to ever reach the l10n system; 
I haven't yet had time to finish examining all of the files (and I'm 
not sure when I'll be able to do so).

>Second question: can't we reuse the translations from gecko and 
>firefox? I don't know in which format they are available, but sure 
>there must be some kind of mapping possible?

Did you see my message from the 16th? 
http://www.mozdev.org/pipermail/caminol10n/2009-June/002598.html  For 
most, but not all, of the files, you can borrow the Gecko l10n files 
and transform them yourself into the Cocoa strings format (you can 
see some of my early regexps that partially generated the current 
foo_locale_bar_properties.stings file in bug 
https://bugzilla.mozilla.org/show_bug.cgi?id=394105 ).

Smokey
-- 
Smokey Ardisson
alqahira at ardisson.org
http://www.ardisson.org/
------------------------------------------
"He is a fool who has forgotten what became of his ancestry
seven generations before him and who does not care what will
become of his progeny seven generations after him."
           --Kazakh Proverb