Copyright Ownership of a Translated Article Appearing in a Book in Which an Online Translator was Used As a follow-up to Attributing the Assistance of an Online Translator for a Book&#39;s Chapter---Is It Necessary?, and at the suggestion of @DaleM: QUESTION: Would an author of a book who incorporates an English translation of an article which was first published in the 19th century (and presumably, in the public domain worldwide) by relying heavily on an online translator (such as DeepL Translate free version or Google Translate)---own also---a copyright, specifically, on the translated article which appears in that book?
Probably Not The creator or owner of a piece of software does not in general have any copyright over the output when others run the software, unless that output is itself a derivative work of input supplied by the copyright owner, or forming part of the software. In this case the translation is a derivative work of the 19th century original, but that is assumed to be in the public domain. SAo google has no copyright on the resulting translation. But copyright protection is only available for &quot;original works of authorship&quot;. (See 17 USC 102 in the US, and similar laws elsewhere.) A machine-produced translation is not an original work, and it is surely not then work of the author of the overall book. However, the author would still have a copyright on the book as a whole. The legal situation is no different than if the author had simply quoted a 19th century work. One may incorporate public domain works into a later work, and that later work is still protected by copyright, provided that there is enough original contentr to make the work as a whole &quot;an original work of authorship&quot;. Others may use the PD [arts, or the original from which they are taken, but not the rest of the work (beyond what fair use would allow in any case). For example, I have made a number of posts here on LAW.SE. In several,of those I quoted sections from one of the numbers of The Federalist. That 19th century work is in the public domain. Anyone else may re-quote the passages I quoted from it. But that gives them no rights to use the rest of my work, except as the CC-BY-SA license or fair use permits. So the author would retain copyright on the book as a whole. But soemoen who merely quotes or uses the translated 19th century article but none of the original parts of the book would not be infringing that copyright. I say probably in the header, because I do not have any actual case-law to cite here. It is possible that some court has rules otherwise on the subject of the copyright on the output of a software tool, but I strongly doubt it.
Section 108(a) is the most useful for an infringer who posts an entire copy of a protected work in public. Subsections(b,c) require that the copy not be made available outside the premises, which precludes internet posting; (d) requires a user request to make a copy; (e) applies only to items that are off the market and transferred to a specific user; (h) allows more copying in the last 20 years of the period when a work is protected (not applicable here). Subsection (a) allows a library or archive to make one copy of a work, as long as there is no commercial advantage to making the copy, the library is relatively public (it might restrict access to bona fide researchers), and a copyright notice is included: this has the fewest restrictions on copying. The internet downloader is not a library or an archive, so the downloader is not granted any permission under 108 to make a copy. Under 108(a) a library can make no more than one copy available, but every uploading or downloading is "making a copy". A library would be contributorily liable for the illegal downloadings of their "customers". It is difficult to know exactly what one can get away with under 17 USC 107 a.k.a. "fair use". I am fairly sure that posting a copy of a contemporary book in the open is not "fair use" even if the intent is to make it possible for dummies to study chemistry: such copying is not at all transformative, totally unlimited, and provides a significant market substitute for the protected work.
The Google terms of service do not prohibit using their translate programs to create something that you sell. TOS for using their API would be irrelevant, since that isn't what you're doing. There is no clear copyright issue: as far as I can tell, there is not yet any case law suggesting that the output of a program can be owned by the copyright-holder of the program. (Copyright must be held by a legal person, i.e. an actual person or a corporation, and a program cannot yet be a legal person). A human-performed translation is subject to copyright protection since what is protected is that which is created by the (translating) author, and a program lacks that creative element. A translation owes its existence to the program-user using a particular tool to create the work, be it a pen or a translation program. What is unclear at present is whether a person using machine translation in a permitted fashion to create a derivative work thereby gains copyright to that derived work.
The English translation is a copyrighted work While the original Greek is public domain, the English translation is a new literary work with its own copyright running for 70 years after the author(s) death(s). The French translation of the English work would require the permission of the author(s). A French translation of the original Greek wouldn't. This assumes that the translation was not simply mechanical; like running it through Google translate. A purely mechanical translation lacks the originality required to create a literary work - an English translation obtained algorithmically is a copy; just like a zip file is a copy.
It should not surprise you that copyright protects the right to (among other things) make copies. There are limited exceptions that are considered &quot;fair use&quot;, like if you reproduce a limited amount of text for educational, reporting, or review purposes. Giving your friend a copy of a large portion of the text just because they want it would almost certainly violate copyright. Whether the book is available or out-of-print has absolutely no bearing whatsoever on who holds the copyright or whether your actions violate it. This is very different from giving your friend the book itself. The book itself is covered under the &quot;first sale doctrine&quot;, meaning that by buying a copy of the book, you buy the right to sell, transfer, or dispose of that particular copy, but it doesn't give you the right to make more copies. I will note that in practice, it is vanishingly unlikely that the copyright holder would ever learn of your isolated instance of limited infringement in the first place (especially since it's out of print), much less bring legal action against you for making a single copy that did not affect their bottom line.
&quot;The Holy See owns all copyrights in the works published under its name or created on its commission (art. 5).&quot; Since this painting was commissioned by the Vatican for the Sistine Chapel, they own the copyright to it. The first sentence just says the Vatican owns all copyrights that exist, it doesn't speak to whether any copyrights exist in the first place. Earlier in that article, it says &quot;The law provides for copyright 70 years after the death of the author, or 70 years after publication for works with no named author.&quot; I don't know off-hand when Michelangelo died, but I'm pretty sure that it was more than 70 years ago. So if there is a copyright, it has long since expired, and who owns it is a moot point. The painting is well in the public domain. If there were a valid copyright, a sculpture would be a derivative work and would require a license.
At least in the United States (and I'm pretty sure this is true around the world), facts and information cannot be copyrighted. Just because a work is copyrighted, doesn't mean every part of that work is copyrighted, and factual information conveyed by the work is a part which is not subject to copyright. Copyright on a collection of facts is limited to the selection and arrangement of those facts, and only if that selection and arrangement has some bare minimum amount of originality. See Feist v. Rural, 499 U.S. 340. In this case, it looks at first glance like the person who made that site made their own selection of which materials and which sources would be included; the one place where they really seem to have copied their selection is from glass catalogs with datasheets from specific manufacturers, who would have a hard time arguing that "everything we manufacture in this widely-recognized class of substances" is an original selection. What the author of the website has done is relinquish his rights in his selection and arrangement of the data. In some places, there are other rights besides copyright that do apply to databases; for instance, the EU recognizes database rights to protect significant investment in compiling a database of stuff. But the US does not have that concept. For citing stuff, that's not really a legal question, and has more to do with academic standards. Ask your adviser or teacher if you have one.
You Own The Code To answer your question on whether or not it is copyright infringement: Yes, you do own the rights to the written code but posting it on Github gives Github the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it. To simply put it, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive your Content. So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward. Things aren’t quite as clear-cut in a scenario where Copilot is trained on code that is hosted outside of GitHub. In that situation, the copyright infringement question would hinge largely on the concept of fair use. If Copilot is being trained on code outside of GitHub, we accept that at least some of what they’re looking at is copyrightable work. So, the question then becomes if it’s fair use. Now, you ultimately can’t conclude definitively that something is fair use until you go to court and a judge agrees with your assessment. But I think there’s a strong case to be made that Copilot’s use of code is very transformative, a point which would favor the fair use argument. There is precedent for this sort of situation. Take the case of Google Books, for example. Google scanned millions of books, provided people who were doing research with the ability to search the book, and provided the user a small snippet of the text that the user was searching for in the book itself. The court did in fact find that was fair use. The use was very transformative. It allowed people to search millions of books. It didn’t substitute for the book itself. It didn’t really take away anything from the copyright holders; in fact, it made it easier for readers to access the work and actually opened a broader market for book authors. And, it was a huge value add on top of the copyrighted corpus. In the latter scenario, a lot depends on the thoroughness and the length of Copilot’s suggestions. The more complex and lengthy the suggestion, the more likely it has some sort of copyrightable expression. If a suggestion is short enough, the fact that it repeats something in someone else’s code may not make it copyrightable expression. There’s also the question of whether what’s being produced is actually a copy of what’s in the corpus. That’s a little unclear right now. GitHub reports that Copilot is mostly producing brand-new material, only regurgitating copies of learned code 0.1% of the time. But, we have seen certain examples online of the suggestions and those suggestions include fairly large amounts of code and code that clearly is being copied because it even includes comments from the original source code.