387065 - [l10n] Portugese localization non-functional due to incorrectly-named lproj

Status: RESOLVED FIXED

(Camino Graveyard :: Translations, defect)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

The Portugese localization in 1.5 (technically it's Brazilian Portugese) doesn't work in 1.5 ML (v1 or v2) because the .lproj folder is mis-named.

It's named "Brazilian Portugese.lproj", which is not a recognized .lproj name in Mac OS X.  Renaming the folder to "Portugese.lproj" (or "pt.lproj") allows the localization to be used with any of "Português", "Português de Portugal" or "Português do Brasil" set as the system language.

(If we want to restrict this version to only work when "Português do Brasil" is the preferred system language, the .lproj can be named "pt_BR.lproj" instead.)

(In addition, the next respin of the ML package needs to get rid of the "Plugin.plugin" folder inside the root of Camino.app.)

Since we haven't announced 1.5 ML v2 due to holidays and Sam being on vacation, I think we'll hold off on announcing it, and once a v3 is ready with the fix for this bug and distributed to the mirror network, announce 1.5 ML v3 instead.

Comment 1

[Marcello Testi]

AFAIK the pt_BR l10n is purposedly not recognizable by pt_PT users.
I don't have the knowledge to tell. I can surely change the name of the folders in a little while (tomorrow) and get rid of the Plugin folder

Comment 2

[Stefano]

I've discovered this issue these days on a Mac OS X 10.3.9. The translation haven't been recognized until I delete all languages except Brazilian Portuguese but it strangely worked on my Mac OS X 10.4.10 without any problem.

Marcello, could you please change the .lproj's name to "Portugese.lproj"? Since we won't find anyone to continue Paulo's efforts until next version, this is the best option. Both pt_PT and pt_BR are similar so I think it would be much better for a Portuguese person to have this translation than don't have any translation at all.

Comment 3

[Marcello Testi]

I just changed the folders name to pt.lproj which seemed safer to me than Portugese or Portuguese. What about this note in the RTF file where available translations are listed?
[...]
Portuguese***
[...]
*** In v2 accessible both by Portuguese and Brazillian users

Comment 4

[Marcello Testi]

Stefano, you probably might want to add a few lines on top of your "Notas da Versão" file specifically for Portuguese users

Comment 5

[Stefano]

(In reply to comment #3)
> I just changed the folders name to pt.lproj which seemed safer to me than
> Portugese or Portuguese. What about this note in the RTF file where available
> translations are listed?
> [...]
> Portuguese***
> [...]
> *** In v2 accessible both by Portuguese and Brazillian users
> 

I just think using Portuguese.lproj is better than pt.lproj because the regular user just does not know what language is pt but it will obviously knoww what is Portuguese and will then make its choice regarding the language on SHOW INFORMATION dialog without confusion.
I'm almost 100% sure that changing to Portuguese won't mess everything and the result will be the one we want.

Comment 6

[Stefano]

(In reply to comment #4)
> Stefano, you probably might want to add a few lines on top of your "Notas da
> Versão" file specifically for Portuguese users
 
Telling what, Marcello? I didn't get your point...

Comment 7

[Stuart Morgan]

(In reply to comment #5)
> I just think using Portuguese.lproj is better than pt.lproj because the regular
> user just does not know what language is pt

Under what reasonable circumstances would an end-user be looking at the lproj folder names?

Comment 8

[Stefano]

(In reply to comment #7)
> Under what reasonable circumstances would an end-user be looking at the lproj
> folder names?
 
An end-user would never be looking at lproj folder names, Stuart, but at the languages available on a application by right clicking its icon and clicking on GET INFO item.
I think many end-users may use this dialog to choose the language they what as the default on any application.
Here is a pic showing the window I'm talking about: http://web.omnidrive.com/APIServer/public/GD0mpU67tH02oBAQEkdxsKwO/get_info_dialog.png

Comment 9

[Stuart Morgan]

Ah, sorry, I hadn't realized that that was using the actual folder names. That's pretty lame, since the system has a mapping from those codes to language names anyway.

Comment 10

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

At least on 10.3.9, "Portugese" and "pt" are completely interchangeable as .lrpoj names in my testing.  Someone should verify on 10.4, but I'm hopeful Apple didn't break this there.

1) Set each of the 3 Portugese options (in turn) in the International System prefs topmost and something totally different (English) second
2) Launch a Camino ML with a "Portugese.lproj"
3) Ensure you have the expected (Portugese) Camino localization each time

Comment 11

[Marcello Testi]

(In reply to comment #6)
> Telling what, Marcello? I didn't get your point...

That your translation is made with a Brazillian vocabulary, so Portuguese people may find some words that they're not used to.

Comment 12

[Stefano]

(In reply to comment #11)
> That your translation is made with a Brazilian vocabulary, so Portuguese
> people may find some words that they're not used to.

Ok! Good idea, Marcello. I'm going to send you a new version of Release Notes with information to Portuguese users along with a translation to English so you can make your considerations by the end of this week.

Comment 13

[Stefano]

(In reply to comment #10)
> At least on 10.3.9, "Portugese" and "pt" are completely interchangeable as
> .lrpoj names in my testing.  Someone should verify on 10.4, but I'm hopeful
> Apple didn't break this there.

With my Mac OS X 10.4.10 everything worked as expected and passed on your test. This mean all 3 Portuguese variations of Mac OS made Camino launch with the translation I worked on.

Comment 14

[Stuart Morgan]

This is FIXED as of the 1.5.1 we've staged, right?

Comment 15

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

FIXED in 1.5.1; thanks all.