Wow solutions everywhere
Well, as I cannot judge about code I will state my opinion as a translator
and from I have seen I must say that I prefer Teo's proposition.
(*though it seems not fully functional: I have tried to test but encountered that probable css issue on the extended settings dialog )
Reasons why I think a html in a locale is not such a good idea :
1. Even though you removed a certain number of tags, translators would have to slalom around "strange" things such as <li>, <ul> and <a href.
. Of course it is nothing for old translators like me, but one big idea of BabelZilla is to make translation an easy non-technical game
So I would prefer to spare them the handling of an html file: use the proper html editor that will not break the encoding, beware not to translate what should not be, beware not to delete one closing tag here and there etc.
2. The size of an html file in every locale (and you know that this extension will probably get more than 20 language subfolders) is more important than the .dtd with corresponding strings. 20 times a small difference becomes significant difference.
If you stick to your idea the solution could be (my little howto here):
- have one .X
html file in the content
- entitize its strings
- drop the entities and strings in the locale .dtd file
About your reluctance to modify your plans to match wts limitations: you are right of course
You should not lose your time trying to adjust good work to annoyances, I understand perfectly. Note that the next version of the WTS will allow to edit html online (as html code, so it is not as good as wysiwyg for non-geek translators)
So I think in this case Teo's solution (*IF it matches code standards and is functional) can be better. My 2 GoofyCents.