Re: Encoding problem
Hi, I had the same problem. It happend when a user entered umlauts (äöü) into a HTML input field. The portlet stores the strings in a database. Each umlaut is encoded with 2 bytes. Setting the charset to ISO-8859-1 in media.xreg solved the problem Thanks - Original Message - From: Shinsuke SUGAYA [EMAIL PROTECTED] To: Jetspeed Users List [EMAIL PROTECTED] Sent: Thursday, June 03, 2004 4:10 PM Subject: Re: Encoding problem Hi Chris, Jetspeed1 uses the encoding by the following priorities. 1. character-set parameter in media.xreg 2. content.defaultencoding in JetspeedResources.properties 3. UTF-8 please see media.xreg. Thanks, shinsuke Floßmann Christoph wrote: Hi folks! The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) How do I change the encoding to ISO-8859-1 by default? Regards Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? http://bb.yahoo.co.jp/ - 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]
Encoding problem
Hi folks! The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) How do I change the encoding to ISO-8859-1 by default? Regards Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem
look in *.properties in title xml-tag: ?xml version=1.0 encoding=utf-8? Floßmann Christoph wrote: Hi folks! The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) How do I change the encoding to ISO-8859-1 by default? Regards Chris - 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: Encoding problem
On Thu, 3 Jun 2004, Floßmann Christoph wrote: | Hi folks! | | The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) utf-8 does most definately support those letters - it is much better than latin-1 (iso8859-1). Use a proper editor that has the capability to save files as utf-8 (as saving in latin1 then reading with utf8 decoding will surely mess up your data), and your problem will be solved.. -- Mvh, Endre Stølsvik M[+47 93054050] F[+47 51625182] Developer @ CoreTrek AS - http://www.coretrek.com/ CoreTrek corporate portal / EIP - http://www.corelets.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem
Hi Chris, Jetspeed1 uses the encoding by the following priorities. 1. character-set parameter in media.xreg 2. content.defaultencoding in JetspeedResources.properties 3. UTF-8 please see media.xreg. Thanks, shinsuke Floßmann Christoph wrote: Hi folks! The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) How do I change the encoding to ISO-8859-1 by default? Regards Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? http://bb.yahoo.co.jp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Encoding problem
Thanks - these changes did it. -Ursprüngliche Nachricht- Hi Chris, Jetspeed1 uses the encoding by the following priorities. 1. character-set parameter in media.xreg 2. content.defaultencoding in JetspeedResources.properties 3. UTF-8 please see media.xreg. Thanks, shinsuke Floßmann Christoph wrote: Hi folks! The jetspeed default encoding is UTF-8 what causes some problems with my portlets (here in Germany we use some letters like üöä) How do I change the encoding to ISO-8859-1 by default? Regards Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? http://bb.yahoo.co.jp/ - 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]
encoding problem
Hello everybody, I got a problem and I'm not sure if it's a bug or a misconfiguration of my system. I had a 1.4b3 portal working ok, and after the upgrade to 1.4b4 some portlets are not sending the form post info well. this is where It sent Iván now it sends Iván, it looks like some ascii to hex change... Anyone knows what can it happen??? Many thanks in advance. Iván __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: encoding problem
There has been a change between b3 and b4 relative to encoding : Here's how jetspeed looks for the encoding to use now, if you use the right way to grab parameters (see next) : 1) the character encoding used in the body of the request. 2) character-set parameter in media.xreg 3) content.defaultencoding in JetspeedResources.properties 4) US-ASCII so check all those parameters to see if one may be wrong for you. Although there is two ways to grab your request parameters in your portlets : data.getRequest().getParameter(aParameterName) : WRONG data.getParameters().getString(aParameterName) : RIGHT Cause Servlet 2.2 API is known to be buggy when encoding is different from ISO8859-1, so you should better use the parameterparser provided in jetspeed (second method). So check all this parameters and see where your trouble comes from. HTH, Aurelien PS : if you're using tomcat 3, then you're meeting a specific bug from it, and right now jetspeed is still buggy with tomcat 3. Ivan a ecrit : Hello everybody, I got a problem and I'm not sure if it's a bug or a misconfiguration of my system. I had a 1.4b3 portal working ok, and after the upgrade to 1.4b4 some portlets are not sending the form post info well. this is where It sent Ivan now it sends IvC!n, it looks like some ascii to hex change... Anyone knows what can it happen??? Many thanks in advance. Ivan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JetspeedLocalization_XX.properties ENCODING problem
Hi, Hi there! As today I'm mysteriously unable to *SEARCH* in the jetspeed mail archive and I need to solve this think briefly I'm asking here. I wrote my own localized JetspeedLocalization_sk.properties file and put it in to right directory. I got my messages in the jsp page, so the file works. The problem is: 1) When I read JetspeedLocalization_sk.properties in windows notepad, everithing looks ok (all special characters look ok). 2) When I put text used in JetspeedLocalization_sk.properties file in to the html document, set the meta http-equiv=Content-Type content=text/html; charset=windows-1250 and wiev it, it works fine. 3) BUT, when I wanna browse jetspeed (WEB-INF\templates\vm\layouts\html\defaut.vm) it comes with UTF-8 encoding and when I switch it in to windows-1250, almost all characters crashe at all. I tried to change some properties in TurbineResources and JetspeedResources.. but I can't get it work properly. Please tell me if you know, this is probably common problem: 1) How should I encode my JetspeedLocalization_sk.properties file and set the /conf (which) files to get it work. In Japanese properties file, I create it by native encoding and convert from a native character to ASCII by native2ascii command. 2) Is a velocity templating services touching the encoding of templates..? Please see the following comment: Encoding configuration If you would like to use Multi-byte character, such as CJK characters, you will need to modify the encoding parameters in: o jetspeed_home/WEB-INF/conf/JetspeedResources.properties: content.defaultencoding=encoding o jetspeed_home/WEB-INF/conf/TurbineResources.properties: services.VelocityService.input.encoding=encoding For examples, if you use UNIX in Japanese environment, encoding will be UTF-8 or EUC-JP. I think that it works if you use UTF-8... Thanks, shinsuke Thank you very much. $kala. __ Do You Yahoo!? Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JetspeedLocalization_XX.properties ENCODING problem
Hi there! As today I'm mysteriously unable to *SEARCH* in the jetspeed mail archive and I need to solve this think briefly I'm asking here. I wrote my own localized JetspeedLocalization_sk.properties file and put it in to right directory. I got my messages in the jsp page, so the file works. The problem is: 1) When I read JetspeedLocalization_sk.properties in windows notepad, everithing looks ok (all special characters look ok). 2) When I put text used in JetspeedLocalization_sk.properties file in to the html document, set the meta http-equiv=Content-Type content=text/html; charset=windows-1250 and wiev it, it works fine. 3) BUT, when I wanna browse jetspeed (WEB-INF\templates\vm\layouts\html\defaut.vm) it comes with UTF-8 encoding and when I switch it in to windows-1250, almost all characters crashe at all. I tried to change some properties in TurbineResources and JetspeedResources.. but I can't get it work properly. Please tell me if you know, this is probably common problem: 1) How should I encode my JetspeedLocalization_sk.properties file and set the /conf (which) files to get it work. 2) Is a velocity templating services touching the encoding of templates..? Thank you very much. $kala.
Encoding problem
Hi, next problem Jetspeed seems to lock normal html pages and portals into UTF-8, thus causing problems with international character sets. Changing the media entries didn´t work in this regard and forcing a header didn´t work as well. Is this a bug or where can I change the encoding? Werner -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
