More localization

[HenningJ]

Ok, different localization stuff. :-)
This fixes issue #250.

Also, there were two functions that handled localization stuff. I refactored them into one.
NSBundle (BLTRExtensions) now handles the localization stuff. QSLocalization is still there, because there is still some weirdness going on. But less than before. :-)

[pjrobertson]

Testing this now.

[pjrobertson]

1. Problems with action names. They're just showing up as e.g. 'QSLoginItemAddAction'. In the command window and Triggers pref pane, actions pref pane etc. etc.

Probably just the localisation of some plugins.

But it is, for example breaking my 1Password action names. They're showing up as the actual method names 'goAndFill' instead of 'Go & Fill'

[HenningJ]

Ok, I'll have another look at it. Seems to be even more complicated than I thought :-/

[HenningJ]

I guess I was a little overzealous when providing fallback options for when a localization attempt failed. Should work better now.

[pjrobertson]

Seems good. I see you've just used no localisation for 'Type to Search' - is it a tough one to localise?

Haven't found any problems with this one, testing in various languages (French, English, Greek -> defaulting to German) and it's all good.
Except half the actions still aren't translated. We need to get working on that :/

Maybe we should make a wiki where people can contribute to the localisations?

I'll use this pull as my running QS for a bit just incase there are any oddities ;)

[HenningJ]

Seems good. I see you've just used no localisation for 'Type to Search' - is it a tough one to localise?

No, I didn't localize "Type to Search", because I actually didn't
localize anything. I just tried to fix parts of how localization is
handled.
But now that I think about it, I don't really know how to say that in German.

Haven't found any problems with this one, testing in various languages (French, English, Greek -> defaulting to German) and it's all good.

Wait, it's defaulting to German? It should default to English.

Except half the actions still aren't translated. We need to get working on that :/
Maybe we should make a wiki where people can contribute to the localisations?

Yeah...that's a major undertaking. :-/

[pjrobertson]

Haven't found any problems with this one, testing in various languages (French, English, Greek ->
defaulting to German) and it's all good.

Wait, it's defaulting to German? It should default to Englis

It's defaulting to the next language in the list in 'Language and Text' in
the prefs. I'd set it to Greek -> German -> British English
so I'd say it was doing the right thing in localising to German (since it
was next in my list)
I tried with Greek -> French and it was defaulting to French. This is how
OS X works if I remember correctly, so I don't see any problems with what
you've done :)

On 3 May 2011 22:29, HenningJ <
reply@reply.github.com>wrote:

Seems good. I see you've just used no localisation for 'Type to Search' -
is it a tough one to localise?

No, I didn't localize "Type to Search", because I actually didn't
localize anything. I just tried to fix parts of how localization is
handled.
But now that I think about it, I don't really know how to say that in
German.

Haven't found any problems with this one, testing in various languages
(French, English, Greek -> defaulting to German) and it's all good.

Wait, it's defaulting to German? It should default to English.

Except half the actions still aren't translated. We need to get working
on that :/
Maybe we should make a wiki where people can contribute to the
localisations?

Yeah...that's a major undertaking. :-/

Reply to this email directly or view it on GitHub:
#260 (comment)

[pjrobertson]

Seems sweet.
It's nice to have the 'type to search' text back. Makes QS that bit easier to understand... :)

[philostein]

Ouvrir should be spelled Ouvier in the French localization.

[jeanravin]

except it's in reverse ;) Apparently it's only misspelled in the triggers prefpane.

[pjrobertson]

Can you guys open a new support ticket for this? :)

Where exactly is the typo?

Thanks!

[jeanravin]

done
#554