Gambin Dejan wrote: > Hi, > > I have a few questions regarding the language handling in pmapper > version > > 1. Can you define the default language in config.ini? So I don't have to > put in in the URL....I can do it of course but since we don't have cvs > or something like this it is better that you do it...
The default language is set in frameview.phtml at the very beginning. Ie, if no session or GET variable is defined then it takes the one defined there. I will check if it will create problems if it is set via the config.ini. > 2. Is there a way to use the ENCODING parameter for showing the result > of the query...for example I have a layer that has labels in > Windows-1250 and I have defined ENCODING WINDOWS-1250 in mapfile. But I > still have to use iconv after getting the query result in info.phtml to > convert from Windows 1250 to ISO-8859-2 (this is the language encoding I > am using on site). Is there maybe antoher way we can set this? I will > help in developing the language handling because this is something that > bothers me all the time > I don't know what happens if the character set in the shapefile is different than that used for the overall application. Also what happens, if you mix shapefiles with different encodings? If all shapefiles are in Win 1250 you could add this settings as header in the info.phtml and overwrite the settings from the config.ini. But does Win 1250 really support all characters you need? I guess that mixing encodings for one page always will lead to problems. One could also try to use the PHP functions to convert correctly the query results. You're welcome to experiment on this, I don't think I will find the time in the near future to test various settings and combinations. > 3. I think my characters are not shown correctly after setting > ISO-88859-2 in config.ini...maybe I still have to define this in > frameview.phtml? The setting in the config.ini are read by common.php and this is loaded in pratically all phtml files, adding a header with this encoding. I just tested it with ISO-8859-1 and UTF-8 and it worked fine for me. I don't know if the editor you are using for the language files supports ISO-8859-2. The header also mainly applies for the text rendered in the user interface. What you get from queries with shapefiles in different encodings is another question (see above). > > > regards, dejan > >
