I tried to set <%@ page contentType="text/html; charset=UTF-8" %> but now even my German development server displays all german characters as "?" only.
I guess I would have to use ALL text coming from resource bundles that are converted to UTF8. And I would have to set my db also to utf8, i guess. But since I don't need i18n, just german language, I saw no sense to start using resource bundles for only one language. Or does it help to save all jsps in UTF8. Guess my Eclipse won't let me do that, too. Any other or more ideas? Thx. Michael > -----Original Message----- > From: Hirschmann, Bernhard [mailto:[EMAIL PROTECTED]] > Sent: Dienstag, 4. Februar 2003 11:51 > To: 'Struts Users Mailing List' > Subject: AW: HTML entities (general Struts taglib problem > with language entities) > > > > Jesus! So much work for that purpose? :-) > > Have you tried to use UTF-8 for your JSPs? Then all that > transforming to HTML encoding is not necessary anymore. It > works great at my project, and I have to use more special > characters than in German. (27 languages in fact) > > See http://www.anassina.com/struts/i18n/i18n.html for a full how-to. > > Regards, > Bernhard > > > -----Ursprüngliche Nachricht----- > Von: mech [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 4. Februar 2003 11:42 > An: 'Struts Users Mailing List' > Betreff: RE: HTML entities (general Struts taglib problem > with language > entities) > > > You can usually use the attribute (e.g. with <bean:write>): > filter="true" if you want special characters converted into > html substitutions or filter="false" if you like to format > your view with <br> tags. > > Unfortunatally, i hate converting all my German language > Umlaute into ä ü etc. in my database. > > If I say filter="true" my German special letters won't get > filtered and I get stupid output if my Solaris server runs on > English language instead like my development server in German > language. > > If I say filter="true" an use ä etc. coming from my db > fields, I get & filtered to & which doesn't help much > either... In the html output I would get &uuml; instead of ü > > So I have to always filter="false" and use ä etc. for > all German characters in my db. :-( At least than I can also > use html tags for formating stored in the db. > > So on question for the future development. > Could the tag filter be enhanced to filter not only brackets > etc. but also language characters? > > Otherwise you'll have a problems if you use filter="true" and > filter="false" aswell. Either you have to convert all your > database field's not to use any language specific characters. > Or you can't use filter="true" because your language specific > html entities get converted twice because one character in > the escape sequence (the & character) gets filtered again... > > What would be needed would be an filter="true" logic that > doesn't filter the & of escape sequences or to filter also > language specific html entities. The last thing would be the > cleaner way. > > Michael > > > > -----Original Message----- > > From: Mark Lowe [mailto:[EMAIL PROTECTED]] > > Sent: Dienstag, 4. Februar 2003 11:16 > > To: Struts List > > Subject: HTML entities > > > > > > Has anyone any information on preventing "<" and ">" being > translated > > into < and > when using the tag libs.. > > > > I have a bunch of data in my sql... there are a few > presentation tags > > strored in the db (e.g. <br>, <b> etc).. > > > > I've parsed the results to replace any entities to "<" etc > > but they're > > being coverted in the jsp when iterating through the result... > > > > My results set contains > > > > <br> etc > > > > i read this into map which i then put into an array (array of maps) > > > > put the array in the request... > > > > It seems to me that > > > > the encoding is happening > > 1. during the iteration > > 2. when being set in the request > > 3. when being added to the map > > > > I'm working my way through these possibilties now but if > anyone knows > > anything then please don't be shy.. > > > > Any suggestions? > > > > Thanks mark > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
