On 12/5/01 6:10 AM, "Neeme Praks" <[EMAIL PROTECTED]> wrote:
>
> I needed to use Texen for some non-english generation tasks and I patched it
> to support different input/output encodings. Diffs attached.
> Example usage (with Ant):
I haven't looked at the diffs but will the task work as it did before if you
do not specify 'inputEncoding' and 'outputEncoding'?
Great additions, I'll apply the patch later tonight.
> <texten
> controlTemplate="${control.template}
> outputDirectory="${output.dir}"
> templatePath="${template.dir}"
> outputFile="${output.file}"
> inputEncoding="Cp1257"
> outputEncoding="Cp1257"
> />
>
> Also, you can use it in a template, see new parse(...) method:
> public String parse (String inputTemplate,
> String intputEncoding,
> String outputFile,
> String outputEncoding,
> String objectID,
> Object object)
>
> Rgds,
> Neeme
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
