The problem is not to extract these information from the pad, but how
to put in in the export format, e.g. the html-export.
I thought about the possibility of writing a generic xml export, which
exports all attributes of the attribute pool and binds these
attributes (and the values) to the corresponding text ranges. The
output of such an xml export could than be transformed in anything
else.
Using xml as an intermediate export result would allow to create one
well-engineered export module and let other exporters just use the xml
instead of working on the attributed text directly.
Just a suggestion.
I have written a LaTeX export modul from scratch some months ago.
Refactoring this code to export xml instead of LaTeX is no big deal. I
will have a look at this next year :)
Cheers and happy holidays!
2011/12/22 Peter Martischka <peterma...@googlemail.com>: