Hi-
Everything seems to be working ok, here's what I did:
I added fprintf(fdm,"Content-Type: text/plain; charset=\"*euc-jp*\"\n" )
to line 256 of the autorespond.c file, ran make and replaced the
original autorespond binary.
Now the Japanese text entered in the qmailadmin euc-jp encoded
autorespond web page will
display correctly on the client machine. The problem is that 95% or
more of the clients in
Japan use *ISO**-**2022**-**JP so any text that the client sends is
turned to garbage because
the mail client can't decipher 2 types of encodings in the same message.
So, I went back to autorespond.c and changed euc-jp to ISO-2022-JP, ran
make and copied
the new autorespond binary to /var/qmail/bin/.
The next trick was to get the euc-jp encoded qmailadmin web pages to
show up in iso-2022-jp.
I assumed that the language files were in
/usr/local/share/qmailadmin/lang and they were.
The problem is that my gentoo installation also had the same language
files in
/usr/share/qmailadmin/htmllib/lang/ and qmailadmin was using the files
in /usr/share
Once I ran *
cd */usr/share/qmailadmin/htmllib/lang/
*cat ja | nkf -j > ja.jis
cp ja.jis ja
The web pages showed up in iso-2022-jp and I was able enter Japanese text in
from qmailadmin
with iso-2022-jp.
Cheers,
David
*
*
David Sperling wrote:
Tom Collins wrote:
On Oct 26, 2005, at 10:59 AM, David Sperling wrote:
1. Is it safe to run make, make install in the autorespond2.0.2
directory?
Will compiling and installing autorespond cause any problems with my
current qmail,
qmail-admin install? The make file looks pretty harmless, but I've
got 100 domains on this machine.
Better be safe and ask than be sorry.
Autorespond is a separate program from vpopmail and qmailadmin.
Recompiling and reinstalling will have no effect on your existing
users. Future autoresponses will be sent with the new binary you
install, so you should test an autoresponder after installing the new
binary.
Great.
2. The changes to the ja language file didn't show up in the qmail
admin web pages.
Do I have to compile something to get the changes in the language
files to show up?
I don't think you'll see any change on the QmailAdmin pages. It
looks like the nkf program just changes from "euc-jp" charset to
"iso-2022-jp". If that charset is more common, it would make sense
for us to update the QmailAdmin distribution to use the updated ja file.
This is a tough call. Cell phones in Japan only work with iso-2022-jp
and Windows runs with iso-2022 as well.
About 50% of the linux/Unix run with EUC encoding which is what
qmail-admin ships with. 20% of linux/Unix
servers run iso-2022-jp and the rest (30%) run in UTF-8. My guess is
that UTF-8 is growing by about 5% a year
but iso-2022 will be with us for many years to come. Personally, I'd
like to see everything done in utf-8, but
then any mail sent to Japanese cell phones wouldn't be readable.
Switching the default to iso-2022-jp would make the responder work
with cell phones, but I have a feeling that EUC and Unicode guys
would get pretty irritated.
Any Japanese administrators have any input?
Cheers,
David
To confirm the change, you'd have to make a manual connection to your
web server and check the HTTP headers for the Content-Type header.
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet:
sniffter.com
