PP wrote:
>
> Hi,
> In fact AddDeafault Charset in Apache 1.3.12 doesn't fix encoding problem.
Yes, it just forces "charset=foo;" sending.
> But my question is:
> Is your mod_charset fix Apache encoding problem or Mysql. I want to know if
> it helps me with put some specail characters in iso-8859-2 to mysql table.
> For now I write Polish fonts in midgard site but they're not in mysql table.
Neither. Mod_charset (which is written by Alexey Tutubalin & Co, not by
me, in fact) just translates characters from several encodings
("client") to unified encoding on server (and vice versa). If you have
only one encoding table, mod_charset doesn't needed at all. So, the
problem might be in MySQL. MySQL has several options for supporting
different encodings in data:
1) Try to compile MySQL with --with-charset=latin2 option to configure.
2) Use SET OPTION CHARACTER SET character_set_name
In latter case the only value for "character_set_name" is 'cp1251_koi8'
which is defined in sql/convert.cc in sources of MySQL. You could add
your reencoding table, but the former case would be simplier for you.
It is not Midgard-related problem, it is problem of MySQL because by
default it works with Latin1 charset (and I'm recompiling MySQL always
with --with-charset=koi8 or --with-charset=cp1251 for my work).
--
Alexander.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
