Which is easier for you?

[Christopher Forsythe]

Folks,

We're working on the 1.3 interface, and wanted to ask a question. The interface will have a lot of changes with regards to how things look, and there should be a decent amount of additions and removals of localizable strings.

So, which is easier? Is it easier to retain the existing localizations and update them to the new UI look and strings? Or is it easier to remove the current localizations and the provide you guys with a window for all new localizations?

Also, if we start all over, is iLocalize still the best solution for you guys and girls?

Chris

[Eugen Mihalache]

Easier is to remove the current localizations and to provide a window for all new localizations. iLocalize won't help. 

Kind regards. 

Eugen M. 

Via iPhone

--
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.

[jpk]

On 18 juil, 05:54, Christopher Forsythe <ch...@growl.info> wrote:
> So, which is easier?

For me, what is the easiest is to get a new version of the app with an
English.lproj folder with non-compressed files (.nib etc).
Si I can use iLocalize to compare it with an already localized version
(1.2.1 for me now) and find what to change for the new version.

With so a process I can use all my previous effort: already localized
strings, layouts, etc.
I can use glossaries too to keep coherent translations as much as
possible.

[Chris Forsythe]

We're changing a lot of the layout in 1.3, and likely even more in 1.4. I don't know if the effort taken now on 1.2.x would be worth it or not.

As soon as we have something for you guys to start localizing, my intention is to have this done right and give you guys a 1 week window to get things done.

What I'm likely going to do is send out a call for localizers, and then email those who respond separately with a link to a download to be localized, once the interface is finalized. I do not believe that we'll be using previous localizations, so if you have any friends who know any other languages and like to localize products, now is the time to let them know to start getting in touch.

I expect that this will be some time near the end of August, but that may still change.

[Alexander Henket]

(:happy:) Progress!

I hope that people who have been contributing in the past are still up to it. If they are, the number of responses should be overwhelming

Alexander

[Søren Palmund]

If you're making major changes to the UI, I recon that the best way to
proceed would be to push the non-compressed nib-files containing the
the new UI, so localizers can start afresh.
Using non-compressed nib-files means that future versions of Growl
introducing new strings or layout can easily be translated.

I'm up for doing the Danish translation.

[Chris Forsythe]

You keep saying "non-compressed nib-files". Do you mean ones which are editable?

Chris

[Søren Palmund]

Yeah. Editable nibs. So iLocalize can read them.

[Chris Forsythe]

Ah, good. Yes I believe this is what we will be doing.

Chris

[jpk]

On 5 août, 21:43, Chris Forsythe <ch...@growl.info> wrote:
> On Aug 5, 2011, at 3:57 AM, jpk wrote:
> > For me, what is the easiest is to get a new version of the app with an
> > English.lproj folder with non-compressed files (.nib etc).
> > Si I can use iLocalize to compare it with an already localized version
> > (1.2.1 for me now) and find what to change for the new version.

> ...

> We're changing a lot of the layout in 1.3, and likely even more in 1.4. I don't know if the effort taken now on 1.2.x would be worth it or not.

I get the "Growl.app" 1.3.0b1 package to localize.
I find in it a French.lproj.
It is almost good.

It seems that the localization work will be not big to update to
1.3.0.
Do I miss something?

[Chris Forsythe]

Not at all. We left the translations from 1.2.2 in there, hoping to run into situations like this where not a lot has changed in certain portions.

You'll notice changes in the General and Network tabs mostly from 1.2.2 to 1.3, with regards to strings.

Chris

[jpk]

On 4 sep, 20:46, Chris Forsythe <ch...@growl.info> wrote:
> Not at all. We left the translations from 1.2.2 in there, hoping to run into situations like this where not a lot has changed in certain portions.

Ok, thanks.
As the translation.folders are no more synchro with the new original
English.lproj folder, a better way would be to start a new iLocalize
project and then to do the first translation using glossary.

[jpk]

On 4 sep, 21:01, jpk <Kuyp...@swing.be> wrote:
> As the translation.folders are no more synchro with the new original
> English.lproj folder, a better way would be to start a new iLocalize
> project and then to do the first translation using glossary.

Building a new iLocalize project based on the 1.1.5 version and using
its English.lproj and French.lproj folders, then updating the project
with the 1.3.0b1 package, it seems that I can re-use a lot of my
previous works. Great!

[Chris Forsythe]

That's really good news, and hopefully true for others who are picking up on languages we previously had. Hopefully things on the development side are just as easy. :)

[Chris Forsythe]

I don't think I understand what you mean by this (other than you're making a suggestion to make things easier).

My reading of the iLocalize help for translators was that sending you the .app was the best way to go. Was that wrong? Or is this suggestion for people who are translating Growl currently? If so I can start an off list thread so that everyone knows (not everyone is on this list).

[jpk]

> On Sep 4, 2011, at 2:01 PM, jpk wrote:
> > As the translation.folders are no more synchro with the new original
> > English.lproj folder, a better way would be to start a new iLocalize
> > project and then to do the first translation using glossary.
>

On 4 sep, 21:24, Chris Forsythe <ch...@growl.info> wrote:
> I don't think I understand what you mean by this (other than you're making a suggestion to make things easier).
>
> My reading of the iLocalize help for translators was that sending you the .app was the best way to go. Was that wrong?

Sorry for the confusion.
Nothing wrong, Chris.

My first note was after I see that the French.lproj folder was not
synchro with the English.lproj one.
So it was not obvious to use this French.lproj folder to start the
updating of translation of the new Growl.
Indeed iLocalize didn't note the changes.

So a way could be to create a new iLocalize project with only the base
language (English), then to add a new language and to do the first
translation using glossary/ries (if any).

Then I discover the way to use a previous already localized version
(with non compressed .nibs) to create a project using the base and the
target languages, and then updating the project using the 1.3.0.b1
package. With this second way I can use more previous works (strings
already translated and notes of the changes).

Sending the .app as you did is the best way, sure!
The localizators must note that the languages.lproj folders are from a
previous release, and not from the 1.3.0b1 one.