The DTD files in XPI archives may contain "external entities," which look like:
<!ENTITY % platformDTD SYSTEM "chrome://browser/locale/help/platformStrings.dtd" >
These need to be preserved in output, along with their ordering. There is probably no need to resolve them on import (especially if the referenced file is a DTD file with a chrome path, because it will be parsed anyway).
It's considered good practice to keep the use of these external entities uniform between translations (so if one locale uses an external entity, another locale will also use it). There is nothing to guarantee this, however.
The DTD files in XPI archives may contain "external entities," which look like:
<!ENTITY % platformDTD SYSTEM "chrome: //browser/ locale/ help/platformSt rings.dtd" >
These need to be preserved in output, along with their ordering. There is probably no need to resolve them on import (especially if the referenced file is a DTD file with a chrome path, because it will be parsed anyway).
It's considered good practice to keep the use of these external entities uniform between translations (so if one locale uses an external entity, another locale will also use it). There is nothing to guarantee this, however.