At 02:12 11/1/01 -0800, Thayer Robins wrote:
>I don't belive this has been picked up yet.
kewl ;)
>This patch adds an additional, nested element ('replacefilter') to the
>replace task. In addition to allowing for multiple replacements, the nested
>element allows replacement values to be extracted from a property file. The
>name of this file is specified using an optional 'replace' attribute
>(propertyFile).
>
>replacefilter has the following attributes:
>
> token (mandatory) -> string to search for
> value (optional) -> replacement string
> property (optional) -> name of property whose value is to serve as the
>replacement value
>
>Either value or property may be specified, but not both. If neither is
>provided, the value provided using the replace attribute 'value' and/or the
>'replacevalue' element is used. If no value was specified there either, the
>token is replaced with an empty string.
>
>The existing elements and attributes of replace are still supported, so it
>is possible to use either the token/replacetoken and value/replacevalue
>attributes/elements, the nested replacefilter elements, or both in the same
>operation.
Would you be able to rework the above into a patch for docs/index.html ? ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
