William Leung wrote:
> Santiago Gala wrote:
>
> > William Leung wrote:
> >
> > > Santiago Gala wrote:
> > >
> > > > William Leung wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > After modified the portlet registry file with some big5
> > > > > encodig string and marshal it to
> > > > > storage, it seems saved as UTF-8 format. I've check out
> > > > > xerces 1.2.1 source code and
> > > > > discovered that there's no support on Big5. Is it true?
> > > >
> > > > UTF-8 should support Big5 characters (in fact, any existing Unicode
> > > > character). It is more uniform, and the default encoding for XML,
> > > > because you can use it without regard to the "native" encoding of the
> > > > machine you are using. The only problem is that you should use UTF-8
> > > > capable editors to read and write it outside Jetspeed.
> > > >
> > >
> > > emm.. I fixed my (silly)problem. Since some screens in Jetspeed (i.e. Admin)
> > > use UTF-8
> > > as the page default character set. After I input something and submit the
> > > form, it becomes
> > > UTF-8 encoding (of cos) and saved in the portletregistry or whatever so I
> > > cannot view it
> > > correctly under the big5 environment.
> > >
> > > >
> > > > I'm fighting with a bug in the process of processing multibyte character
> > > > channels in Jetspeed. If you are experiencing a bug with multibyte
> > > > characters in Jetspeed, please give more details.
> > > >
> > >
> > > I also worked with multibyte character channels (Big5), what problem you
> > > are
> > > facing?
> > >
> >
> > In cvs Jetspeed, if you run it, you will get a channel
> > (www.javable.com/rus/rss.shtml) in russian. The file gets correctly to the cache
> > as UTF-8 (even if its encoding attrbitue says other thing). But the characters
> > get broken in the portlet, as "?".
> >
>
> Should it related to the web page's character set? I tried
> some Chinese channel,
> either
> encoding in Big5 and UTF-8 works, but you should be reminded
> to change the page's
> character set as well.
>
> Unicode should have no problem , right?
>
As Jetspeed merges several content sources in the same HTML page, there should be a
unique content encoding for the whole page. As performing a negociation during request
processing would be complex and resource consuming, I opted for use the same encoding
for all the Jetspeed pages.
So, I patched Jetspeed some time ago to use UTF-8 as the encoding of all pages. In
this way, different portlets can come in different character encodings (imagine a
multilingual page, with some portlets in spanish, some in russian, some in japanese
and some in chinese. The only reasonable way to render all together in the same page
is to use a Unicode capable encoding. UTF8 looked simple enough, as the ASCII
characters are not transformed at all.
One important thing is not limit to use a META HTTP_EQUIV HTML tag. Ecs needs to know
about the encoding, to generate the proper bytes. So, we need to tell the proper ECS
element about the encoding.
>
> --
> Regards,
> William Leung
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
