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

[Bob Basques]

Dan,

Ahh, that's was I was thinking might need to be done.  Since it seems
that GeoMoose would need to somehow know what to expect before parsing
the return from MapServer.

bobb



>>> Dan Little <danlittle at yahoo.com> 11/04/08 9:32 AM >>>
Have you tried changing the encoding settings in the index.html file?




________________________________
From: Matej <matej at matnet.net>
To: geomoose-users at lists.sourceforge.net
Sent: Tuesday, November 4, 2008 9:17:31 AM
Subject: Re: [Geomoose-users] Special characters - "sh", "ch", "zh" -
Central European symbols - part 2

 
Hi,
 
I was looking at MapScript which would be an 
option, but due to the following fact I think that there must be an
"easier" 
solution maybe with some XML settings or something like that - when I 
click on the "Identify" tool and the result is open in the div 
"content_results_form" as a part of the GeoMoose window, the characters
DO NOT 
appear correctly. But when I get the direct link to the MapServer 
call (vith FireBug) that is being called by Geomoose, e.g.
"http://xxx.xxx.xxx.xxx/cgi-bin/mapserv?map=/home/webuser/identif.map&mapxy=468286.9195712629%20125082.02776175489&imgext=468282.0218372162%20125066.72580171067%20468308.97320987994%20125086.39975033894&layers=Boxes&imgsize=974%20711&mode=nquery"

in a separated window or a tab, those characters DO appear correctly.
And also 
when I set the charset of that window when the data is appearing
correctly the 
same charset as the GeoMoose window has, they look as they should.
 
That is the fact that is bothering me and I suspect 
that some method which performs the "call" of the Mapserver from
GeoMoose isn't 
capable of getting data differently than in utf-8, but it proves that
MapServer 
is returning the data in the iso-8859.2 charset correctly.
 
Thank you in advance,
Matej Serc
matej at matnet.net
----- Original Message ----- 
From: Fischer, Brian 
To: Matej ; geomoose-users at lists.sourceforge.net 
Sent: Monday, November 03, 2008 9:48  PM
Subject: RE: [Geomoose-users] Special  characters - "sh", "ch","zh" -
Central European symbols - part 2

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/referencemanual-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 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