Posted by Jukka K. Korpela on 11/28/06 07:39

Scripsit sunilp:

> I have a problem related to frame src URL and japanese characters.

Stop using frames, to start with.

> Sometimes this URL contains a few request parameters.Currently i m
> testing for japanese characters in request parameters.

Probably this problem has nothing to do with frames. This is one reason for
stopping using frames: there is one source of problems less, so it is easier
to identify where the problem is.

> I have set the character-set of all web pages as "UTF-8".(Using
> content-type meta tag).

You should use HTTP headers for setting the encoding ("charset"). In the
absence of any URL, we cannot know whether you in fact have HTTP headers
that override the meta hacks (tags).

But irrespectively of such issues, the URL _should_ be % encoded after
representing it in UTF-8, by the current protocols. This is defined handling
of URLs, independently of the internal encoding of documents. On the other
hand, browsers are known to fail to comply with this relatively new
approach.

> If the japanese character data is submitted through forms then i get
> correct data at server side, but when i set the src of frame then i
> get corrupt data at server side.

That's understandable, because form submission may work differently from URL
handling in browsers. So why don't you use forms?

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

[Back to original message]