RE: [CFORMS] required fields error translation

2006-02-14 Thread Bruyn Bill
Title: Message Bingo!  Switching the order of the transforms seems to have done the trick.  For clarification, the matcher in question now reads:                                                           Thank you!   -Original Mes

RE: [CFORMS] required fields error translation

2006-02-14 Thread Jason Johnston
Yeah, I have that defined just as you've written it > there. > >> -Original Message- >> From: Jason Johnston [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, February 14, 2006 11:15 AM >> To: users@cocoon.apache.org >> Subject: Re: [CFORMS] required fields e

Re: [CFORMS] required fields error translation

2006-02-14 Thread Simone Gianni
Hi Jason, not sure about that, i haven't tested it for a while, but i usually put the i18n transformer before the actualy cform xsl. This is because cforms xsl does Could you give it a try and tell us if it works correctly moving the i18n transformer after the ? Simone Gianni Jason Johnsto

RE: [CFORMS] required fields error translation

2006-02-14 Thread Bruyn Bill
Thanks, Jason. Yeah, I have that defined just as you've written it there. > -Original Message- > From: Jason Johnston [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 14, 2006 11:15 AM > To: users@cocoon.apache.org > Subject: Re: [CFORMS] required fiel

Re: [CFORMS] required fields error translation

2006-02-14 Thread Jason Johnston
> For the life of me, I can't figure out how to translate the i18n error > messages for required fields... I did find this thread that reports a > bug that should be fixed by now (I'm on Cocoon 2.1.8): > http://java2.5341.com/msg/97625.html > > Can anyone confirm that this was indeed fixed? > > If

[CFORMS] required fields error translation

2006-02-14 Thread Bruyn Bill
For the life of me, I can't figure out how to translate the i18n error messages for required fields... I did find this thread that reports a bug that should be fixed by now (I'm on Cocoon 2.1.8): http://java2.5341.com/msg/97625.html Can anyone confirm that this was indeed fixed? If so, then I su