[Geomoose-users] Special characters - "sh", "ch", "zh" - Central European symbols - part 2

[Fischer, Brian]

Matej,

 

I think this would be a question for the mapserver mailing list.  I have
never used international characters so I have no experience with them.
I wonder if it is an issue with the MapInfo format. I do know mapserver
encodes the attributes for HTML, but will leave them as is if you do
something like this:

 

[DBASE item name],[DBASE item name_esc],[DBASE item name_raw] 

Item name from the attribute table of a queried layer. Only attributes
for the active query layers are accessible. Case must be the same as
what is stored in the DBASE file. ArcView, for example, uses all caps
for shapefile field names. Available only when processing query results.

By default the attributes are encoded especially for HTML
representation. In addition the escaped version (for use in URLs) as
well as the raw data is available.

This is from the mapserver website under the template reference guide
(http://mapserver.gis.umn.edu/docs/reference/templatereference/reference
manual-all-pages).  Maybe it won't do this for MapInfo files.

 

Just an idea,

Brian

 

Brian Fischer

Houston Engineering, Inc.

Maple Grove, MN

(763) 493-4522

 

From: Matej [mailto:matej at matnet.net] 
Sent: Monday, November 03, 2008 2:36 PM
To: geomoose-users at lists.sourceforge.net
Subject: [Geomoose-users] Special characters - "sh", "ch","zh" - Central
European symbols - part 2

 

Hi,

 

I have been further investigating this issue and I am out of ideas what
to do. Let me explain more. I have data with those symbols in a MapInfo
(.TAB file has the entry !charset WindowsLatin2 for charset definition).
As I mentioned before, MapServer returns correct data and when I open it
in the different browser everything is displayed as it should be.

But when the results are open in the div inside geomoose, it is always
(and I mean always) displayed in utf-8 encoding. I have found out that
it is typical behaveour for setRequestHeader to always return data in
utf-8. I tried adding "charset=iso-8859-2" to those two setRequestHeader
calls, but I get no different results. 

Now I don't know if I should also write on the MapServer's mailing list
if there is a chance to convert the data from mode=nquery to specified
encoding since I think that I MUST get the results of the query in utf-8
from Mapserver otherwise this won't work. But searching around, there is
no option for that. 

 

Maybe there is a way of replacement some characters before displaying
them? 

 

Thank you for any help in advance,

Matej Serc

matej at matnet.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20081103/a2676741/attachment.html