SH> Is it recommended we all add this? Will it cause any issues with other
SH> clients?
I for one wouldn't recommend it. It seems to trash the message header in an
unnecessary way.
This is what my part looks like, and with the unfortunate shortcomings
still in JamNNTPd when it comes to marrying UTF-8 with FTN, it so far seems to
be optimal. At least to me, and I today seem to be one of a few who have
problems with my umlauted name. :)
= = = = = =
# Syntax: read [,]
#
# Here you can configure the charset translations to be used when reading
# messages. CHRS and CODEPAGE are taken from the respective kludge lines.
# If you omit the xlat file, no actual charset translation will take place.
read CP437 iso-8859-1 437_iso.chs
read CP850 iso-8859-1 850_iso.chs
read CP865 iso-8859-1 865_iso.chs
readalias UKR CP866
readalias FIDO,2 CP866
readalias +7 CP866
read CP866 koi8-r 866_koi.chs
read IBMPC,850 iso-8859-1 850_iso.chs
read IBMPC,865 iso-8859-1 865_iso.chs
read IBMPC iso-8859-1 437_iso.chs
read LATIN-1 iso-8859-1
read UTF-8 utf-8
read * unknown-8bit
# Charset translations when posting messages
# The charset specified with "defaultread" is the charset JamNNTPd will use
# when no charset was specified. It can be overridden for specific areas in
# the jamnntpd.groups config file.
defaultpost iso-8859-1
# Syntax: read
#
# Here you can configure the charset translations to be used when posting
# messages. If you don't want to create CHRS kludges, enter "" as CHRS.
# You should have "read" translations set up for all charsets you accept or
# the receiver name of the posts migth not be translated properly.
#post iso-8859-1 LATIN-1
post iso-8859-1 IBMPC iso_437.chs
post koi8-r CP866 koi_866.chs
post utf-8 UTF-8
post us-ascii ""
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2.17) Gecko/20110414
* Origin: news://felten.yi.org (2:203/2)
|
