|
|
Fixing Quicksilver Localizations: msg#00113
os.macosx.quicksilver.user
|
Subject: |
Fixing Quicksilver Localizations |
I fixed some typos in the branch recently, so now more stuff shows up
as localized in the interface ;-). Quicksilver just needs a
localization update for some of the stuff, but I think there's a need
to redesign how localization is handled in the code, so it's in
waiting line...
By the way, I need some help on localization. I need to complete all
missing keys for the English localization, so they can be used as a
starting point for other languages. So here's a quick guide on how to
do this :
If you want to check which stuff isn't localized, try setting
QSDebugLocalization in the environment. It will output line with the
format "Localization: Missing key %@ in table %@, using default %@" in
the console each time a localized key is missing. Then you can
manually add it to the corresponding .strings file (There are a bunch
of those, but the file name is indicated by the table in the log
message. The problem with this approach is that you don't have a
direct way of knowing to which plugin belongs which key, and I want to
keep localization separate).
If someone is interested in writing some patches for the
aforementioned files, I'll be happy to apply them ;-).
|
|