Moving com.sun.javadoc packages to cp-tools gjdoc cvs module

2002-05-11 Thread Mark Wielaard

Hi,

Any objections to moving the classes from classpath sun/com/javadoc to
the cp-tools gjdoc CVS module? Those classes are not really part of the
standard java library packages. They are already licensed under the GPL
without exception (just like gjdoc). And it would make gjdoc self
contained.

Cheers,

Mark



___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath



Re: Moving com.sun.javadoc packages to cp-tools gjdoc cvs module

2002-05-11 Thread Eric Blake

No objections here.  Besides, having com.sun packages in a free project
has always sounded weird to me, since this project is not sponsored by
Sun.  And, since Sun specifically states that the classes in com.sun are
undocumented and subject to change, no external project should be
linking to those classes in the first place, so it really isn't part of
Classpath.

Mark Wielaard wrote:
> 
> Hi,
> 
> Any objections to moving the classes from classpath sun/com/javadoc to
> the cp-tools gjdoc CVS module? Those classes are not really part of the
> standard java library packages. They are already licensed under the GPL
> without exception (just like gjdoc). And it would make gjdoc self
> contained.
> 
> Cheers,
> 
> Mark
> 

-- 
This signature intentionally left boring.

Eric Blake [EMAIL PROTECTED]
  BYU student, free software programmer

___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath



Re: XML Entities, DTDs

2002-05-11 Thread Mark Wielaard

Hi,

On Fri, 2002-05-10 at 02:14, Julian Scheid wrote:
> We need to ship some sort of entity definition files along with Gjdoc
> so that the stylesheets can properly resolve external entity
> references like   or ä.
> 
> Can we use these?
> http://www.oasis-open.org/committees/docbook/xmlcharent/0.1/index.shtml

I think the license says that it may be freely used to make derived
works that implement what it describes (the entities). But my brains
does become a bit fuzzy when reading this copyright statement.

Copyright © 2001 The Organization for the Advancement of Structured
Information Standards [OASIS]. All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to OASIS, except as needed for
the purpose of developing OASIS specifications, in which case the
procedures for copyrights defined in the OASIS Intellectual Property
Rights document must be followed, or as required to translate it
into languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Does anybody think this is not free and/or GPL compatible?

If anybody objects then maybe we can use the ones from the XHTML spec?


But the simplest solution might be to just clean the original HTML from
those entities when transforming to XML. I believe there are only about
200 valid/used symbols anyway.

> BTW have we yet agreed on which URIs to use for the DTDs? I'm currently using
> 
> "http://www.gnu.org/software/cp-tools/dtd/gjdoc.dtd";>
> 
> Any problems with that?

I don't know. We might have to ask the gnu webmasters
([EMAIL PROTECTED]). Should there be an actual dtd at that address?

Speaking of which. Since we still don't have a dtd can we also use the
--novalid flag for xsltproc so we won't get the warning messages about
missing dtds?

Cheers,

Mark

___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath



Re: XML Entities, DTDs

2002-05-11 Thread Julian Scheid


Mark Wielaard wrote:
 >On Fri, 2002-05-10 at 02:14, Julian Scheid wrote:
>>We need to ship some sort of entity definition files along with Gjdoc
>>so that the stylesheets can properly resolve external entity
>>references like   or ä.
>>
>>Can we use these?
>>http://www.oasis-open.org/committees/docbook/xmlcharent/0.1/index.shtml
> 
> Does anybody think this is not free and/or GPL compatible?
> 
> If anybody objects then maybe we can use the ones from the XHTML spec?
> 
> 
> But the simplest solution might be to just clean the original HTML from
> those entities when transforming to XML. I believe there are only about
> 200 valid/used symbols anyway.

But it's an evolving standard which we would need to keep up with if we
reinvented the wheel. Besides, an XSLT processor delivers entity
transformation for free, so why should we implement it? If there are no
entity definition files out there with an acceptable license (which I
don't believe) then we need to implement our own, but only the definitions
and not the transformation.

> Speaking of which. Since we still don't have a dtd can we also use the
> --novalid flag for xsltproc so we won't get the warning messages about
> missing dtds?

I'll write the DTD soon... until then feel free to use --novalid. I'll
leave the warning in so it reminds me of what is missing. ;)

Julian



___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath