Subj : Re: Problem with filenames containing spaces
To : deon
From : James Coyle
Date : Tue Jan 18 2022 10:37 pm
de> is not), but that is moot - if your software doesnt work with it, I dont
de> get why you wouldnt want to make it work with it, even if the binkd
de> development team werent interested in "fixing" it the way you want it
de> "fixed".
My software works fine with it, there is nothing I could possibly change. It handles all formats of escaping and its configurable per node. The person in this case is using a version many years old with a bug, but you knew that.
You know it because I have explained this to you now in three different messages, and you keep ignoring it. I don't want anything fixed. I never posted here asking for anything, someone else did. I could care less if BINKD adds it or not but given its a FTS guideline I think it should. I keep telling you that but again, you just ignore it.
You should ask yourself the same question you just asked me: If implementing the *FTS recommendations for handling filename escaping* into BINKD would make it work better with more mailers, then why not do it? Wouldn't you want to make it better? BINKD will fail with any legacy mailer that uses the \XX format and those legacy mailers cannot be updated only BINKD can.
To answer your "would you want to fix it" question. When this issue was brought to me back in 2020 I made changes within an hour of reporting it, and the person who did so didn't have to push through all this drama and resistance for no reason. So yes, as my reputation fully has proven over more than two decades, I respond very quickly and fix issues often times in the same day its reported. You can go back 20 years and see this very thing happen over and over again.
Its really weird how you guys go on and on about FTS compliance and then you ignore whats going on and cherry pick what should and shouldn't be applied when it aligns with whatever narrative you're trying to push.
