Reduce compatibility breakage

[AntoineTurmel]

Once strings will be cleaned and divided into multiple files, some add-ons may not work anymore (giving yellow pages for an unfound .dtd or .properties file).

We should :

• Fix base add-ons
• Communicate to add-ons developers (blog post/mail)
• Create an article on bests practices on how to make add-ons localizable.

Since we are not changing strings ID, the developer will have to use songbird.dtd on Songbird, and feature.dtd on Nightingale. (Possible to detect if X software then use X .dtd ?)

What do you think @rsjtdrjgfuzkfg ?

[rsjtdrjgfuzkfg]

For add-ons compartible to both Nightingale and Songbird (which will become less and less as soon as we do some of the 2.x issues), I can think of this solution (not tested): The add-on should provide a import-songbird.dtd and a import-nightingale.dtd somewhere in chrome (probably content to not mess around with babelzilla?!). These dtd's should include the songbird.dtd or the required nightingale-one-feature-only-dtd(s). Then chrome overlay something like

overlay chrome://great-addon/content/import.dtd chrome://great-application/content/import-nightingale.dtd application=nightingale@getnightingale.com
overlay chrome://great-addon/content/import.dtd chrome://great-application/content/import-songbird.dtd application=songbird@songbirdnest.com

In XUL, use import.dtd which in theory loads the required sub-DTDs.

For the dtd include thing see also: http://stackoverflow.com/questions/6389741/including-a-dtd-in-another-dtd

[AntoineTurmel]

Oh ok well good idea :)

[AntoineTurmel]

Since POTI is dropping Songbird, I guess we could "force" developers to follow our new rules once we change L10n.

[ilikenwf]

Here's hoping we can get the addons and database, then we'd have all their emails.