428859 - Missing translations in Camino 1.6 German

Status: RESOLVED FIXED

(Camino Graveyard :: Translations, defect)

Description

[Marcello Testi]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; it; rv:1.8.1.13) Gecko/20080327 Camino/1.6b4 (like Firefox/2.0.0.13)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; it; rv:1.8.1.13) Gecko/20080327 Camino/1.6b4 (like Firefox/2.0.0.13)

The following files are not translated in the provided l10n:
- Frameworks/SharedMenuCocoa.framework//Resources/InfoPlist.strings
- MacOS/components/talkback/Talkback.app/Resources/Localizable.strings
- MacOS/plugins/Default Plugin.plugin/Resources/InfoPlist.strings
- MacOS/plugins/JavaEmbeddingPlugin.bundle/Resources/InfoPlist.strings
- MacOS/plugins/MRJPlugin.plugin/Resources/InfoPlist.strings
- Resources/FeedHandlers/BloglinesFeedHandler.app/Resources/InfoPlist.strings
- Resources/FeedHandlers/GoogleFeedHandler.app/Resources/InfoPlist.strings
- Resources/FeedHandlers/MyYahooFeedHandler.app/Resources/InfoPlist.strings


Reproducible: Always

Comment 1

[Tobias Stohr]

Attachment: Talback.app Localizable.strings

Here is Localizable.strings for Talkback.app. Somehow iLocalize managed to write an empty file. Sorry for that!

Regarding the Info.plist files:
I don't think it's necessary to translate them since they only contain copyright information and in most cases a Camino user won't notice their existance at all.
If you want them though, just tell us.

Comment 2

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

The InfoPlist.strings files should be mostly copy/paste.  

I'm not sure what the effect of not having language-appropriate InfoPlist.strings files for the feedhandlers is, since those strings are used in the UI; I'd be much more comfortable with user experience quality if we had those three.

Comment 3

[Tobias Stohr]

Attachment: The missing InfoPlist.strings files.

Here are the missing InfoPlist.strings files for Camino 1.6 German language bundle.

We should figure out if they are needed (I didn't experience any problems so far). If they aren't needed, we could save some space.

Comment 4

[Stuart Morgan]

(In reply to comment #3)
> We should figure out if they are needed

If they aren't there, the English files will be used. We could look into the
possibility of changing JEP and MRJPlugin to drop "version" and "copyright"
(just using the symbol), moving everything into Info.plist, and dropping that
file entirely. SMC has actual text; we could decide that we don't care about
translating it potentially, since we don't expect the user to see it.