I agree that we should implement both 3.2 and 4.01 DTDs. Moreover 3.2 is just a 
subset of 4.01 and, I believe, it doesn't require much work to support 3.2 too.

--
Alexey A. Ivanov
Intel Middleware Product Division


>-----Original Message-----
>From: Alexey Petrenko [mailto:[EMAIL PROTECTED]
>Sent: Saturday, July 22, 2006 11:44 AM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [classlib][html] HTML 3.2 or 4.01
>
>I agree that we should implement both if it possible. Since we can
>easile determine the HTML version by DTD in the header.
>
>SY, Alexey
>
>2006/7/22, Miguel Montes <[EMAIL PROTECTED]>:
>> HI all:
>> Intel has just contributed javax.swing.text.html, based on HTML 4.01.
>Sun's
>> implementation, on the other hand, claims to be based on HTML 3.2,
>although
>> there are same differences.
>> ¿Which one should we follow? ¿Both? The parser behavior is parameterized
>by
>> a DTD, so perhaps we should provide a 3.2 DTD, to be compatible with Sun,
>> and a 4.01 DTD.
>> Any ideas?
>>
>> Miguel Montes
>>
>> On 7/21/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>> >
>> >
>> >
>> > Miguel Montes wrote:
>> > > Hi all:
>> > > On behalf of ITC, I would like to offer our help to complete this
>> > package.
>> > > We could work in the missing parser.
>> >
>> > Fantastic.  Please have the people working on it work here and with
>much
>> > discussion with the rest of the community.
>> >
>> > > The new contribution is based on HTML 4.01, while Sun's version is
>based
>> > on
>> > > HTML 3.2,  (in fact, the DTD used is different from the HTML 3.2 DTD,
>> > > perhaps is based on an early draft).
>> > > ¿Which one should we follow? ¿How important is to be compatible with
>the
>> > > existing codebase?
>> >
>> > To start the discussion, fire that off as a new thread w/ the subject :
>> >
>> > [classlib][html]  ......
>> >
>> > or something.
>> >
>> > geir
>> >
>> > >
>> > >
>> > > On 7/21/06, Ivanov, Alexey A <[EMAIL PROTECTED]> wrote:
>> > >>
>> > >> Hi all,
>> > >>
>> > >> I'd like to announce the contribution of javax.swing.text.html
>package
>> > >> on behalf of Intel. The archive can be found here:
>> > >>
>> > >> https://issues.apache.org/jira/browse/HARMONY-948
>> > >>
>> > >>
>> > >> The contribution includes new files implementing HTML text
>> > functionality
>> > >> and a small patch for already existing files in javax.swing to
>> > integrate
>> > >> the new code.
>> > >>
>> > >> The package is incomplete, the code there is not sufficient to
>enable
>> > >> those nice help windows in jEdit... yet. If anyone wants to help
>making
>> > >> it complete, you have an excellent chance to do so!
>> > >>
>> > >> For the biggest issue, there is no HTML parser. Some tags are not
>> > >> supported yet, such as AREA, MAP, APPLET, IFRAME, OBJECT, PARAM and
>> > some
>> > >> others, as well as incomplete support of CSS1 properties. The list
>of
>> > >> known issues and TODOs can be found in the README file included in
>the
>> > >> contribution, as well as the building and testing instructions.
>> > >>
>> > >> Please don't hesitate to contact me for more details if needed, and
>I
>> > >> intend to keep working on this package in Harmony.
>> > >>
>> > >> --
>> > >> Alexey A. Ivanov
>> > >> Intel Middleware Product Division
>> > >>
>> > >> --------------------------------------------------------------------
>-
>> > >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > >> For additional commands, e-mail: harmony-dev-
>[EMAIL PROTECTED]
>> > >>
>> > >>
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > Terms of use : http://incubator.apache.org/harmony/mailing.html
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>> --
>> Miguel Montes
>>
>>
>
>
>--
>Alexey A. Petrenko
>Intel Middleware Products Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to