[Oberon] Text vs. txt; was Re (2): Links for the Oberon-2 report.

[Charles Perkins]

Not only conceivable but exactly how I do it! All the source I compile is
plain ascii with newlines instead of carriage returns. The compiler doesn't
care about newlines vs. carriage returns either, which is nice.

Chuck

On Wed, Jul 29, 2020 at 8:20 AM <peter at easthope.ca> wrote:

> Hello Liam,
>
> From:   Liam Proven <lproven at gmail.com>
> Date:   Wed, 29 Jul 2020 16:32:38 +0200
> > I fully understand that this is not true in Oberon but I absolutely do
> > think that it is fair, reasonable and understandable to see a file
> > called "README.Text" and expect it to contain plain text!
>
> Considering this, Text is discussed on the front page of the Wikibook.
> https://en.wikibooks.org/wiki/Oberon#Oberon_Text
> A novice might catch that before abandoning Oberon.  Suggestions
> to improve the section are welcome.
>
> The compilers ignore niceties of typography.  Building an Oberon
> system without changing the compiler and with strictly ASCII txt files
> is conceivable.  An ETH Oberon derivative might attract significant
> attention.  ...        =8~)
>
> Regards,                             ... Lyall E.
>
>
> --
> https://en.wikibooks.org/wiki/Medical_Machines
> https://en.wikibooks.org/wiki/Oberon
> Tel: +1 604 670 0140            Bcc: peter at easthope. ca
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20200729/b4c97acd/attachment-0001.html>