----------------------------------------------------------------------------------
@MSGID:
<577f6d17-245b-4e4c-a56a-3f062366a690n@googlegroups.com> c7404435
@REPLY: 1@dont-email.me> 5675893b
@REPLYADDR fadden <thefadden@gmail.com>
@REPLYTO 2:5075/128 fadden
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<b1851b43-77c6-4887-8690-c2f891d4cbc1n@googlegroups.com> <09603b77-1953-4742-b400-268c6e457e9cn@googlegroups.com>
1@dont-email.me>
@RFC-Message-ID:
<577f6d17-245b-4e4c-a56a-3f062366a690n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Monday, September 25, 2023 at 9:08:28 PM UTC-7, Brian Patrie wrote:
> Out of curiosity, why aren`t you simply calling it CiderPress 5?
Because it`s a rewrite from scratch, rather than an improved
version, and there are differences in how they can be used. CiderPress is a
Windows MFC app that can run in WINE on other systems, CiderPress II is a
.NET app that (for now) has a Windows GUI and a broadly executable
command-line interface. Explaining how to use them to somebody else is easier if
the recipient doesn`t need to know that everything changed in v5.
Besides, ciderpress2.com was available. :-)
The debate that I expect will engage scholars for generations is
"CiderPress II" vs. "CiderPress 2" vs. "CiderPress ][".
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441