AW: HTML rendering in Mozilla

Hi Sandro

Nice to hear from you again - on the list as well:)

>> What would HTML help for implementing that? Or asked differently, what
>> can't be done in XML for footnotes, which you think would be easier in
>> HTML? I'm just wondering, to see if we go into the right direction.
>
>Remember our last talk? The problem with DocBook-like footnotes in
>BXE is that
>BXE can currently display XML elements in the given sequence only.
>It is not
>possible to display footnotes, which appear inside a DocBook paragraph (or
>block in general), at the end of the Browser page.
>
>This is due to the fact that BXE transforms
>
>XML -> CSS -> Browser Display
>
>instead it should be
>
>XML -> XSLT -> HTML -> CSS -> Browser Display

I am not sure at all that this is problem with footnotes. IMHO, we would
need some sort of popup (like for the ulink) where you can write the content
your footnote. And then display it at the end of the page. This can be done
with CSS as well.

Another problem is counting your footnotes through. But there maybe is a
trade-off, do you want to have your footnotes displayed immediately or
should the XSLT have to calculate quite a bit.

Still I am not religious to the CSS only way (and I think there have been a
misunderstanding to oppose XSLT and CSS to strongly) - I better would call
our method a hybrid one - use XSLT or CSS where it makes most sense. For our
projects so far it made much more sense to use XSLT for the static part and
CSS for the editable part. I also think with footnotes (if we leave out the
counting of the footnotes) the CSS way in Mozilla is way more effective. But
maybe we just have to try out both ways and then see which is the better
way. Christian who has a much better understanding of the BXE than I, will
certainly add something to this.

>> Help from others? Always appreciated :) I will try to write somehting
>> down about that when i'm more awake..
>
>Yes, let us know what we can do.

We will as soon as possible - and thank you very much.

At the moment we are finishing a project. we will continue our work for the
BXE. As much as Q42/Xopus we depend on  other resources for this Editor and
therefore I can understand very well the problem of Q42. An Open Source
Editor is just not comparable to a Open Source CMS.
We hope that there are other solutions for Xopus than reverting to a
non-open-source model as we think they are definitely our best critics at
the moment.



-- 
bx-editor-dev mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev