Growl localizations submitted but forgotten

[Yann Ricquebourg]

Hi all,

Unfortunately, as already described in july 2010 (and normally solved?)
http://groups.google.com/group/growl-localizations/browse_thread/thread/b55eac18925858b
previous updates to my own earlier French translations of several growl extras have been ignored
while they have been submitted a long long time ago.

Hardware Growler http://groups.google.com/group/growl-localizations/browse_thread/thread/bffeaf6eadd20e90
GrowlTunes http://groups.google.com/group/growl-localizations/browse_thread/thread/b0a67f3131089e77
GrowlMail http://groups.google.com/group/growl-localizations/browse_thread/thread/3122e95dbe7d6e4b
GrowlSafari http://groups.google.com/group/growl-localizations/browse_thread/thread/61ba1f17c0838738

They are still forgotten in the last Growl package released a few days ago, thus leaving remaining misspellings,
mistakes, or not yet translated texts.
Is there a mistake somewhere?
I resend them (attached to this message) hoping they will at last be included (dated from 2009 ;-))

Regards,

-yann.

[Christopher Forsythe]

We are still not accepting localizations at this time. We have not because there is not an easy way to do so with regards to Growl and xibs. We'll continue down this path until there is one.

Chris

--
You received this message because you are subscribed to the Google Groups "Growl Localizations" group.
To post to this group, send email to growl-loc...@googlegroups.com.
To unsubscribe from this group, send email to growl-localizat...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growl-localizations?hl=en.

[Yann Ricquebourg]

Hello Chris,

Christopher Forsythe wrote on 02/06/11 at 01:50

> We are still not accepting localizations at this time. We have not because there is not an easy way to do so with regards to Growl and xibs. We'll continue down this path until there is one.
>
> Chris

I can imagine that, but that was not really my point ;-)
I'll precise it:

As described in a previous message about one year ago (July 2010), you seemed personally
to have taken the "miss" into account (but no change in fact up today):

> http://groups.google.com/group/growl-localizations/browse_thread/thread/b55eac18925858b

And as I wrote in this message, even if I can imagine that the localization process is
"not accepted at this time", I am quite "frustrated" that it was then never accepted over a
period starting in... 2009 ;-) (because my last submitted localized but never integrated file was
in october 2009).

During those two years, the four concerned Growl extra contain in French visible misspellings and
some texts still existing not translated mixed with French... Then my "old" message of 2010 and this one
of 2011 was just to mention that it's quite a pity for the users from 2009.

> Hardware Growler http://groups.google.com/group/growl-localizations/browse_thread/thread/bffeaf6eadd20e90
> GrowlTunes http://groups.google.com/group/growl-localizations/browse_thread/thread/b0a67f3131089e77
> GrowlMail http://groups.google.com/group/growl-localizations/browse_thread/thread/3122e95dbe7d6e4b
> GrowlSafari http://groups.google.com/group/growl-localizations/browse_thread/thread/61ba1f17c0838738

The concerned files are:
3 oct 2009 HardwareGrowler-1.2_fr.lproj.zipfile
3 oct 2009 GrowlTunes-1.2_fr.lproj.zipfile
3 oct 2009 GrowlMail-1.2_fr.lproj.zipfile
3 oct 2009 GrowlSafari-1.2_fr.lproj.zipfile

Nevertheless, I can accept that from October 2009 there were no periods for localization process,
but have you an idea when the current Growl package (I'm not speaking of a future re-worked version
or some really deep implementations) could accept final translation corrections?

(BTW I noticed that the Googlegroups can't accept uploaded files anymore? and that my e-mail message
to the list yesterday removed the small attached files... So what's the best way to supply files?
Nevertheless the above mentioned four zip files are still available in the Googlegroup till...
this summer 2011, according to Google new policy ;-)

Regards,

-yann.

[Christopher Forsythe]

On Thu, Jun 2, 2011 at 2:36 AM, Yann Ricquebourg <yann.ric...@gmail.com> wrote:

Hello Chris,

Christopher Forsythe wrote on 02/06/11 at 01:50

> We are still not accepting localizations at this time. We have not because there is not an easy way to do so with regards to Growl and xibs. We'll continue down this path until there is one.
>
> Chris

I can imagine that, but that was not really my point ;-)
I'll precise it:

As described in a previous message about one year ago (July 2010), you seemed personally
to have taken the "miss" into account (but no change in fact up today):

>     http://groups.google.com/group/growl-localizations/browse_thread/thread/b55eac18925858b

At no time here did I say "we'll get right on that and update these!". You just assumed. Our localizations acceptance is still paused.

If we can't come up with something by 2.0, we're most likely going to drop localizations since the prefpane will be changing dramatically.

 

And as I wrote in this message, even if I can imagine that the localization process is
"not accepted at this time", I am quite "frustrated" that it was then never accepted over a
period starting in... 2009 ;-) (because my last submitted localized but never integrated file was
in october 2009).

I'm frustrated with localizations in general. There is no simple process to do it. I understand that you put some work into this, but the amount of work that we have to put in on the rest of it requires another resource at this point that we simply haven't had for more than 2 years.

No one has stepped up to volunteer to do this work.

 

During those two years, the four concerned Growl extra contain in French visible misspellings and
some texts still existing not translated mixed with French... Then my "old" message of 2010 and this one
of 2011 was just to mention that it's quite a pity for the users from 2009.

>     Hardware Growler http://groups.google.com/group/growl-localizations/browse_thread/thread/bffeaf6eadd20e90
>     GrowlTunes http://groups.google.com/group/growl-localizations/browse_thread/thread/b0a67f3131089e77
>     GrowlMail http://groups.google.com/group/growl-localizations/browse_thread/thread/3122e95dbe7d6e4b
>     GrowlSafari http://groups.google.com/group/growl-localizations/browse_thread/thread/61ba1f17c0838738

The concerned files are:
3 oct  2009 HardwareGrowler-1.2_fr.lproj.zipfile
3 oct  2009 GrowlTunes-1.2_fr.lproj.zipfile
3 oct  2009 GrowlMail-1.2_fr.lproj.zipfile
3 oct  2009 GrowlSafari-1.2_fr.lproj.zipfile

Nevertheless, I can accept that from October 2009 there were no periods for localization process,
but have you an idea when the current Growl package (I'm not speaking of a future re-worked version
or some really deep implementations) could accept final translation corrections?

The current version releases is the last 1.2 version that we will be putting out. We're working on 1.3 only at this point. If a simple process for localization comes up then we'll start including localizations. Alternatively, if we have someone step forward who will do the work on these, then we'll accept localizations.

 

(BTW I noticed that the Googlegroups can't accept uploaded files anymore? and that my e-mail message
to the list yesterday removed the small attached files... So what's the best way to supply files?
Nevertheless the above mentioned four zip files are still available in the Googlegroup till...
this summer 2011, according to Google new policy ;-)

Ya, they turned it off without consulting anyone. It's annoying.

I do not have a new place for you guys to send localizations. Note that this is some of the work I'm talking about above.

 

Chris

[Peter Hosey]

On Jun 2, 2011, at 15:56:26, Christopher Forsythe wrote:
>> (BTW I noticed that the Googlegroups can't accept uploaded files anymore? and that my e-mail message to the list yesterday removed the small attached files... So what's the best way to supply files?
>> Nevertheless the above mentioned four zip files are still available in the Googlegroup till... this summer 2011, according to Google new policy ;-)
>
> Ya, they turned it off without consulting anyone. It's annoying.
>
> I do not have a new place for you guys to send localizations. Note that this is some of the work I'm talking about above.

The best place, once we start accepting localizations (not yet!), would be either Google Docs, MobileMe/iCloud, or Dropbox, or your own web-accessible storage if you have it.

I, for one, will not accept/apply any localization submission stored on Rapidshare, MegaUpload, etc. Those sites are too annoying.

[Christopher Forsythe]

I did bring back up the thread on the ilocalize mailing list to ask for an update.

Chris 

[Eugen Mihalache]

As I said several months ago, if you send us Growl.xcodeproject file, everything will be done.

But I guess you don't want that.

If you don't want, just tell us.

We will accept it.

As a developer for Macintosh Platform you need to know this; 

- you can localize or put the localization for an app right from/in the .m file. 

- there's no need to write something in the .xib file, only to link it to it is enough.  

Eugen M. 

Via iMac

[Christopher Forsythe]

I don't remember this email that you say you sent.

Please go into much, much more detail about how this would work.

Chris

[Eugen Mihalache]

Here the old eMail. 

----------------------------------------------------------------

On Feb 13, 2011, at 11:49 PM, Eugen Mihalache wrote:

I would like to translate the GROWL into romanian language.
Send me please the Growl.xcodeproject file and in 24 hours you have it
back with the romanian language on it.

Kind regards

Eugen Mihalache

--

----------------------------------------------------------------

[Christopher Forsythe]

That provides no details as to exactly how that would get 30+ localizations translated. I'm not interested in something where I have to manually send you large amounts of files. This is not a viable solution for us if that's what you're proposing.

Chris

[Eugen Mihalache]

I understand very well. 
I'm sorry thats not helping. 

Then we'll not have a localization.

Via iPhone