I'm interested in information about current practices among mail/news
clients in the following areas. I'm interested in information both about the most common practices and any alternative ways of handling these things. Any direct information as well as pointers to documents to read and persons/companies/organizatons/institutions to contact will be appreciated.

1. In what order do mail/news clients using UTF-8 encoding of text that
should be displayed right-to-left (RTL) encode the characters on a line? Is
the first character on each line the left-most or the right-most in the
UTF-8 stream for that line?

2. Where is the end-of-line marker put? To the left or to the right of the UTF-8 stream for that line?

2. How do mail/news clients using UTF-8 encoding tell the software on the receiving end that a text should be displayed bottom-to-top (BTT)?

3. In what order do mail/news clients using UTF-8 to encode text that should
be displayed BTT encode the different lines of the text? Is the line that should be displayed at the bottom of the mail/article at the start or at the end of the UTF-8 stream?

4. How do mail/news clients UTF-8 encode texts that should be displayed column-wise? (I understand that such text may come in different variations: columns displayed RTL or LTR and contents of each column displayed TTB or
BTT.)

5. How do you think things should be done in these respects in FidoNet messages
containing UTF-8 encoded text?

---
* Origin: GET - The Point (2:201/505.1)

Hello Goran!

22 Aug 03 06:48, Goran Eriksson wrote to All:

5. How do you think things should be done in these respects in
FidoNet messages containing UTF-8 encoded text?

i will hope UTF (unicode) will get translated to LATIN-1 in the software that imports it to ftn network, and the software that export from ftn could translate to UTF (unicode), transperant ? :-)

Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/2.4.20-20.8 (i686))
* Origin: ftp://junc.org/ binkd 1.0a-241 xpoint@junc.org (2:237/53)

Hello Benny!

08 Nov 03 02:30, you wrote to Goran Eriksson:

5. How do you think things should be done in these respects in
FidoNet messages containing UTF-8 encoded text?

i will hope UTF (unicode) will get translated to LATIN-1 in the
software that imports it to ftn network, and the software that export
from ftn could translate to UTF (unicode), transperant ? :-)

Indeed, LATIN-1 should be the widely used charset in Fidonet.. But it's too late now..

I don't use LATIN-1 because many people don't do charset translation properly..
So I just send in CP850.

Regards,
Bo

--- GoldED+/LNX 1.1.4.7
* Origin: The Night Express - Roennede, Dk (2:236/100)

Hello Bo!

08 Nov 03 14:11, Bo Simonsen wrote to Benny Pedersen:

Indeed, LATIN-1 should be the widely used charset in Fidonet.. But
it's too late now..

with all that new linux software comming its not to late :-)

I don't use LATIN-1 because many people don't do charset translation properly.. So I just send in CP850.

-+- GoldED+/LNX 1.1.4.7

yep golded is to blame !

Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/2.4.20-20.8 (i686))
* Origin: ftp://junc.org/ binkd 1.0a-241 xpoint@junc.org (2:237/53)

Hello Benny!

08 Nov 03 20:25, you wrote to me:

Indeed, LATIN-1 should be the widely used charset in Fidonet..
But it's too late now..

with all that new linux software comming its not to late :-)

BTW there is pretty mutch FTN/BBS software for Linux. Except for there is no BBS system which actually satisfy me.. I did have the same feeling about the fileticker ;-)

I don't use LATIN-1 because many people don't do charset
translation properly.. So I just send in CP850.

-+- GoldED+/LNX 1.1.4.7

yep golded is to blame !

IMHO the best editor.. I can't stand to have a editor which doesn't do full nodelist lookup.

Regards,
Bo

--- GoldED+/LNX 1.1.4.7
* Origin: The Night Express - Roennede, Dk (2:236/100)

Hi Benny.

08-Nov-03 02:30:02, Benny Pedersen wrote to Goran Eriksson

Hello Goran!

22 Aug 03 06:48, Goran Eriksson wrote to All:

5. How do you think things should be done in these respects in
FidoNet messages containing UTF-8 encoded text?

i will hope UTF (unicode) will get translated to LATIN-1 in the
software that imports it to ftn network, and the software that
export from ftn could translate to UTF (unicode), transperant ? :-

That's not going to work too well for cyrillic text

Bye <=-

---
* Origin: Bad karma, yea Way bad karma.. (3:640/1042)

Hello Bo!

09 Nov 03 08:22, Bo Simonsen wrote to Benny Pedersen:

IMHO the best editor.. I can't stand to have a editor which doesn't
do full nodelist lookup.

but golded do sooks when it comes to charsets, it have troble with cp866, have you seen one single golded user that have this working ?

cp866 is no troble for msged, just the sender set the charset kluge, but i still have fun reading the russians :-)

Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/2.4.20-20.8 (i686))
* Origin: ftp://junc.org/ binkd 1.0a-241 xpoint@junc.org (2:237/53)

Hello Jasen!

10 Nov 03 22:20, Jasen Betts wrote to Benny Pedersen:

software that imports it to ftn network, and the software that
export from ftn could translate to UTF (unicode), transperant ? :-

That's not going to work too well for cyrillic text

yes it will if senders put the charset kluge in the msg, cp866 can be translated to latin-1 no trouble :-)

and cp866 is supported natively in msged, why translate ?


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/2.4.20-20.8 (i686))
* Origin: ftp://junc.org/ binkd 1.0a-241 xpoint@junc.org (2:237/53)

Hello Benny!

11 Nov 03 22:41, you wrote to me:

IMHO the best editor.. I can't stand to have a editor which
doesn't do full nodelist lookup.

but golded do sooks when it comes to charsets, it have troble with
cp866, have you seen one single golded user that have this working ?

No it actually hasn't.. My golded does properly charset convertion from CP866 to LATIN-1 the problem is that I can't do manually convertion.

cp866 is no troble for msged, just the sender set the charset kluge,
but i still have fun reading the russians :-)

That's right.. If timEd was ported properly it wouldn't be a problem either..

Regards,
Bo

--- GoldED+/LNX 1.1.4.7
* Origin: The Night Express - Roennede, Dk (2:236/100)