Michael Schulz schrieb:
Christoph,
I think that makes perfect sense. This would mean no UTF-8/ISO
decision in mapbender.conf, no two data sqls...
I would love to abandon the database option "ISO" as well, but I think
we still need it. I was just referring to the client side encoding.
It'll only require to set the webservers character set to UTF8 also?
Could this be a potential problem, e.g. with other software running on
the same server?
I think Mapbender can explicitly set the encoding in all documents it
sends and delivers. In how far is Apache involved?
Just playing devil's advocat, I think we'll eliminate a lot of
problmes with that.
Cheers, Michael
Christoph
2008/7/16 Christoph Baudson <[EMAIL PROTECTED]>:
Arnulf Christl schrieb:
Christoph Baudson wrote:
This is a proposal to serve UTF-8 encoded HTML pages only. In my opinion
there is no need to serve ISO-8859-1 pages.
All character set conversions (when interacting with a database) could be
done in PHP. So the architecture would change from
client: ISO/UTF8
server: UTF8
database: ISO/UTF8
to
client: ISO/UTF8
server: UTF8
database: ISO/UTF8
This will simplify things a lot and would make Mapbender less
error-prone. If anyone has any reason why we should still serve ISO pages,
please step up. I have no idea why we should.
Thanks,
Christoph
You confuse me, I cannot see the difference?
neither do I.
Here's what I meant
client: UTF8
server: UTF8
database: ISO/UTF8
Christoph
nr: copy and paste for beginners
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
