[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jetspeed-dev
Subject:    RE: iso-8859-7 at a title at jetpeed 3.2a
From:       "Ender KILICOGLU" <ender () kilicoglu ! nom ! tr>
Date:       2002-11-30 21:42:28
[Download RAW message or body]

I have same problem. Did not look for problem but I have a clue: 2
months ago it was working. Look for changes.

Ender


-----Original Message-----
From: Vlachogiannis Evangelos [mailto:evlach@aegean.gr] 
Sent: Saturday, November 30, 2002 3:38 PM
To: 'Jetspeed Developers List'
Subject: RE: iso-8859-7 at a title at jetpeed 3.2a


Hi all,
I have another similar problem. I have written a portlet writing to a
database and then retrieving results. The problem is that when the input
is in Greek even if this is stored to the database correctly (correct
encoding) when it retrieves it and return that back to jetspeed,  ??????
appear. Having in mind all those problems and also that we cannot use
jetspeed's last release for similar reasons I am thinking of working on
the newest Jetspeed and trying to fix it. 
Could I have some guidelines/advices/docs/classes to concentrate from
the experts?

Thnx
Vangelis

-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com] 
Sent: Wednesday, November 27, 2002 7:43 PM
To: Jetspeed Developers List
Subject: RE: iso-8859-7 at a title at jetpeed 3.2a



> -----Original Message-----
> From: Vlachogiannis Evangelos [mailto:evlach@aegean.gr]
> Sent: Wednesday, November 27, 2002 2:21 AM
> To: 'jetspeed-dev@jakarta.apache.org'
> 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:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:jetspeed-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:
<mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:jetspeed-dev-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]