Hello Scott!

21 Jun 2012 15:27, Scott Street wrote to mark lewis:

 SS> ΤσάΤσΙΤσΙΤσΙΤσΨ

 SS> This will be translated - and should be.

so i can read it here scrampled

 SS> Well, might not be if you don't have utf-8 to iso8859-1 setup;

this is a no go !

 ss> if that is the case, then this message should come across as 
 SS> Content-type: text/plain; charset=unknown-8bit.

sure if unicode is just 8 bit

 SS> Good luck.

thanks for learning me more about it


i will share my xlat table again:

   ----- 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 -----

needs fixing ?


 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))