Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3BD89017.BCA4DA30@apache.org>
Date: Fri, 26 Oct 2001 00:20:07 +0200
From: Stefano Mazzocchi <stefano@apache.org>
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Documentation: short alternative to @docname@?
References: <200110232036.f9NKawf26900@orion.rgv.hp.com>
 <3BD67C4D.4FE83153@apache.org> <0110251918260A.01292@igacer>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

David Crossley wrote:
> 
> Hold on to your hats everyone! Once we resolve this stuff then
> let us add it to documentation/xdocs/IMPORTANT
> There are some real good reasons for keeping some type of
> term substitution. Here is my big one - consistent speling.
> Hey, i seem to type "Coccon" often - we had best not let that
> slip through to production. Entity replacement prevents it.

Following this reasoning, we could "entitize" almost all currently
mispelled words (I *always* mispell "environment" in "enviornment" due
to slippery typing skills)... c'mon, I don't think we need to go that
far.

The vote is:  do you want to keep @doctitle@ or equivalent (entities,
xslt transformation, whatever) or stick with pure text (like Cocoon,
Apache Cocoon) where it makes sense.

This is *ONLY* for the term "Cocoon" and "Apache Cocoon" that are *NOT*
expected to change. Stuff like @version@ and @years@ are not touched by
this vote.

I vote +1 to remove @doctitle@.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org