[Oberon] Updating Project Oberon PDF Docs (was: ALU 2015 and 2018)

[Nemo Nusquam]

Greetings, Guido.

On 2022-05-20 12:56, Guido Bartolucci wrote:
> I've been intending on making a TeX translation of the Project Oberon 
> PDFs for a while. I haven't prioritized it since it's just for my own 
> personal project but if others are interested in it I can make 
> finishing it more of a priority.

A LaTeX version would be welcome, thank you.  (That way, I can increase 
the font size very easily.)

N.

>
> As for the copyright. I am not a lawyer, but it says the following, 
> which looks a lot like a BSD or MIT style license. But I'd love a 
> lawyer to confirm for us.
>
> Project Oberon, Revised Edition 2013
>
> Book copyright (C)2013 Niklaus Wirth and Juerg Gutknecht;
> software copyright (C)2013 Niklaus Wirth (NW), Juerg Gutknecht (JG), Paul
> Reed (PR/PDR).
>
> Permission to use, copy, modify, and/or distribute this software and its
> accompanying documentation (the "Software") for any purpose with or
> without fee is hereby granted, provided that the above copyright notice
> and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHORS DISCLAIM ALL WARRANTIES
> WITH REGARD TO THE SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY, FITNESS AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
> AUTHORS BE LIABLE FOR ANY CLAIM, SPECIAL, DIRECT, INDIRECT, OR
> CONSEQUENTIAL DAMAGES OR ANY DAMAGES OR LIABILITY WHATSOEVER, WHETHER IN
> AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
> CONNECTION WITH THE DEALINGS IN OR USE OR PERFORMANCE OF THE SOFTWARE.
>
> On Thu, May 19, 2022 at 12:19 AM Skulski, Wojciech 
> <skulski at pas.rochester.edu <mailto:skulski at pas.rochester.edu>> wrote:
>
>     Chris:
>
>     > We combined all three PDF files into one for convenience
>     > when we sent it out to get a printed copy, and added the bookmarks
>     > to make it easier to navigate. AFAIR, we didn't make any changes
>     to the text.
>
>     This is great. Thank you for the hint. How about the copyright? I
>     mean, imagine we modify portions of the original project and we
>     want to update the document. It makes sense to start from the
>     original because it was a significant piece of work. It will make
>     sense to keep part of the document intact for those parts which
>     were not changed (yet).  After a while it will become a patchwork
>     of the original and the modified text. How is this going to work?
>     I will not feel comfortable modifying the text as I see fit, while
>     an unmodified text will become disconnected with the actual project.
>
>     Wojtek
>     --
>     Oberon at lists.inf.ethz.ch <mailto:Oberon at lists.inf.ethz.ch> mailing
>     list for ETH Oberon and related systems
>     https://lists.inf.ethz.ch/mailman/listinfo/oberon
>     <https://lists.inf.ethz.ch/mailman/listinfo/oberon>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon