Thx for reporting back. I changed this now in the SVN
http://svn.pmapper.net/trac/changeset/1264
armin
On 18/04/2012 15:13, Miha Požauko wrote:
> Your modification works.
>
> The reason i'm using windows-1250 is because i had problems with dadabik
> application.
> But anyway it would be better
Your modification works.
The reason i'm using windows-1250 is because i had problems with dadabik
application.
But anyway it would be better to have UTF-8. At least i know now that it works
with non-ASCII
characters too.
Thanks again Armin for your help.
On 17/04/2012 13:53, Miha Požauko wrote:
> Armin thanks for your answer and sorry i didn't mention modifications in my
> first question.
>
> All modifications in code are now restored to default settings.
>
> Following your explanation i managed to get characters showing properly
> except when us
Armin thanks for your answer and sorry i didn't mention modifications in my
first question.
All modifications in code are now restored to default settings.
Following your explanation i managed to get characters showing properly except
when using type "options" in search.xml ("suggest" is OK).
>
> en
> windows-1250
> 0
>
always use UTF-8 for defaultCharset if your language has other
characters than plain ASCII, and make your web server using UTF-8 as
default.
> To show characters like č, š, ž, Č, Š, Ž correctly in result window i
Hello again.
I hope anyone can really help me out here. I have been playing with different
settings to correctly show all characters in PostGIS table (they are in
Windows-1250) using P.mapper 4.2. And with following settings they appear like
they should (in TOC and in result window):
-mapfile:
Hey.
I'm having some problems with character encoding in search option list. my
search parameters are defined like this:
pgsql://postgres:luke@localhost:5001/dadabik_win1250
SELECT DISTINCT imeko, imeko FROM publ
