"Kevin A. Burton" wrote:
>
> Raphael.
>
> Is there a reason for this? I saw your FIX ME but what was the bug?
>
If I typed an accentuated character in the JetspeedContentAdmin,
the jetspeed-content.xml becomes un-parsable because the character doesn't match
the defined encoding for the file which is UTF-8 by default.
> This shouldn't go in the JetspeedContentAdmin but instead should go in
> the Admin screen right before we grab the Portlet.
>
Either this will affect all admin portlets if it's put in the Admin screen or we
have to test for this specific portlet, in either case it's not very good.
I guess we should allow an encoding attribute in the registry portlet definition...
> Java Apache CVS Development wrote:
> > + //FIX: I18N fix, set the character encoding to UTF-8
> > + //can we do this without using RunData ?
> > +
> > + this.getPortletConfig().getRunData().getPage().getHead().addElement(
> > + new Meta().setHttpEquiv("content-type").setContent("text/html;
>charset=utf-8"));
> > +
>
> Could you fix it?
>
Done.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
