issue-#113 XhtmlExporter bug with StdLinks.Target

[Josef Templ]

This is best way. How did you get window title from TextView?

I looked for inspiration and found it in StdHeaders.
It is possible to enumerate all windows and select the one that
displays the converted document. There is no way back from the text view
to the window.

The html encoding of attributes has now also been added.
From my point of view this issue is ready for voting.

- Josef

[Zinn]

Josef,

your version is a great improvement. For a really useful small tool there are two important parts missing.
They are the element list <ul> <li> and the elment header <h1> ... <h5>.
We can add them in the same way as XhtmlTextTableMarker by creating XhtmlTextListMarker and XhtmlTextHeaderMarker.
Do you prefer to have separate modules or to have one module for those tasks?
Should we have different end marker or one end marker for all in common?

- Helmut

[Ivan Denisov]

I think, that this should be separate features issue with html markers and so on. We can continue work with this new issue, however it will be aimed to 1.8.

[Josef Templ]

I agree with Ivan. This is beyond version 1.7.

The very rudimentary table support by means of the special marker views
is an undocumented feature and not well suited as a blueprint for more such features.
It is so limited that it is useless and it must stay undocumented.

Instead of introducing special marker views for special exporters,
It would of course be great if BB supported tables, named styles, bulleted and numbered lists etc.
in the standard text model. Then it would be possible to convert that to html (or other target formats) without
any special markers. The creativity should be invested towards extending the standard
text model or introducing new standard views similar to StdLinks.Link/Target.

- Josef