• FMail 2.3.0.1 public beta release

    From Wilfred van Velzen@2:280/464 to All on Tue Mar 19 22:37:31 2024

    Hi All,

    There is an update for the beta.

    ChangeLog:

    2024-03-19 2.3.0.1-Beta
    * Make fconfig linux use a 80x24 terminal instead of the DOS default 80x25
    * Replaced a number of memcpy() usages with memmove(), because of possible
    overlapping memory in src and dst. Fixed at least 1 bug in Nodemgr Areas
    configuration with this.

    2024-03-17 2.3.0.1-Beta
    * Check for the right terminal size: 80x25 instead of 80x24
    * Some cosmetic code changes.


    Downloads:

    http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.1-Beta20240319.zip

    http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.1-Beta20240319.zip


    For the linux version, instead of using above statically linked executables,
    I recommend, if you have the setup/tools for it,
    to download the sources with git, and compile it yourself.

    These are the steps/commands:

    # git clone git://git.code.sf.net/p/fmail/code FMail
    # cd FMail
    # git checkout --track origin/fconfig_linux
    # mkdir cmake-build
    # cd cmake-build
    # cmake ..
    # make


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From IB Joe@1:342/200 to Wilfred van Velzen on Wed Mar 20 08:59:51 2024
    On 19 Mar 2024, Wilfred van Velzen said the following...

    Downloads:

    http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.1-Beta20240319.zip

    http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.1-Beta20240319.zip


    Wilfred... you should make OS/2 exes for those who don't have the capability...

    Bye,

    IB Joe, Pronouns (FJB/LGB)
    AKA Joe Schweier
    SysOp of 4A 6F 65 73 42 42 53
    -=JoesBBS.com=-

    ... Nine times out of ten the statisticians are wrong

    --- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
    * Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/200)
  • From Wilfred van Velzen@2:280/464 to IB Joe on Wed Mar 20 16:16:17 2024
    Hi IB,

    On 2024-03-20 08:59:51, you wrote to me:

    Downloads:

    http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.1-Beta20240319.zip
    http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.1-Beta20240319.zip

    http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.1-Beta20240319.zip
    http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.1-Beta20240319.zip


    Wilfred... you should make OS/2 exes for those who don't have the capability...

    I can't, and I doubt the current source still compiles for OS/2. Or maybe it will if there is a gnu compiler for OS/2, like mingw for windows?

    But there is the OS/2 version by the original author from 2001:

    http://www.vlzn.nl/fmail/files/fml2_160.zip


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From IB Joe@1:342/200 to Wilfred van Velzen on Wed Mar 20 12:05:24 2024
    On 20 Mar 2024, Wilfred van Velzen said the following...


    But there is the OS/2 version by the original author from 2001:

    http://www.vlzn.nl/fmail/files/fml2_160.zip


    I have FastEcho OS/2 ... I just wanted the latest and greatest...

    Thanx

    IB Joe, Pronouns (FJB/LGB)
    AKA Joe Schweier
    SysOp of 4A 6F 65 73 42 42 53
    -=JoesBBS.com=-

    ... There are three kinds of people: Those who can count, and those who can't

    --- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
    * Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/200)
  • From Wilfred van Velzen@2:280/464 to IB Joe on Wed Mar 20 19:08:48 2024
    Hi IB,

    On 2024-03-20 12:05:24, you wrote to me:

    But there is the OS/2 version by the original author from 2001:

    http://www.vlzn.nl/fmail/files/fml2_160.zip

    I have FastEcho OS/2 ...

    I hope you don't have out of zone links, because FastEcho is known to strip seen-by's, when linking with out of zone links.

    I just wanted the latest and greatest...

    Who doesn't!? ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From IB Joe@1:342/200 to Wilfred van Velzen on Wed Mar 20 12:46:33 2024
    On 20 Mar 2024, Wilfred van Velzen said the following...


    http://www.vlzn.nl/fmail/files/fml2_160.zip


    Does this need a key??


    I hope you don't have out of zone links, because FastEcho is known to strip seen-by's, when linking with out of zone links.


    For now no...


    I just wanted the latest and greatest...

    Who doesn't!? ;-)

    :)

    IB Joe, Pronouns (FJB/LGB)
    AKA Joe Schweier
    SysOp of 4A 6F 65 73 42 42 53
    -=JoesBBS.com=-

    ... A SQL query walks into a bar and sees two tables. Asks: 'Can I join you?'

    --- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
    * Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/200)
  • From Wilfred van Velzen@2:280/464 to IB Joe on Wed Mar 20 20:47:04 2024
    Hi IB,

    On 2024-03-20 12:46:33, you wrote to me:

    http://www.vlzn.nl/fmail/files/fml2_160.zip

    Does this need a key??

    It works perfectly fine without a key. There is only a few things you can't configure without a key.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Tue Mar 26 20:20:18 2024
    On Wed, 20 Mar 2024 03:37:30 +0100, Wilfred Van Velzen -> All wrote:

    There is an update for the beta.

    Compiled today..

    fconfig seems to work fine so far.

    First, is it just me or does the custom tearline only allow 24 characters?

    Second, Am I not able to make JAM netmail areas? Or am I doing something wrong?

    Third, and last for now.. Is the backbone.na import format only for file areas? I've made one with message areas with 168 lines of this format:

    ECHOTAG <DESCRIPTION>

    And I get "0 descriptions imported".

    Sorry, I haven't used a GUI menu driven tosser configuration program in quite some time. I don't even know what half of the options mean yet. :)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Wed Mar 27 09:13:20 2024
    Hi Nicholas,

    On 26 Mar 24 20:20, Nicholas Boel wrote to Wilfred van Velzen:
    about: "FMail 2.3.0.1 public beta release":

    There is an update for the beta.

    Compiled today..

    fconfig seems to work fine so far.

    Nice!

    If I may ask, which linux distribution/version are you using? And which termimal?

    First, is it just me or does the custom tearline only allow 24
    characters?

    Yes, that is the maximum, because that is the room for it that is reserved for it in the config file. I don't know why this is. I searched the ftsc docs, but it doesn't mention a length limit for tear lines.

    Second, Am I not able to make JAM netmail areas? Or am I doing
    something wrong?

    They are not supported.

    Third, and last for now.. Is the backbone.na import format only for
    file areas? I've made one with message areas with 168 lines of this format:

    ECHOTAG <DESCRIPTION>

    And I get "0 descriptions imported".

    I have to look into this. But it isn't for file areas, because fmail doesn't do anything with file areas.

    Sorry, I haven't used a GUI menu driven tosser configuration program
    in quite some time. I don't even know what half of the options mean
    yet. :)

    Me neither. ;-)

    But there is always the description on the bottom line when you are on an option. Or if you are desperate the doc file! ;-)


    Wilfred.

    --- FMail-W64 2.3.0.1-B20240319
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Wed Mar 27 17:39:50 2024
    On Wed, 27 Mar 2024 14:13:20 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

     NB>> fconfig seems to work fine so far.

    Nice!

    If I may ask, which linux distribution/version are you using? And which termimal?

    Archlinux, 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35 +0000 x86_64 GNU/Linux

    I use PuTTY from a Windows 11 machine to connect to the VM via SSH (same as how I access Golded, if you remember that conversation). Full UTF-8. I did have to enable the "Enable VT100 line drawing even in UTF-8 mode" option in Putty in order for it to display correctly. Otherwise I haven't found any issues compiling or using it, or even saving.. besides what I've mentioned below.

     NB>> First, is it just me or does the custom tearline only allow 24
     NB>> characters?

    Yes, that is the maximum, because that is the room for it that is reserved for it in the config file. I don't know why this is. I searched the ftsc docs, but it doesn't mention a length limit for tear lines.

    Is there an easy way to up that to 75? (this allows for the "--- ", so you could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I suppose?)

    I don't even have it fully setup yet and I'm already requesting features. :)

     NB>> Second, Am I not able to make JAM netmail areas? Or am I doing
     NB>> something wrong?

    They are not supported.

    Ok. That's what I gathered when I couldn't name the JAM base.

     NB>> Third, and last for now.. Is the backbone.na import format only for
     NB>> file areas? I've made one with message areas with 168 lines of this
     NB>> format:

     NB>> ECHOTAG     <DESCRIPTION>

     NB>> And I get "0 descriptions imported".

    I have to look into this. But it isn't for file areas, because fmail doesn't do anything with file areas.

    Ok. Let me know if you find something, or if I'm doing something wrong. Permissions don't seem to be the issue. I'm running everything as the same user/group (the only user/group on that VM, actually) that I compiled it with.

    But there is always the description on the bottom line when you are on
    an option. Or if you are desperate the doc file! ;-)

    I've had to read most of them multiple times, and then sometimes look at the doc file for a more detailed description. Even after that I'm still confused on a few options that I've never used. Guessing leaving them default probably won't hurt anything. :)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Rob Swindell@1:103/705 to Nicholas Boel on Wed Mar 27 16:19:44 2024
    Re: FMail 2.3.0.1 public beta release
    By: Nicholas Boel to Wilfred van Velzen on Wed Mar 27 2024 05:39 pm

    NB>> First, is it just me or does the custom tearline only allow 24
    NB>> characters?

    Yes, that is the maximum, because that is the room for it that is reserved for it in the config file. I don't know why this is. I searched the ftsc docs, but it doesn't mention a length limit for tear lines.

    Is there an easy way to up that to 75? (this allows for the "--- ", so you could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I suppose?)

    Tear lines (starting with "--- ") don't normally have FidoNet addresses in them. Are you thinking of an origin line (starting with " * Origin:") ?
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #12:
    C128 = Commodore 128 (personal computer)
    Norco, CA WX: 70.6F, 47.0% humidity, 8 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nicholas Boel@1:154/10 to Rob Swindell on Wed Mar 27 18:30:18 2024
    On Wed, 27 Mar 2024 21:19:44 -0700, Rob Swindell -> Nicholas Boel wrote:

    Tear lines (starting with "--- ") don't normally have FidoNet
    addresses in them. Are you thinking of an origin line (starting with
    " * Origin:") ?

    No. I was thinking of the tearline, but was apparantly confusing the two when I mentioned the fidonet address. :)

    75 it is, then.. please!

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Thu Mar 28 09:09:19 2024
    Hi Nicholas,

    On 2024-03-27 17:39:50, you wrote to me:

    If I may ask, which linux distribution/version are you using? And
    which termimal?

    Archlinux, 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35 +0000 x86_64 GNU/Linux

    Nice to know! I can't test them all! ;-)

    I use PuTTY from a Windows 11 machine to connect to the VM via SSH
    (same as how I access Golded, if you remember that conversation). Full UTF-8. I did have to enable the "Enable VT100 line drawing even in
    UTF-8 mode" option in Putty in order for it to display correctly. Otherwise I haven't found any issues compiling or using it, or even saving.. besides what I've mentioned below.

    And the discussion to get my terminals right for golded, continued until yesterday! ;-)
    But I now seem to have it as good as it can get.

    Yes, that is the maximum, because that is the room for it that is
    reserved for it in the config file. I don't know why this is. I
    searched the ftsc docs, but it doesn't mention a length limit for
    tear lines.

    Is there an easy way to up that to 75? (this allows for the "--- ",

    Not so easy. There is reserve space in the binary config file, but not directly after the current field.
    So you need code around it for compatibility to use the old or new field. But I don't find this a very important new feature.
    The tearline is mostly used for version info of the generating software, and fmail already handles that very well.

    so you could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I suppose?)

    I noticed you already noticed your mistake here. ;-)

    I don't even have it fully setup yet and I'm already requesting
    features. :)

    Well it is good to have some fresh eyes on it, to suggest improvements for fmail. So keep them comming! ;-)

     NB>>> Third, and last for now.. Is the backbone.na import format only
     NB>>> for file areas? I've made one with message areas with 168 lines of
     NB>>> this format:

     NB>>> ECHOTAG     <DESCRIPTION>

     NB>>> And I get "0 descriptions imported".

    I have to look into this. But it isn't for file areas, because fmail
    doesn't do anything with file areas.

    Ok. Let me know if you find something, or if I'm doing something wrong.

    It crossed my mind you could test importing files with different line endings (linux vs dos).

    Permissions don't seem to be the issue. I'm running everything as the
    same user/group (the only user/group on that VM, actually) that I
    compiled it with.

    Ok, good you thought of this, because that is often an issue on linux systems.

    But there is always the description on the bottom line when you are
    on an option. Or if you are desperate the doc file! ;-)

    I've had to read most of them multiple times, and then sometimes look at the
    doc file for a more detailed description. Even after that I'm still confused
    on a few options that I've never used. Guessing leaving them default probably
    won't hurt anything. :)

    Probably... ;)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6 to Nicholas Boel on Fri Mar 29 13:50:20 2024
    On 27.03.2024 1:20, Nicholas Boel wrote:

    Third, and last for now.. Is the backbone.na import format only for
    file areas? I've made one with message areas with 168 lines of this
    format:

    ECHOTAG <DESCRIPTION>

    And I get "0 descriptions imported".

    I created a text file with nano. Echoarea descriptions imported fine with fconfig.

    'Tommi

    --- FMail-lnx64 2.3.0.2-B20240329
    * Origin: news://news.fidonet.fi (2:221/6.0)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Fri Mar 29 18:32:00 2024
    Hello Wilfred,

    On Thu, 28 Mar 2024 14:09:18 +0100, you wrote:

    And the discussion to get my terminals right for golded, continued until yesterday! ;-)
    But I now seem to have it as good as it can get.

    I've been keeping up. Glad you were able to get it all sorted!

    You're still way luckier than most, if you have been able to use Golded for all those years without having to use translation tables. I thought something was weird when you told me that. :)

    Not so easy. There is reserve space in the binary config file, but not directly after the current field.

    Boooo.

    So you need code around it for compatibility to use the old or new
    field. But I don't find this a very important new feature.

    Not a new feature, really. Just fixing an old one.

    The tearline is mostly used for version info of the generating software, and fmail already handles that very well.

    Some generating software uses much more space than FMail does when it comes to the tearline. What if one wants to put FMail's information in the TID kludge, instead, so the tearline can be used for the editor information?

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Tommi Koivula on Fri Mar 29 18:54:44 2024
    I've made one with message areas with 168 lines of this format:

    ECHOTAG <DESCRIPTION>

    And I get "0 descriptions imported".

    I created a text file with nano. Echoarea descriptions imported fine
    with fconfig.

    I just tried creating a text file (also with nano) with a single line, test.na:

    FMAIL_HELP FMAIL SUPPORT

    It didn't import it. So I don't know what the problem is.

    1) I've tried putting it in the same directory as fconfig and not using directories.

    2) I've tried typing out the entire directory structure to the file.

    3) I've tried renaming test.na to backbone.na, and backbone.NA, with no luck.

    With all of these options it obviously finds the file, or it would have told me it couldn't.

    Does your "Sysop Name" in fconfig need to match the user and/or group you're running it with?

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Tommi Koivula@2:221/6 to Nicholas Boel on Sat Mar 30 09:05:31 2024
    On 30.03.2024 1:54, Nicholas Boel wrote:

    I just tried creating a text file (also with nano) with a single line, test.na:

    FMAIL_HELP FMAIL SUPPORT

    It didn't import it. So I don't know what the problem is.

    1) I've tried putting it in the same directory as fconfig and not using directories.

    2) I've tried typing out the entire directory structure to the file.

    3) I've tried renaming test.na to backbone.na, and backbone.NA, with no luck.

    With all of these options it obviously finds the file, or it would have told me it couldn't.

    Let's see how this screenshot looks like. :)

    ┌───────────────────────────────────────────────────────────────────────┐
    │ FConfig-lnx64-2.3.0.2-Beta20240329 - Configuration utility
    ┌─┌───── Import config ┐
    ┌───│ │ │
    │ │ │ Import Areas.BBS │
    │ Mi│ │ Import RA info │
    │ Sy│ │ Import Folder.F┌─────────────────────────┐
    │ Im│ │ Import Backbone│ │
    │ Up│ │ │ 1 descriptions imported │



    Does your "Sysop Name" in fconfig need to match the user and/or
    group you're running it with?

    No. I run fmail and fconfig as "ftn". I created the test.na file as "tommi". Works.

    'Tommi

    --- FMail-lnx64 2.3.0.2-B20240329
    * Origin: jamnntpd/lnx (2:221/6.0)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 11:06:40 2024
    Hi Nicholas,

    On 2024-03-29 18:32:00, you wrote to me:

    And the discussion to get my terminals right for golded, continued
    until yesterday! ;-) But I now seem to have it as good as it can
    get.

    I've been keeping up. Glad you were able to get it all sorted!

    You're still way luckier than most, if you have been able to use Golded for
    all those years without having to use translation tables. I thought something
    was weird when you told me that. :)

    Most text in fido messages is just ascii. So if you're not bothered by the occasional weird character, your fine! ;-)

    So you need code around it for compatibility to use the old or new
    field. But I don't find this a very important new feature.

    Not a new feature, really. Just fixing an old one.

    Does something that has been working like this for 30 years, without complaints, really needs fixing?

    The tearline is mostly used for version info of the generating
    software, and fmail already handles that very well.

    Some generating software uses much more space than FMail does when it comes to
    the tearline. What if one wants to put FMail's information in the TID kludge,
    instead, so the tearline can be used for the editor information?

    FMail can be configured to just use the TID, so your editor can do what it wants with the tearline.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 11:19:26 2024
    Hi Nicholas,

    On 2024-03-29 18:54:44, you wrote to Tommi Koivula:

    I've made one with message areas with 168 lines of this format:

    ECHOTAG <DESCRIPTION>

    And I get "0 descriptions imported".

    I created a text file with nano. Echoarea descriptions imported fine
    with fconfig.

    I just tried creating a text file (also with nano) with a single line, test.na:

    FMAIL_HELP FMAIL SUPPORT

    I tried the same.

    It didn't import it. So I don't know what the problem is.

    1) I've tried putting it in the same directory as fconfig and not using directories.

    2) I've tried typing out the entire directory structure to the file.

    3) I've tried renaming test.na to backbone.na, and backbone.NA, with no luck.

    These shouldn't matter. If the file can't be opened, it wil say so.

    With all of these options it obviously finds the file, or it would
    have told me it couldn't.

    Indeed.

    Does your "Sysop Name" in fconfig need to match the user and/or group you're running it with?

    Those have nothing to do with each other.

    What I found out while testing, is that the area(s) you want to import the description for needs to already exist in the area configuration. It won't create new areas. Was this the case in your tests?


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Mar 30 08:50:24 2024
    On Sat, 30 Mar 2024 16:06:40 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    Most text in fido messages is just ascii. So if you're not bothered by the occasional weird character, your fine! ;-)

    I suppose. With all else that bothers you in regards to FTN messaging, I figured you would have been one of the pioneers on making it work correctly, though. :)

    Does something that has been working like this for 30 years, without complaints, really needs fixing?

    Not at all. The majority of the handful of people using it probably don't care much about the technical aspects of these programs, though.

    FMail can be configured to just use the TID, so your editor can do what it wants with the tearline.

    Yes sir!

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Mar 30 08:54:26 2024
    On Sat, 30 Mar 2024 16:19:26 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    What I found out while testing, is that the area(s) you want to import the description for needs to already exist in the area configuration. It won't create new areas. Was this the case in your tests?

    Yes!

    I have 0 areas in my area configuration. That is kind of the whole point of importing from backbone.na (or areas.bbs, or any other for that matter). To create the areas and add their descriptions.

    Is the original intent just meant to import the descriptions to said areas that were already entered manually? If so, I digress. 30 years is a long time for nobody to complain about that one.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 15:02:32 2024
    Hi Nicholas,

    On 2024-03-30 08:50:24, you wrote to me:

    Most text in fido messages is just ascii. So if you're not bothered
    by the occasional weird character, your fine! ;-)

    I suppose. With all else that bothers you in regards to FTN messaging, I figured you would have been one of the pioneers on making it work correctly,
    though. :)

    Am I? But indeed it takes effort to get your terminals, locale, and charset settings just right.

    And there are limitations. You can't display utf correctly. And you have to choose a native charset. Any character not supported by the charset, can't be displayed correctly. I can probably not view Russian messages correctly for instance...

    Bye, Wilfred.

    --- FMail-lnx64 2.3.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 15:08:26 2024
    Hi Nicholas,

    On 2024-03-30 08:54:26, you wrote to me:

    What I found out while testing, is that the area(s) you want to
    import the description for needs to already exist in the area
    configuration. It won't create new areas. Was this the case in your
    tests?

    Yes!

    I have 0 areas in my area configuration. That is kind of the whole point of
    importing from backbone.na (or areas.bbs, or any other for that matter). To
    create the areas and add their descriptions.

    Is the original intent just meant to import the descriptions to said areas that were already entered manually?

    It says so in the bottom line description for the function:

    "Import descriptions from Backbone.NA into fmail.ar"

    On the other hand the areas.bbs import I think should create areas, judging from the description:

    "Convert Areas.BBS into fmail.ar"

    But that is a more complex file format, then the simple .na format.

    If so, I digress. 30 years is a long time for nobody to complain about that one.

    Apparently... ;-)

    But there are also import functions for a number of other config files of other tossers.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Mar 30 09:37:38 2024
    On Sat, 30 Mar 2024 20:02:32 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    Am I? But indeed it takes effort to get your terminals, locale, and charset settings just right.

    Yes, it does.

    And there are limitations. You can't display utf correctly. And you have to choose a native charset. Any character not supported by the charset, can't be displayed correctly. I can probably not view Russian messages correctly for instance...

    You might be able to view them, if your terminal is still UTF-8. But I think I remember you changing your locale to CP850 now, so sure it's probably doubtful you can view much of any UTF-8.

    You can display utf-8 correctly if you terminals, locale, and charset settings are just right. The only issue I have is the CP437 line/box drawing characters when converted to UTF-8 just wrap early because they are converted to multiple bytes. They do display correctly, though.

    Most of this was already covered in the GOLDED echo, and is probably off topic here. I heard the moderator rules with an iron fist. ;)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Mar 30 09:45:26 2024
    On Sat, 30 Mar 2024 20:08:26 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    Is the original intent just meant to import the descriptions to said areas
    that were already entered manually?

    It says so in the bottom line description for the function:

    "Import descriptions from Backbone.NA into fmail.ar"

    Ok. It is what it is, I guess.

    So your suggestion would be to use two different config files to get your areas imported properly?

    1) Import an AREAS.BBS first
    2) Import the descriptions with backbone.NA?

    But there are also import functions for a number of other config files
    of other tossers.

    I don't happen to be using any of those. So this would be my only option.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 16:04:14 2024
    Hi Nicholas,

    On 2024-03-30 09:37:38, you wrote to me:

    And there are limitations. You can't display utf correctly. And you
    have to choose a native charset. Any character not supported by the
    charset, can't be displayed correctly. I can probably not view
    Russian messages correctly for instance...

    You might be able to view them, if your terminal is still UTF-8. But I think I
    remember you changing your locale to CP850 now, so sure it's probably doubtful
    you can view much of any UTF-8.

    Both: My terminal is utf-8, but I use CP850 as locale to start golded.

    You can display utf-8 correctly if you terminals, locale, and charset settings are just right. The only issue I have is the CP437 line/box drawing characters when converted to UTF-8 just wrap early because
    they are converted to multiple bytes. They do display correctly,
    though.

    I don't think you can have both. And I'm happy with my current setup.
    And I can probably use an external editor/viewer, if I realy needed to see an utf-8 message.

    Most of this was already covered in the GOLDED echo, and is probably
    off topic here. I heard the moderator rules with an iron fist. ;)

    Moderator? What moderator? ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.3.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Mar 30 16:07:31 2024
    Hi Nicholas,

    On 2024-03-30 09:45:26, you wrote to me:

    It says so in the bottom line description for the function:

    "Import descriptions from Backbone.NA into fmail.ar"

    Ok. It is what it is, I guess.

    So your suggestion would be to use two different config files to get your areas imported properly?

    1) Import an AREAS.BBS first
    2) Import the descriptions with backbone.NA?

    Yes, there is no other way.

    The areas.bbs contains much more information anyway, that you want to import, then the .na file. But it doesn't contain the area descriptions.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6.600 to Nicholas Boel on Sun Mar 31 10:11:45 2024
    Hi Nicholas.

    30 Mar 24 16:07, Wilfred van Velzen wrote to you:

    1) Import an AREAS.BBS first
    2) Import the descriptions with backbone.NA?

    Yes, there is no other way.

    I created areas.bbs from husky config and imported it to fmail. Worked fine.

    tommi@ubi386:~$ fconf2areasbbs.pl
    fconf2areasbbs
    --------------
    Usage:
    fconf2areasbbs <FidoConfigFileName> <AreasBbsFileName>
    fconf2areasbbs <AreasBbsFileName>

    Example:
    fconf2areasbbs config.areas areas.bbs

    'Tommi

    --- FMail-lnx64 2.3.1.0
    * Origin: -------------> (2:221/6.600)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sun Mar 31 12:11:26 2024
    Hi Tommi,

    On 2024-03-31 10:11:45, you wrote to Nicholas Boel:

    1) Import an AREAS.BBS first
    2) Import the descriptions with backbone.NA?

    Yes, there is no other way.

    I created areas.bbs from husky config and imported it to fmail. Worked fine.

    Good to know. Thanks for testing!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.1.0
    * Origin: FMail development HQ (2:280/464)