• Re: A question to all the

    From Joe Martin@1:104/57 to Dan Clough on Wed May 29 20:04:21 2019
    But if there is a compelling need for the ZC1 system to have
    8-bits enabled, I will gladly entertain discussion amongst RC's
    and ZC's to do so.

    The end result just better not cause problems for *me* or waste
    *my* time.

    If you are discussing/debating anything with Bjorn Felten, you can
    count on it being a waste of your time.

    You know, I've been 'somewhat' following this thread and am curious
    about the 'why' 8 bit (vs 7 bit) is such an issue. I get the one byte vs
    two bytes (characters) for unicode, just not the 8 bit vs 7 bit of a
    single byte (ie: high ascii). I also get what high ascii offers but
    since code pages are all about presentation and the nodelist is simply
    data, it would seem to me that the issue would be with the readers and
    or editors not the data. Dunno.

    Now just so you know, I've written my own mailer, nodelist compiler/diff processor, echomail tosser etc, so I'm all too familiar with the
    nodelist and FTSC specs in general, but I frankly never gave the whole
    8/7 bit issue a second thought.

    So if someone would enlighten me, I'd appreciate it. Please
    understand, this is simply a request for info with the main goal of
    ensuring my stuff continues to work like it's supposed to... Not to try
    and start something!

    <g>...

    Joe Martin

    --- ViaMAIL!/WC v2.00
    * Origin: ViaSoft Support BBS - Back online at 303-953-0568 (1:104/57)
  • From Holger Granholm@2:20/228 to Joe Martin on Thu May 30 09:41:00 2019
    In a message on 05-29-19 Joe Martin said to Dan Clough:

    Good evening Joe,

    You know, I've been 'somewhat' following this thread and am curious
    about the 'why' 8 bit (vs 7 bit) is such an issue.

    As far as the NODELIST goes I don't find a problem with ASCII 7 or 8,
    but considering the situation in Europe with many languages using 8-bit characters for letters that are not used in english, the situation is
    quite different.

    Just in swedish, finnish and norwegian we have letters Aa and Oo with
    two dots above the letter. We also have the Aa letter with a ring on top

    Other languages in the world also use high-ASCII (8-bit) characters.

    I don't have a problem with different characters in various languages
    since I have extended the code in my editor (The Semware Editor) to
    include conversion from/to ASCII 7/8, Latin-1 and Mac.

    Neither does the nodelist compiler in PCBoard care about characters.


    Have a good night,

    Holger


    .. If you find yourself in a hole -- stop digging.
    -- MR/2 2.30

    --- PCBoard (R) v15.22 (OS/2) 2
    * Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
  • From Henri Derksen@2:280/1208 to Joe Martin on Thu May 30 14:46:00 2019
    Hello Joe,

    You know, I've been 'somewhat' following this thread and am curious
    about the 'why' 8 bit (vs 7 bit) is such an issue.

    Because it can give problems, in mailreaders, and if the NodeList would
    carry characters with the 8 bit set, soms compiling software may go wrong.

    I get the one byte vs two bytes (characters) for unicode,
    just not the 8 bit vs 7 bit of a single byte (ie: high ascii).

    I'll show you, read on.

    I also get what high ascii offers but since code pages are all about presentation and the nodelist is simply data, it would seem to me that
    the issue would be with the readers and or editors not the data. Dunno.

    Many mailers need a compiled NodeList, so that compile process could go wrong when 8 bit characters are presented, hence it is still only 7 bit.

    Now just so you know, I've written my own mailer, nodelist compiler/diff processor, echomail tosser etc, so I'm all too familiar with the
    nodelist and FTSC specs in general, but I frankly never gave the whole
    8/7 bit issue a second thought.

    So if someone would enlighten me, I'd appreciate it. Please
    understand, this is simply a request for info with the main goal of ensuring my stuff continues to work like it's supposed to... Not to try
    and start something!

    For the completeness here a partial list of characters above 128:

    Special signs in Acorn Archimedes/AxThousend/RiscPC in RISC OS 3.xx
    and higher,
    or the IyonixPC, A9home, BeagleBoard xM, Panda Board, Raspberry Pi computers all with ISO 8859/1 Latin 1 character set/system font in RISC OS,
    in conjunction to M$-DOS/Windows with CP 437.

    To get by pressing Alt together with a digit
    at the numerical keypad:

    Acorn H Binairy | MSDos/Windows H Binairy
    ISO 8859/1 e bbbbbbbb | IBM CodePage e bbbbbbbb
    description Latin 1 x 76543210 | 437 USA/UK x 76543210
    |
    a\ a accent grave = Alt 224 E0 11100000 | = Alt 133 85 10000101 a/ a accent aigu = Alt 225 E1 11100001 | = Alt 160 A0 10100000 a^ a accent circonflexe = Alt 226 E2 11100010 | = Alt 131 83 10000011 a~ a tilde = Alt 227 E3 11100011 | =
    a" a trema/umlaut = Alt 228 E4 11100100 | = Alt 132 84 10000100 ao a with o = Alt 229 E5 11100101 | = Alt 134 86 10000110 ae a with e = Alt 230 E6 11100110 | = Alt 145 91 10010001 c, c with cedille = Alt 231 E7 11100111 | = Alt 135 87 10000111 e\ e accent grave = Alt 232 E8 11101000 | = Alt 138 8A 10001010 e/ e accent aigu = Alt 233 E9 11101001 | = Alt 130 82 10000010 e^ e accent circonflexe = Alt 234 EA 11101010 | = Alt 136 88 10001000 e" e trema/umlaut = Alt 235 EB 11101011 | = Alt 137 89 10001001 i\ i accent grave = Alt 236 EC 11101100 | = Alt 141 8D 10001101 i/ i accent aigu = Alt 237 ED 11101101 | = Alt 161 A1 10100001 i^ i accent circonflexe = Alt 238 EE 11101110 | = Alt 140 8C 10001100 i" i trema/umlaut = Alt 239 EF 11101111 | = Alt 139 8B 10001011 n~ n tilde = Alt 241 F1 11110001 | = Alt 164 A4 10100100 o\ o accent grave = Alt 242 F2 11110010 | = Alt 149 95 10010101 o/ o accent aigu = Alt 243 F3 11110011 | = Alt 162 A2 10100010 o^ o accent circonflexe = Alt 244 F4 11110100 | = Alt 147 93 10010011 o~ o tilde = Alt 245 F5 11110101 | =
    o" o trema/umlaut = Alt 246 F6 11110110 | = Alt 148 94 10010100 o/ o with slash = Alt 248 F8 11111000 | = Alt 237 ED 11101101 u\ u accent grave = Alt 249 F9 11111001 | = Alt 151 97 10010111 u/ u accent aigu = Alt 250 FA 11111010 | = Alt 163 A3 10100011 u^ u accent circonflexe = Alt 251 FB 11111011 | = Alt 150 96 10010110 u" u trema/umlaut = Alt 252 FC 11111100 | = Alt 129 81 10000001

    This table is still incomplete, and only for personal reference.
    See: Resources:$.Apps.!Chars from the RISC OS IconBar.
    I have not the energy to also make such a table for CodePage 850 (International), or others.

    Bjorn Felten and Michiel van der Vlist know everthing about CP850.

    Greetings from: Henri Derksen, SysOp UniCornBBS.demon.nl.

    ---
    * Origin: Computing Apart Together (2:280/1208)
  • From Joe Martin@1:104/57 to Holger Granholm on Sat Jun 1 11:56:52 2019
    In a message on 05-29-19 Joe Martin said to Dan Clough:

    Good evening Joe,

    You know, I've been 'somewhat' following this thread and am
    curious JM> about the 'why' 8 bit (vs 7 bit) is such an issue.

    As far as the NODELIST goes I don't find a problem with ASCII 7 or 8,
    but considering the situation in Europe with many languages using
    8-bit characters for letters that are not used in english, the
    situation is quite different.

    Just in swedish, finnish and norwegian we have letters Aa and Oo with
    two dots above the letter. We also have the Aa letter with a ring on
    top
    Other languages in the world also use high-ASCII (8-bit) characters.

    I don't have a problem with different characters in various languages
    since I have extended the code in my editor (The Semware Editor) to
    include conversion from/to ASCII 7/8, Latin-1 and Mac.

    Neither does the nodelist compiler in PCBoard care about characters.

    Okay, still not sure where the problem is though. Is it the 'result' of
    a compile and the presenting program doesn't know what codepage to use
    or is it causing compile-time issues?

    Have a good night,

    I appreciate the response.

    Regards,

    Joe Martin

    --- ViaMAIL!/WC v2.00
    * Origin: ViaSoft Support BBS - Back online at 303-953-0568 (1:104/57)
  • From Holger Granholm@2:20/228 to Joe Martin on Sun Jun 2 11:53:00 2019
    In a message on 06-01-19 Joe Martin said to Holger Granholm:

    Hello Joe,

    I don't have a problem with different characters in various languages
    since I have extended the code in my editor (The Semware Editor) to
    include conversion from/to ASCII 7/8, Latin-1 and Mac.

    Neither does the nodelist compiler in PCBoard care about characters.

    Okay, still not sure where the problem is though. Is it the
    'result' of a compile and the presenting program doesn't know what
    codepage to use or is it causing compile-time issues?

    I appreciate the response.

    Thanks Joe.


    Have a nice day,

    Holger


    .. Political Season: Does this mean we can shoot them?!
    -- MR/2 2.30


    --- PCBoard (R) v15.22 (OS/2) 2
    * Origin: Coming to you from the Sunny Aland Islands. (2:20/228)