Subject: Re: bug 629
From: sam th (sam@bur-jud-118-039.rh.uchicago.edu)
Date: Tue Jan 25 2000 - 16:09:30 CST
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 25 Jan 2000, Eric W. Sink wrote:
> > </p><p> what we have now
> > <br></br> gibberish
> > <br> what HMTL expects
> > <br/> the XML equivalent of what HTML expects
>
> I think I feel even more strongly than Paul on this issue. Option #3
> is the only choice.
>
> HTML is simply not XML-compliant. For a lot of reasons, it cannot be.
>
> Option #1 is semantically incorrect.
> Option #2 is simply wrong. In HTML, <br> is NOT a container.
> Option #4 is XML, which is wrong.
>
> Option #3 is exactly what a forced line break is, according to HTML as
> expressed in both its specification and in *all* of its prevalent
> implementations.
>
> Now, if this were the XHTML exporter, then the answer would be
> different. ;-)
>
> --
> Eric W. Sink, Software Craftsman
> SourceGear Corporation
> eric@sourcegear.com
>
I was afraid that you folks would think this. The major problem is, this
will require significant changes in the HTML export code to facilitate.
First, forced line breaks are simply not recognized as such by the current
HTML exporter. Second, <p> is the default block used in the exporter, and
as such, the code (as far as I can tell, which is not that far) does not
include particular provision for it. Finally, in order to distinguish
forced line breaks in HTML, we would have to distinguish them in AbiWord,
which I don;t think is currently done (unless every </p> represents one).
I could be wrong about these difficulties, and I hope I am, but I just
want to get them out.
sam th
sytobinh@uchicago.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4jh8bt+kM0Mq9M/wRAmaHAJ0a5BbtLgiKvQlHVuEUspC8ZoZPhACfdFAl
B4NBcyo5FJ4Lm7WvudqtTg0=
=xKM1
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b25 : Tue Jan 25 2000 - 16:09:41 CST