AW: localization oddity
It would be very intresting for if you could tell me how you could convert the messages properties files to UTF-8 because as I know java properties files can only be ISO-8859-1 encoded. Mit lieben Grüßen aus dem eWerk | Holger Stolzenberg | Softwareentwickler | | Geschäftsführer: | Frank Richter, Erik Wende, Hendrik Schubert | | eWerk IT GmbH | Markt 16 | Leipzig 04109 | http://www.ewerk.com | HRB 9065, AG Leipzig | Hauptniederlassung Leipzig | | fon +49.341.4 26 49-0 | fax +49.341.4 26 49-88 | mailto:[EMAIL PROTECTED] | | Support: | fon 0700 CALLME24 (0700 22556324) | fax 0700 CALLME24 (0700 22556324) | | Auskünfte und Angebote per Mail | sind freibleibend und unverbindlich. -Ursprüngliche Nachricht- Von: Daniel Kleine-Albers [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 17. Mai 2007 21:45 An: Tapestry users Betreff: Re: localization oddity Hi there, I had the same problem with German umlauts not rendering correctly. Have a look at the character encoding of your files. I converted all my files to UTF-8 and since then all the labels (regardless in which message file) render correctly. Best regards Daniel On 10.05.2007, at 11:43, Jesse Kuhnert wrote: Not much - and definitely not anything that would be related to what you are seeingSo if you see an oddity that would explain it it has to in there, or your copy paste of the characters didn't come through ok in the new file,. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: I'm still using 4.0.2. Not sure how much has changed since then. e. On 5/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: I don't know what version you are on but most of that happens in here: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry- framework/src/java/org/apache/tapestry/services/impl/ ComponentMessagesSourceImpl.java?view=markup I haven't changed things ~too~ much in 4.1.2 but there are slight differences...Reading the code leads me to believe that the namespace properties (ie the global) would be read from the same service...In fact I know it is since I added something in for appfuse to be able to place them in different locations. Maybe you'll see a slight difference in component vs. namespace reading in there? If you do let me know. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: Thanks for the tip, I'll give it shot. I'm still very curious about why it would behave differently. :-| e. On 5/9/07, Michael Maier [EMAIL PROTECTED] wrote: I wonder that 'recap_label=Récapitulation' works... try man native2ascii *.properties are invented by english speaking man, so everything is ascii...:-) maybe this will help Am 10.05.2007 um 00:16 schrieb Eric Schneider: I'm in the process of moving my page and component message bundles into a global file. In the long run this seems like a much more manageable approach. But, I'm seeing some results that I didn't expect. For example, moving recap_label=Récapitulation from a page property file to the global property file causes the label to render differently. When it was in the page_fr.properties file it would render in the browser properly, Récapitulation. When being pulled from the global file (app_name_fr.properties) it would render like RÈcapitulation. Another example of the oddness, RÉSERVATION BLESSÉE renders as R...SERVATION BLESS...E from the global properties file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - 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]
Re: localization oddity
Hi there, I had the same problem with German umlauts not rendering correctly. Have a look at the character encoding of your files. I converted all my files to UTF-8 and since then all the labels (regardless in which message file) render correctly. Best regards Daniel On 10.05.2007, at 11:43, Jesse Kuhnert wrote: Not much - and definitely not anything that would be related to what you are seeingSo if you see an oddity that would explain it it has to in there, or your copy paste of the characters didn't come through ok in the new file,. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: I'm still using 4.0.2. Not sure how much has changed since then. e. On 5/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: I don't know what version you are on but most of that happens in here: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry- framework/src/java/org/apache/tapestry/services/impl/ ComponentMessagesSourceImpl.java?view=markup I haven't changed things ~too~ much in 4.1.2 but there are slight differences...Reading the code leads me to believe that the namespace properties (ie the global) would be read from the same service...In fact I know it is since I added something in for appfuse to be able to place them in different locations. Maybe you'll see a slight difference in component vs. namespace reading in there? If you do let me know. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: Thanks for the tip, I'll give it shot. I'm still very curious about why it would behave differently. :-| e. On 5/9/07, Michael Maier [EMAIL PROTECTED] wrote: I wonder that 'recap_label=Récapitulation' works... try man native2ascii *.properties are invented by english speaking man, so everything is ascii...:-) maybe this will help Am 10.05.2007 um 00:16 schrieb Eric Schneider: I'm in the process of moving my page and component message bundles into a global file. In the long run this seems like a much more manageable approach. But, I'm seeing some results that I didn't expect. For example, moving recap_label=Récapitulation from a page property file to the global property file causes the label to render differently. When it was in the page_fr.properties file it would render in the browser properly, Récapitulation. When being pulled from the global file (app_name_fr.properties) it would render like RÈcapitulation. Another example of the oddness, RÉSERVATION BLESSÉE renders as R…SERVATION BLESS…E from the global properties file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: localization oddity
Thanks, I did something similar. Except I used ISO-8859-1. meta key=org.apache.tapestry.template-encoding value=ISO-8859-1/ meta key=org.apache.tapestry.messages-encoding value=ISO-8859-1/ meta key=org.apache.tapestry.output-encoding value=ISO-8859-1/ I still don't have an explanation for the odd behavior, but it works...I move on. e. On 5/17/07, Daniel Kleine-Albers [EMAIL PROTECTED] wrote: Hi there, I had the same problem with German umlauts not rendering correctly. Have a look at the character encoding of your files. I converted all my files to UTF-8 and since then all the labels (regardless in which message file) render correctly. Best regards Daniel On 10.05.2007, at 11:43, Jesse Kuhnert wrote: Not much - and definitely not anything that would be related to what you are seeingSo if you see an oddity that would explain it it has to in there, or your copy paste of the characters didn't come through ok in the new file,. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: I'm still using 4.0.2. Not sure how much has changed since then. e. On 5/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: I don't know what version you are on but most of that happens in here: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry- framework/src/java/org/apache/tapestry/services/impl/ ComponentMessagesSourceImpl.java?view=markup I haven't changed things ~too~ much in 4.1.2 but there are slight differences...Reading the code leads me to believe that the namespace properties (ie the global) would be read from the same service...In fact I know it is since I added something in for appfuse to be able to place them in different locations. Maybe you'll see a slight difference in component vs. namespace reading in there? If you do let me know. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: Thanks for the tip, I'll give it shot. I'm still very curious about why it would behave differently. :-| e. On 5/9/07, Michael Maier [EMAIL PROTECTED] wrote: I wonder that 'recap_label=Récapitulation' works... try man native2ascii *.properties are invented by english speaking man, so everything is ascii...:-) maybe this will help Am 10.05.2007 um 00:16 schrieb Eric Schneider: I'm in the process of moving my page and component message bundles into a global file. In the long run this seems like a much more manageable approach. But, I'm seeing some results that I didn't expect. For example, moving recap_label=Récapitulation from a page property file to the global property file causes the label to render differently. When it was in the page_fr.properties file it would render in the browser properly, Récapitulation. When being pulled from the global file (app_name_fr.properties) it would render like RÈcapitulation. Another example of the oddness, RÉSERVATION BLESSÉE renders as R…SERVATION BLESS…E from the global properties file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: localization oddity
This sounds troublesome, if you file this in jira I should be able to track down the discrepancy. (if any) On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: Hi, I'm in the process of moving my page and component message bundles into a global file. In the long run this seems like a much more manageable approach. But, I'm seeing some results that I didn't expect. For example, moving recap_label=Récapitulation from a page property file to the global property file causes the label to render differently. When it was in the page_fr.properties file it would render in the browser properly, Récapitulation. When being pulled from the global file (app_name_fr.properties) it would render like RÈcapitulation. Another example of the oddness, RÉSERVATION BLESSÉE renders as R…SERVATION BLESS…E from the global properties file. Anyone know why this would be happening? Thanks in advance. Eric -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: localization oddity
Not much - and definitely not anything that would be related to what you are seeingSo if you see an oddity that would explain it it has to in there, or your copy paste of the characters didn't come through ok in the new file,. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: I'm still using 4.0.2. Not sure how much has changed since then. e. On 5/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: I don't know what version you are on but most of that happens in here: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/services/impl/ComponentMessagesSourceImpl.java?view=markup I haven't changed things ~too~ much in 4.1.2 but there are slight differences...Reading the code leads me to believe that the namespace properties (ie the global) would be read from the same service...In fact I know it is since I added something in for appfuse to be able to place them in different locations. Maybe you'll see a slight difference in component vs. namespace reading in there? If you do let me know. On 5/9/07, Eric Schneider [EMAIL PROTECTED] wrote: Thanks for the tip, I'll give it shot. I'm still very curious about why it would behave differently. :-| e. On 5/9/07, Michael Maier [EMAIL PROTECTED] wrote: I wonder that 'recap_label=Récapitulation' works... try man native2ascii *.properties are invented by english speaking man, so everything is ascii...:-) maybe this will help Am 10.05.2007 um 00:16 schrieb Eric Schneider: I'm in the process of moving my page and component message bundles into a global file. In the long run this seems like a much more manageable approach. But, I'm seeing some results that I didn't expect. For example, moving recap_label=Récapitulation from a page property file to the global property file causes the label to render differently. When it was in the page_fr.properties file it would render in the browser properly, Récapitulation. When being pulled from the global file (app_name_fr.properties) it would render like RÈcapitulation. Another example of the oddness, RÉSERVATION BLESSÉE renders as R…SERVATION BLESS…E from the global properties file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
