Suggest the following changes to the PreferencePanes in mozilla/camino/PreferencePanes (1.0rc1): Privacy: use "web sites" or "websites" consistently--currently the Cookies text says "web sites," but the Passwords text says "websites." Security: change "url field" to "Location bar" as that is how that element is labeled in the Camino UI and in the History PreferencePane. Web Features: add a comma after "moving" unless it is the usual practice to omit the comma before the last element in a series

Ah crud. The first two are real issues (and the label in the Cookies sheet says "Websites" too); the third one probably depends on whether the Europeans or the Americans are determining grammar rules in the Camino UI ;) We're string-complete for 1.0 now, but we'll get these for 1.1.

Also, in /Camino.app/Contents/Resources/English.lproj/Keychain.nib : Should use "smart" quotation mark and apostrophe characters (“ ” ’ instead of " " ') Also the same "website" / "web site" issue mentioned above. And the Tabs PreferencePane, at least, does not use quotation marks when referring to external apps (Keychain Access).

Ludo, this bug is about rewording some English text and can have l10n impact. What do you think? I'm inclined to minus this for 1.0.1 but do the easy polish for 1.0.2, but if you think you can be ready with the translations for 1.0.1, we might as well do this now.

(In reply to comment #3) > Ludo, this bug is about rewording some English text and can have l10n impact. Impact is minimal - But it would be easier to do it in a larger time frame. > What do you think? I'm inclined to minus this for 1.0.1 but do the easy polish > for 1.0.2, but if you think you can be ready with the translations for 1.0.1, > we might as well do this now. Minus is for 1.0.1 lets release 1.0.1 then first check in should be that one so my localizer have some time for 1.0.2.

Minused per comment 4. Requesting blocking for 1.0.2.

We've pretty much decided to stay string-frozen for 1.0.x unless we have to change something.

*** Bug 343057 has been marked as a duplicate of this bug. ***

Are we remembering to do comment 0 and comment 2 when fixing these?

question about smart quotes: why? do apple's HI guidelines require this?

Comments 0 and 2 have all been addressed in the nibs currently up for sr on the bugs in the depends list, so making this a regular meta. If there are issues with other dialogues, file separate bugs on each and set them to block this one.

Since the only remaining open bug in this meta (bug 359334) is targeted to 1.2, undepping and closing FIXED.