Kari,
Sorry about not getting back to you on your post sooner. (Now that the thundering herds of family and grandchildren have departed, I have the time to do so.)
The idea of turning XyWrite into a public domain project has both good and bad sides.
One difficulty is that unless we want to write a clone from scratch, getting a licensed copy of the proprietary code to port over to a modern OS platform could be difficult. That is, unless the proprietary owner would make it into a donation, or a group of benefactors were to provide the money to buy it. Another problem is the number of man-hours needed to port the old code onto a modern platform so public domain ‘volunteers’ could continue to perfect it, maintain it and keep it current.
On the positive side, XyWrite is a classic editing and scripting tool, not unlike LaTeX, which could intrigue new and old programmers enough to give it a following. (There is a lot more to say on this aspect, but is OT here…)
Personally, I do have a few connections that could be a source of manpower to get this off the ground, especially in the public domain, but I’d need to make inquiries and see if I could stir up interest. (Namely in enlisting grad students from the University I retired from. I also know some of the higher-ups who could put in a good word, many of these having a reverence for older platforms, like LaTeX.)
There are a few posts in this thread offering a wish list. However, to play the game, first you need a ‘ball.’
Phil
Sent from Mail for Windows 10
From: xywrite-bounce@xxxxxxxxon behalf of Kari Eveli
Sent: Wednesday, April 11, 2018 9:59:37 AM
To: xywrite@xxxxxxxx
Subject: Re: A radical idea: a new XyWritePhil,
If the source code can be obtained somehow, it should be turned into an
open-source project. That way it would gain much more developer interest
and perhaps even sponsors.
Reviving the Atex heritage is also something to consider: after all, the
publishing industry might be interested in an open-source typesetting
alternative. Why XyWrite developers did not keep the typesetting focus
beats me. The mainframe ancestor of XyWrite is alive and still doing
business:
Down memory lane: PC Mag on Atex and XyWrite (1984):
The XyWrite text format which I have put into good use in
lexicographical text databases is not the best for modern applications.
I am converting it to XML-type format myself. No doubt, it is an editing
convenience in its simplest form (Xy3). An XML-based format is what is
required today. The current NB lacks it, and is scorned by users that
opt for programs like Oxygen XML Editor ().
But if we drop the Xy format, what is left of XyWrite?
As to typography, there are plenty of capable free alternatives.
Scribus () for general typography.
TeX packages offer a lot for technical writers:
or Lyx for math:
Universities are using these and their commercial brethren like
ShareLaTeX ().
What would have we to offer that is better or even close to what there
is already there for free? I must say that my initial 'vaste programme'
comment is by no means exaggerated. A paid application is out of the
question. An open-source hobby project for a few aficionados may be
doable if the source code becomes available.
Best regards,
Kari Eveli
LEXITEC Book Publishing (Finland)
lexitec@xxxxxxxx
*** Lexitec Online ***
Lexitec in English:
Home page in Finnish:
> One of the many powerful assets of Atex/XyWrite was that it was capable
> of being /programmed/. A new implementation should have hooks for
> running/using scripts written in modern program and scripting languages.
>
> Conjectures can be infinite and still gets nothing done.
>
> Perhaps it would be a good idea for the various participants to throw
> out a few ideas of what they would like to see in a new embodiment of
> XyWrite. We could discuss, see the potentials and perhaps come up with
> something that would make it useful for all of its traditional uses and
> find some that would make it even more relevant for today.
>
> The distribution method and form are important, too. Depending on the
> source we use, and the cost, we could consider making this available as
> a modestly priced utility, or ‘app,’ making it available on line or even
> as a public domain project that could become self-perpetuating.
>