Growl localizations submitted but never integrated

3 views
Skip to first unread message

YR

unread,
Jul 9, 2010, 11:11:42 AM7/9/10
to Growl Localizations
Hello,

I discovered the recent release of Growl 1.2.1 and I am again
disappointed concerning the (missing) integration of my localization
works. Some discussions with other localizers tend to demonstrate this
is not a isolated case.
(I also read
http://groups.google.com/group/growl-localizations/browse_thread/thread/caaadca7a872de85
)

My case:
- I have been regularly submitting French localizations for months
(years...) concerning
HardwareGrowler, GrowlMail, GrowlSafari and GrowlTunes:

http://groups.google.com/group/growl-localizations/browse_thread/thread/bffeaf6eadd20e90
http://groups.google.com/group/growl-localizations/browse_thread/thread/3122e95dbe7d6e4b
http://groups.google.com/group/growl-localizations/browse_thread/thread/61ba1f17c0838738
http://groups.google.com/group/growl-localizations/browse_thread/thread/3122e95dbe7d6e4b

(Growl itself being localized by a contact I know, that explained me
being in the same disappointing situation as me)

- but most of my updates have never been integrated... For instance,
the current French translation of HardwareGrowler is one of my early
works from... june 20th, 2008 !!! All of my next updates posted here
seem to have been ignored.

- Meantime, I've read that a new localization process for Growl was
under definition and it made sense to wait. But I think that two years
ignoring corrections is far too long for users to get the necessary
corrections (sometimes it's really big misspellings awfully visible
every day! It does not give a very serious image of the product...)

=> So I am wondering:
Is there any problem with the way we submitted previous localizations?
If a new localization process is under work, isn't there any hope to,
at least, integrate the localized files that simply need to replace
the released files to work?

That would be very nice for the users of translated versions...
I can re-submit localization files concerning the current release
1.2.1, hoping they will be integrated, but I worry.... ;-)

Christopher Forsythe

unread,
Jul 9, 2010, 11:24:03 AM7/9/10
to growl-loc...@googlegroups.com
To be honest, localization has never really been a priority for the Growl Project. While it is nice, and we've tried, we don't have someone who is focused, knows the localization process, knows how to work with code, test out the localizations once submitted, etc etc etc.

That's what I was hoping we'd aleviate with the automation I was thinking we would get with that whole discussion you link to.

I would love to say that "hey, we'll make this right!", but I've been saying that for years.

I'm not sure how to address this yet, but we'll come up with something to make this a bit of a better process, which will hopefully lead to localizations getting processed and not ignored.

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.


Christopher Forsythe

unread,
Jul 9, 2010, 12:15:09 PM7/9/10
to growl-loc...@googlegroups.com
Are there any updates besides these ones you link to that we missed?

Chris

YR

unread,
Jul 9, 2010, 5:09:45 PM7/9/10
to Growl Localizations
On 9 juil, 18:15, Christopher Forsythe <ch...@growl.info> wrote:
> Are there any updates besides these ones you link to that we missed?
>
> Chris

No other links.
As far as I am concerned, these are all the most recent ones
concerning each Growl Extra I worked on.

Thank you very much.
Reply all
Reply to author
Forward
0 new messages