Selon Denis Barbier <barbier(a)linuxfr.org&gt;: Consider me out of the picture until the end of the assistant lecturer recruiting period in France, by end June. Sorry about that. That's appleaing, but I prefere to see the problem than hiding them that way. The best solution would be that you modify the Sgml.pm file to fit your needs. I would mainly consist in adding missing tags in the right categories. The rest should not need to be changed, but if you see any improvement, please inform us. Then, send us the result for inclusion, so that your work can benefit to next ones. First answer: If you *improve* tagging, that's a bug in the original which should be repported and fixed. That's the best way to fix structure discrepancy. A diff-like algorithm is planned to continue in case of structure discrepancy (like in po-debiandoc, if I remember well), but still to do. addenda are more adapted for the addition of large chunks of text, such as sections. For simple tag addition, feel free to add them into the msgstr. Similarly, you could add a <b> tag to a translation with no harm (that I can predict). Yes, using po4a-gettextize always imply some sort of butchery on the files to make their structures match. You may have to remove parts of the original and of the translation. Do not be affraid to do so. The most important is to manage to get a po file. Once it's done, you may reintroduce the removed parts. If it's in the master, you'll get empty translations for them. If it's in translation, you are free to add them in msgstr OR use the addendum mecanism, depending on the size of the removed blocks and on what you prefere. Good luck, Mt.