1. Forum
  2. FidoNet
  3. FIDOTEST

  • IBMPC 2 = deprecated

    From August Abolins@2:221/360 to Michiel van der Vlist on Sat Mar 7 19:00:22 2020
    On 07/03/2020 8:55 a.m., Michiel van der Vlist : August Abolins wrote:

    @CHRS: IBMPC 2
    ^^^^^

    Obsolete and depricated per FTS-5003.

    Hello Michiel!

    OpenXP seems to only post messages with two CHRS types.

    If it detects only 7-bit chars, it uses ASCII 1

    If it detects at least one 8-bit char, then it uses IBMPC 2

    I thought FTSC documents common practices. The above is quite "common" for OpenXP. ;) Where does the decision to announce deprecation get decided?

    I'm just a user of the prog. If there is a specific replacement for IBMPC and how to achieve it, I would not know what it is.

    BTW, OpenXP doesn't care what chars are used in Origin line.
    According to the hard fast definition of what a fidonet "message" is, the Origin
    line is no included?

    --- TB68.4.1/Win7
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to August Abolins on Sun Mar 8 10:15:29 2020
    Hello August,

    On Saturday March 07 2020 19:00, you wrote to me:

    @CHRS: IBMPC 2
    aaaaaaaaaaa ^^^^^

    I wonder where the accented as comes from...

    Obsolete and depricated per FTS-5003.

    OpenXP seems to only post messages with two CHRS types.

    If it detects only 7-bit chars, it uses ASCII 1

    If it detects at least one 8-bit char, then it uses IBMPC 2

    That may have worked 30 years ago when Fidonet was still mostly limited to Northern America and the only "ASCII extension" in use was CP437. For the last two decades most of the messagaes in Fidonet are written in Cyrrilic and this algorithm fails miserably.

    I thought FTSC documents common practices. The above is quite
    "common" for OpenXP. ;)

    Another criterium for documenting something as a standard is "wide spread use".
    The algorithm used by OpenXp is not in "wide spread use".

    Where does the decision to announce deprecation get decided?

    The FTSC.

    I'm just a user of the prog.

    A prog that is obviously no longer up to standards.

    If there is a specific replacement for IBMPC and how to achieve it, I would not know what it is.

    There isn't. IBMPC can mean anything. Which is the main reason why its use was deprecated...

    BTW, OpenXP doesn't care what chars are used in Origin line.
    According to the hard fast definition of what a fidonet "message" is,
    the Origin line is no included?

    See FTS-004.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Tommi Koivula@2:221/1.11 to you on Sun Mar 8 11:32:26 2020
    Hi Michiel.

    08 Mar 20 10:15:28, Michiel van der Vlist wrote to August Abolins:

    Hello August,

    On Saturday March 07 2020 19:00, you wrote to me:

    @CHRS: IBMPC 2
    aaaaaaaaaaa ^^^^^

    I wonder where the accented as comes from...

    UTF-8 "support" in Jamnntpd is not perfect. ;)

    'Tommi

    ---
    * Origin: rbb soupgate, the fidonet nntp junction (2:221/1.11)
  • From August Abolins@2:221/1.58 to Michiel van der Vlist on Sun Mar 8 09:34:00 2020
    Hello Michiel!

    ** 08.03.20 - 10:15, Michiel van der Vlist wrote to August Abolins:

    MvdV>Hello August,

    MvdV>On Saturday March 07 2020 19:00, you wrote to me:

    |aAA> @CHRS: IBMPC 2
    |a|a|a|a|a|a|a|a|a|a|a ^^^^^

    MvdV>I wonder where the accented as comes from...


    Duh.... dunno. Ask TB/Jamnntp? :(


    MvdV>Another criterium for documenting something as a standard is "wide
    MvdV>spread use". The algorithm used by OpenXp is not in "wide spread
    MvdV>use".

    How is that measured?



    ../|ug

    --- OpenXP 5.0.43
    * Origin: If at first you don't succeed, call it Ver 1.0 (2:221/1.58)
  • From Michiel van der Vlist@2:280/5555 to August Abolins on Sun Mar 8 17:56:18 2020
    Hello August,

    On Sunday March 08 2020 09:34, you wrote to me:

    MvdV>> Another criterium for documenting something as a standard is "wide
    MvdV>> spread use". The algorithm used by OpenXp is not in "wide spread
    MvdV>> use".

    How is that measured?

    It is not measured, it is judged.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)