Hi all,
   I studied how could I myself edit necessary pages at top level here,
http://xerces.apache.org (mainly mirrors.html & index.html, in case the
voting for 2.12.0 release concludes successfully). Following are my
thoughts,

1) Each of the HTML pages at top level here, http://xerces.apache.org have
following meta-data at the top,

<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.9">
<meta name="Forrest-skin-name" content="pelt">

This gives an indication that, Apache Forrest was used to publish top level
pages at http://xerces.apache.org. I think instead, I could manually edit
(specifying 2.12.0 artifacts) these pages within an HTML editor (I have one
good one installed) and commit; Can this be ok? If only Apache Forrest
needs to be used for this task, then I think Michael needs to help us with
that.

The Apache Forrest meta-data isn't present on HTML pages within the folder
http://xerces.apache.org/xerces2-j/ (so those can be committed as I
explained in my previous mails in this thread).

2) I also see, that every HTML page at top level here,
http://xerces.apache.org has a corresponding pdf file,
like mirrors.pdf, index.pdf etc. I don't know how these could be produced
during the modifications. If these kind of pdf files are very much
necessary, then I think Michael would need to help us with that.

Hoping to have some thoughts from Michael, or anyone who knows about these
issues.


On Wed, Apr 25, 2018 at 11:09 AM, Mukul Gandhi <[email protected]> wrote:

Sorry I made a little mistake, while drafting above line (its my mailer's
> feature). The underlying link of http://xerces.apache.org/xerces2-j
> above, is pointing to http://xerces.apache.org/xerces2-j/publish_test.html
> to the readers of this mail. It should have pointed to,
> http://xerces.apache.org/xerces2-j.
>



-- 
Regards,
Mukul Gandhi

Reply via email to