Hi There, can't we just go with the UTF-8 by default (pages, forms etc.) and specify only changes to this default mapping (global or local or even on activate or using the actual writer.
Often you end up using UTF-8 by default and you are messing with filter and forms and stuff. This is indeed anoying (Howard gets my vote on this one). @Thiago I do not get the point about the database and output-streams are non-UTF-8. As Howard said everything becomes a Java-String And is indeed encoded using UTF already. The only chance I know about this is becomes an issue if one 'accidently' does not convert the database strings to UTF correctly and 'accidently' reconvert these strings back to the same character-set (should blow up for certain high byte values). So I guess that converting something to strings should always be Correct. If I missed the point please correct me. Cheers, Martin (Kersten) -----Ursprüngliche Nachricht----- Von: Thiago H. de Paula Figueiredo [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. Juli 2008 16:43 An: Tapestry users Betreff: Re: What if Tapestry's I18N was just "UTF-8"? Em Tue, 29 Jul 2008 11:39:21 -0300, Howard Lewis Ship <[EMAIL PROTECTED]> escreveu: > My observation is that the current design; allowing every page to have > its own charset, is beginning to feel like overkill, especially given > that the solution has a number of frayed edges. What about setting a charset for every page, but having the option of what this charset is? Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
