String changes expected in Camino 2.1

This post will list documented/expected string changes for Camino 2.1.

Bug 569280 - The print dialog settings have moved. A new set of strings is going to appear in the main Localizable.strings file

Bug 534809 - The %s string placeholder in the cookies sheet/dialog has been replaced with %@

Bug 594672 - VersionTracker was replaced by MacUpdate in the default bookmarks, and the URLs for BBC News and Mac OS X Hints were updated

Every localizable Gecko string used in Camino can now be localized; you should be able to ship a 100% localized Camino 2.1 to all of your fellow speakers.
Unfortunately, a few of these files have to be localized in their original Gecko formats (.properties, .dtd) rather than in typical Cocoa .strings:
config.dtd (about:config)
global.dtd (text direction; only needed if you're a right-to-left language)
mozilla.dtd (about:mozilla)
netError.dtd (error pages)
prettyprint.dtd (XML parsing errors)
plugins.dtd (blocked or disabled plug-ins)
typeaheadfind.properties (find-as-you-type)
caps.properties (assorted security strings)
These files are all found in Camino.app/Contents/Resources/*.proj/; iLocalize will bring them over to the localized Resources folder, but hasn't got an UI for translating them (just drag them to a text editor of choice).
global.dtd (only needed if you're a right-to-left language), mozilla.dtd, prettyprint.dtd, and caps.properties can use the corresponding files from your language from http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/
Location of files inside localized mozilla packages:
toolkit/chrome/global/config.dtd (about:config)
dom/chrome/global.dtd (text direction; only needed if you're a right-to-left language)
toolkit/chrome/global/mozilla.dtd (about:mozilla)
dom/chrome/netError.dtd (error pages)
dom/chrome/xml/prettyprint.dtd (XML parsing errors)
toolkit/chrome/mozapps/plugins/plugins.dtd (blocked or disabled plug-ins)
suite/chrome/common/typeaheadfind.properties (find-as-you-type)
dom/chrome/security/caps.properties (assorted security strings)
config.dtd, netError.dtd, plugins.dtd, and typeaheadfind.properties all contain Camino-specific changes, so you cannot reuse the corresponding Gecko files (you may be able to use them as a guide in some cases). Note also that in plugins.dtd, you only need to translate the 4 strings (entities) immediately following "CAMINO LOCALIZATION NOTE".

In terms of new or changed *_properties.strings files (over what was shipped in Camino 2), the Cocoa l10n tools should pick up that they need changes, but they are:
global_locale_css_properties.strings.in
global_locale_dom_dom_properties.strings.in
global_locale_plugins_properties.strings.in
global_locale_svg_svg_properties.strings.in
pipnss_locale_pipnss_properties.strings.in

The JEP has been removed from Camino 2.1b1, so the InfoPlist strings from those bundles should disappear if you localized them before.