Address book in (german) localized Trunks is broken



Mozilla Localizations
de / German
10 years ago
10 years ago


(Reporter: Nomis101, Unassigned)


Firefox Tracking Flags

(Not tracked)




10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_3; de-de) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.1 Safari/525.20
Build Identifier: Version 3.0a2pre (2008053003)

I have this bug only in the (german) localized versions of Thunderbird 3.0a2pre, not in the en-US version. If I click on the address book button I get the message:
"XML-Verarbeitungsfehler: Nicht definierte Entität 
Adresse: chrome://messenger/content/addressbook/addressbook.xul 
Zeile Nr. 205, Spalte 17: <menuitem id="menu_osxAddressBook" 
(in the german version).

The address book function in the compose window is not affected.

NOTE: I've tested this only with de, fr and en-US. I have this bug only in the german version. I have this bug not in en-US and in the french version. I've don't tested other localized versions yet.

Reproducible: Always

Steps to Reproduce:
1. Open a (german) localized version of Thunderbird (current Nightly)
2. Click the address book button
Actual Results:  
I get the message mentioned obove

OS X 10.5.3, PPC G4, Thunderbird Nightly Version 3.0a2pre (2008053003)
The patch that changed that was checked in yesterday (or the day before), en-US is the trunk so will have changed already, obviously fr have updated their versions.

Please give localisations some time to change things before filing bugs. They follow development but aren't synced up with it completely.

Moving to the appropriate localisation component.
Component: Address Book → de / German localizations
Product: Thunderbird → Mozilla Localizations
QA Contact: address-book →

Comment 2

10 years ago
I wait one day before filing this bug. But you are right, this bug is fixed in todays build. 
Sorry, next time I wait a little longer before filing a bug.


10 years ago
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.