Hello Tommi!
25 Mar 2012 08:13, Tommi Koivula wrote to All:
TK> @MSGID: 2:203/2 4f6ec5ae
TK> @PID: JamNNTPd/Win32 1
TK> @CHRS: UTF-8 2
TK> @TZUTC: 0100
TK> @TID: CrashMail II/Win32 0.71
TK> testing |Ñ|ñ|Â
works from my jamnntpd ?
super if yes :)
----- xlat begins -----
# Charset configuration for JamNNTPd using Unicode
#
# It is necessary to still have the "read" translations for the charsets you
# will be posting in or JamNNTPd will not be able to translate the receiver
# name properly. Unfortunately posting in utf-8 is not possible at this time.
chsdir /etc/jamnntpd/xlat.d
defaultread IBMPC
read CP437 utf-8 437_utf.chs
read CP850 utf-8 850_utf.chs
read CP865 utf-8 865_utf.chs
read CP866 utf-8 866_utf.chs
read LATIN-1 utf-8 iso_utf.chs
read CP437 iso-8859-1 437_iso.chs
read CP850 iso-8859-1 850_iso.chs
read CP865 iso-8859-1 865_iso.chs
read CP866 koi8-r 866_koi.chs
read LATIN-1 iso-8859-1
# from jamnntpd
read UTF-8 utf-8
readalias IBMPC,850 CP850
readalias IBMPC,865 CP865
readalias IBMPC,866 CP866
readalias IBMPC CP437
defaultpost iso-8859-1
post iso-8859-1 LATIN-1
post koi8-r CP866 koi_866.chs
postalias windows-1252 iso-8859-1
postalias iso-8859-15 iso-8859-1
postalias us-ascii iso-8859-1
----- xlat ends -----
enjoy
Regards Benny
... there can only be one way of life, and it works :)
--- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))
* Origin: home.junc.org where qico is waiting (2:230/0)
|