On Thu, 17 Jan 2002, Nicola Ken Barozzi wrote:

>
> From: "Martin Holz" <[EMAIL PROTECTED]>
> > Hi,
> >
> > we are currently preparing a cocoon package, which transforms MathML to
> > GIF and SVG. The package consist of a two Transformers and a Serializer
> plus
> > bunch of auxiliary classes, which are not cocoon specific.
> > Now we need some advice on the best package structure.
> >
> > Should we place everything in one package (org.apache.cocoon.xml.mathml ?)
> or
> > should the transformer go into the package
> > org.apache.cocoon.xml.transformation?
>
> Since I presume that the Transformer and the Serializer share code, IMHO
> it's best to split the package in an Avalon Component to put in
> org.apache.cocoon.components.mathml , like the SVGSerializer did, and put
> the transformer in org.apache.cocoon.transformation and the serializer in
> org.apache.cocoon.serialization.

The MathML package currently 3 sitemap components:

Transformer:
FragmentExtractorTransformer, similar to the SVG extractor.
MathTransformer, to replace the MathML fragments to SVG fragments in the
document

Serializer:
MathSerializer, to generate a GIF Image from a MathML document

My first qeustion is, can the author of FragmentExtractorTransformer write
his class more flexible? So that I can set the information,
which elements should be extracted, in the sitemap, like

<map:generator  name="extractor"
  src="org.apache.cocoon.generation.FragmentExtractorGenerator">
 <map:parameter name="EXTRACT_URI"
                value="http://www.w3.org/1998/Math/MathML"/>
 <map:parameter name="EXTRACT_ELEMENT" value="math"/>
</map:generator>

We want to give the project free as open source, and ask the
xml.apache.org projekt to pick up out project. At this moment the
project is licenceless, so we can take the apache licence.

In future we ant also write a ant task to contruct the content offline,
as preprocessing step.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to