Hi, I have installed this newest version_1, and will do some detailed test these days.
I se the reference map is not "synchronized" with the main map, I see there are extent definitions in map file (for example for countries) that do no "cover" the entire shape file. And since I am often having similar problems, I am asking as a general question: how to create the reference map in most simple and correct way? How to set extents properly? regards, dejan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Armin Burger > Sent: Sunday, November 06, 2005 6:15 PM > To: [EMAIL PROTECTED] > Subject: [Pmapper-users] New intermediate versions > > > I uploaded 2 intermediate versions for p.mapper 1 and 2. > > http://www.pmapper.de/dl/pmapper1_2005-11-06.zip > http://www.pmapper.de/dl/pmapper2_2005-11-06.zip > > Both should now have less problems with multi-language settings and > character sets. I noticed that with Mozilla browsers and some server > settings the special characters were not displayed correctly > (a '?' was > displayed). The reason seems to be related to Mozilla that > cannot well > guess the character set. > > So for version 1 and already existing applications it would be > sufficient to add a line in common.php that specifies the > character set, > like > > header("Content-type: text/html; charset=ISO-8859-1"); > > or > > header("Content-type: text/html; charset=UTF-8"); > (if your language files are UTF encoded) > > I updated pmapper 1 to specify that in the config.ini (the same for > pmapper 2, but there the definition of the charset has to done in > various files). > > When I made some tests I realized that the SQLite database I > prefer for > the multilanguage settings ('localedb.db') unfortunately does not > correctly implement UTF-8. So if you are using anything else than > character set ISO-8859-1 you should stay at the file-based > solution, now > with locale files like 'language_it.php'. In any case I would > recommend > using UTF-8 where ISO-8859-1 is not sufficient. Text editors > more likely > support UTF than other ISO sets. 'Scite' eg. is a good editor for UTF. > > There were some significant changes in parts of pm 1 in order to have > version 1 and 2 better synchronized. The changes will apply to the > planned release 1.1.0. They mainly tackle > * language settings: definitions of language strings moved out of > the map file, everything is handled via the '_()' function > * initialization of various settings modified and now like in pm2 > * facilitated attribute search definition, like in pm2 > * functionality to re-size the map window > * a preliminary test for including WMS layers from the client > * an easier solution to specify extent buffers for point layers > (in the config.ini) > > A list of modified files is in the changelog.txt. > > I hope the modifications did not add too many new bugs :-) > > Armin > > > > > > > > > > _______________________________________________ > Pmapper-users mailing list > [EMAIL PROTECTED] > http://faunalia.it/cgi-bin/mailman/listinfo/pmapper-users >
