> -----Original Message-----
> From: Vlachogiannis Evangelos [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 27, 2002 2:21 AM
> To: '[EMAIL PROTECTED]'
> Subject: FW: iso-8859-7 at a title at jetpeed 3.2a
>

Do you mean version 1.3a2?
Don't think we have a version 3.2a (yet)

>
> Further... What I have actually done is to change the myportlets.xreg from
> utf-8 to iso, and also change every "var" of encoding in the configuration
> files from either utf-8 or iso-8859-1 to iso-8859-7. What I am getting is
> ???? instead of portlets' titles... Any help pls???
> thnx
>

Yes, and I believe PSML has the same problem.
Would recommend setting up your PSML by language, and then putting the
correct encoding type in the header.
But Im pretty sure that Jetspeed doesn't respect the encoding type that it
reads in when writing back out.

This makes me wonder how this is supposed to work from the PSML Browser,
when you create a new PSML resource, with a specific country code.
Do we now need a country+language code -> UTF mapping. Perhaps a new
registry...

One other problem that I've noticed is that the registries don't support
multiple language entries for titles and descriptions.

I don't think that its an easy fix and is going to take some research, since
I don't fully understand the problem.

As for version 1.3a2, is there anyway you could work off the cvs head?
I think you will get a lot more support from the developers if you did so.

Also recommend logging a well-documented bug.

David



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to