Well i tried including it within the getcontent of a portlet, didn't work. So I tried to modify the default.vm template to include them after the body :
<body class="PageBody"> <script type="text/javascript" src="/jetspeed/scripts/Resources_fr.js" language="JavaScript"></script> <script type="text/javascript" src="/jetspeed/scripts/Validation.js" language="JavaScript"></script> Didn't work. Then I tried changing the meta content of the webpage and set it to iso 8859-1, no success :-( Finally I just tried your idea, didn't work neither :) I'm lost... Here are the parameters named "encoding I have" : template.encoding=8859_1 (velocity.properties) services.VelocityService.input.encoding=8859_1 (turbineresources.properties) content.defaultencoding=iso-8859-1 (jetspeedresources.properties) It seems more as a problem of servlet parameter, since it's during the transfert of the file that it gets wrong, but don't know where.... If anyone has another idea ? Aurélien Pernoud > -----Message d'origine----- > De : Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]] > Envoyé : jeudi 3 octobre 2002 11:50 > À : 'Jetspeed Users List' > Objet : RE: Strange Javascript Transfert using Jetspeed : > encoding issue > ? > > > > That's the tricky question :) it actually depends on how you > include the js > code > into the portal but my best guess is: > > TurbineResources.properties: > services.VelocityService.input.encoding=8859_1 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
