That's pretty much it In english, this could be the case:
propertyname=this is a word Where say in Elbonian: propertyname=GDSH DGHDS DGDSSKD DHDSJ DHDSH HDHDHD If I want the spaces translated as 's I would have to propertyname=this is a word And then explain to the Elbonian translator what means (and pray it's not part of Elbonian already ;-)) I think that there should be a bean:message tag attribute to do this, but in the short term, my idea would create a custom Message Resource Configuration to do it for a specific message resource bundle. -Joe -----Original Message----- From: Freddy Villalba A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 6:21 PM To: Struts Users Mailing List Subject: RE: i18n and You're initiative sounds interesting... however, I'm not sure I've fully undestood what you express. Let's see: if what you want to translate are property names, then what's the problem? for a property "X" that reads "Y Z L" in another language, you could perfectly have an entry on each dictionary for that property... say MYPROPERTY = X for language 1 and MYPROPERTY = Y Z L for language 2. This sounds so obvious and your idea so interesting that I'm sure I've to be missing something. Could you please be a little bit more illustrative? Thanx, Freddy. -----Mensaje original----- De: Joe Hertz [mailto:[EMAIL PROTECTED] Enviado el: jueves, 14 de octubre de 2004 0:12 Para: 'Struts Users Mailing List' Asunto: i18n and I have a number of property values that will be internationalized and need non-breaking spaces between each word in them. I could put into each space, but that 1) is going to confuse my native language translators who know nothing of HTML. 2 words in english could be 3 in language-x). 2) would be wrong. There doesn't appear to be any built in method of handling this with bean:message or anything else, so I'm about to write a custom configuration class for a separate Message Resource Bundle that will contain the properties where I want spaces displayed as " "'s I have a hard time believing no one else has run into this...so I ask the following: Do I need to do this? Is there a way of doing it without writing a custom handler? or a better way of doing it? And if not, who wants to see the code when it's done? :-) -Joe --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
