A big +1 on URL rewriting that supports i18n. As a matter of fact the teensy app that I'm writing in T5 is not primarily for the US market and now my choices are not appealing at all: 1. Use english class names for pages and hope that non-english speaking customers are OK with that 2. Use the non-english page names so that they're OK for the primary market and try to deal w/ english speaking customers somehow ( e.g make a different set of pages w/ the same functionality but different names, good luck if I have to ask someone else to support the app down the line). 3. Do some crazy hacking (e.g some filter or something) that will allow mw to mount the pages to meaningful URLs. The fact that the page/class names end up being in the URL with no easy way to change is where the wonderful T5 i18n support loses MUCH of its appeal.
Alex Kotchnev - original message - Subject: Re: My Tapestry5 suggestion list From: Chris Lewis <[EMAIL PROTECTED]> Date: 10/02/2008 21:43 Good point. Markus Joschko wrote: > Talking about configurable URLs: Don't forget i18n issues. > We once had a product where customers wanted to have the URL > internationalized to be meaningful in different countries. > This requirement is not uncommon in Europa at least. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- http://thegodcode.net --------------------------------------------------------------------- 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]
