“ The translator's rights are not a factor in this discussion, though I recognize that even an unauthorized translation can in some countries give rise to its own copyrights. If we are to be consistent in the view that copyright is a property right, then we recognize the right of the owner of such rights to dispose of them as he will. There may very well be modern day requirements that would serve as evidence of an intention to put work into the public domain, but requiring those affected to rise from the grave to fulfill bureaucratic requirements does not seem realistic. ”
Summary
“Scriptorium/Archives/2008-04”, is a work by . It explores elements such as Wikisource, bot and copyright.
Quotes from Scriptorium/Archives/2008-04 ()
“ The community should review the bot policy over the mandatory restriction of the inclusion of "bot" in bot usernames. The community should do so not to simply satisfy me but because that such a discussion and change may benefit the community. The real question is does the mandatory "bot" in bot usernames really benefit wikisource? Would a lack of "bot" in bot usernames harm the project? Should it be a recommendation rather than requirement? Mind you, a bot operator may still choose to name their bot username to contain a "bot" even if manditory "bot" in bot username thing is loosened. ”
“ In common-law countries there is a greater tendency to interpret copyright law as a balancing of rights between the rights owner and the general public. Following the strict blind letter of the law in all cases is bound to be a losing strategy. Although, I believe that there are still strong legal arguments that could be raised to defeat the idea of non-acceptance, (e.g. A US law giving a greater protection to foreign nationals than to its own citizens could be seen as contrary to public policy.) ”
“ I'm always happy to blame Microsoft for what's wrong with software, but what ball did they drop here? Template based solutions need to be kept to a minimum if you want to maintain the involvement of the less geeky among us. Keeping things looking as much like the original could just as easily be used to argue for maintaining the original text justification and hyphenation. Is all that additional complexity really worth the effort? ”
“ Administrators are also likely to treat a rapidly-editing bot differently from a user. Most bots on Wikisource run without a bot flag, and there is no other standard way to distinguish them from normal editors. Using a naming standard is the simplest and most effective way to do so, and distinguishes them in all contexts (links, recent changes feeds, edit histories, user pages, et cetera) . Other possible standards (such as a user page template or standard edit summary) are more difficult to implement and have more limited applicability. ”
“ It seems that people are going to do whatever they think best for each project. Some will maintain linebreaks, while some will fix spelling — most will do something in between. Is that a fair thing to say? I prefer using the unicode characters in the text, and not templates, just because it's so much easier to write (and read whilst editing) . But I take back what I said before about trusting the Unicode Consortium to determine what characters we can and cannot use — I am currently transcribing Terræ-filius, and I want the st (that's a long s joined to the top of the t) ligature! ”
“ You point out that Google searches work irrespective of the ligatures on the page; I pointed out that internal search work on the actual text. We already have the best of both worlds. If we need better search engines, then eventually someone will build them. Yes, we did have this discussion, but I am now noting my objection to these templates here as part of the general discussion. If Wikisource is to ever introduce display ligatures as anything except for the actual intended character, I would expect that it would be done in the software itself rather than using templates. ”
“ Where texts or images are tagged as being in the public domain, the text and images are unable to be copyrighted. Attempts to claim copyright on works in the public domain are called Copyfraud. It is possible that a Wikisource contributor could claim that their presentation of a PD text is creative, but if this was ever to occur, I think the appropriate response from the Wikisource project would be to remove the creative presentation and replace it with the presentation in the original so that is nothing more than the sweat of the brow. ”
“ The bot does not have "bot" in its name; that makes it impossible for someone reviewing the history of an article to know that a particular action was taken by a bot. I would even question the validity of "Computer" as a user name, because in generic nature could cause confusion. The proposed bot purports to combine the work of three existing bots; what would be the problem with running each of these separately? The delinker is also a problem, because the image inclusion policy here allows for some images that might not be allowable in Commons. ”
“ If a work is considered copyrighted in the U.S. (and is not available under a free license) , then we can not use the work on the English Wikisource (or any other Wikimedia project) , even if it is considered PD in its country of origin. (This is per Mike Godwin's comments — Mike Godwin is the legal council for the Wikimedia Foundation.) U.S. copyright law may be complex, counter-intuitive, or even absurd, but the Wikimedia Foundation is still bound to adhere to it. General cases for the public domain If a work contains no "creative content", then it is not eligible for copyright. ”
“ A vandal may choose to vandalize using a fake bot account. Marking known good bots with a bot flag has lots of benefits and no real harm. Not everybody needs to review every bot edit which almost always are non-problematic. This request isn't just about my bot. It has a general rationale. It would be trivially easy for me to alter my bots username (user-config.py) rather than making a single post about it. ”
“ In response to my first comments in this thread you did not show how to search for "ship" in the Periplus text so as that it will reveal both uses of the long "s" and the capital "S". If people want the æsthetic feel of the historical original, they are just as well off with a pdf file. There is no need for pedantic tinkering with the typography. For me the important thing about Wikisource is the presentation of information and old texts that are not easily available to most people. There is no shortage of such material. ”
“ In general, I don't think we should overregulate style standards that pertain to layout only. If someone wants to implement a tightly crafted layout, why not, but please don't make it mandatory. As for the prose class, I typically use it as something to start from (it certainly makes the text more readable than using nothing at all) and alter it wherever such alterations are easy. ”
“ Featuring an image does not need to complete with our featured texts. They would only need to be good quality images of PD texts, with a blurb to explain them. The text would not need to be transcribed for the image to be appreciated. In this way we can encourage Commons contributors to notify us of good page scans which dont have much chance of being a Commons featured image. For a featured image to get off the ground, Darkfalls would need to be willing and able to commit to keeping it moving for a month or two. ”
“ In no way are commons admins required or expected to upload images locally. If a commons user is doing such a thing perhaps you should be thanking him or her for the hard work. Please do not ask me or anyone such a thing. Be reasonable. Commons admins juggle over two million images. With thousands of new images a day this is a very demanding and tiring task. You are welcome to run CommonsTicker, a bot that posts relevant commons activity. If you are really concerned, you are more than welcome to help out on commons processing every image used on Wikisource. ”
“ Javanese books Javanese literary history spans more than 1200 years. There are literally thousands of works in Javanese. So I plan to put them on the internet by setting up a Javanese wikisource. However nowadays before commencing a new project, one should place this first on a multilingual wikisource. So my question is: is it better to place this material here or for exemple at another wikisource edition, for exemple the Indonesian Wikisource? ”
“ Grammaticus 05:00, 23 February 2008 (UTC) Newbie opinion here (lots of experience with text, but new to Wikisource) : A good principle to apply is to avoid throwing away information, except with good reason. I assume that the purpose of transcription is to go from image to "text", which is partly objective concept, so throwing away purely geometric information has a good reason, but we should avoid throwing away textual information. If you preserve the distinction between long/short "s", it's easy for a display to automatically conflate them. ”
“ Double redirects are a navigational hazard to the reader and is a mindless task to fix these. Say if pages of wikisource material were to be moved all redirects leading to them would now point to a redirect. All those god knows how many redirects would need to be updated so they point at the new location of the moved page. This requires no human intervention. It is a task bots can handle this way humans can focus on other tasks. As of this post Special:DoubleRedirects registered 42 double redirects for en.wikisorce. If this isn't fixed, the number will grow. ”
“ Any legal works of any government are not copyrightable in the US. This means that UK court rulings are public domain in the United States. See WS:PD#Category:Acts_of_the_Scottish_Parliament. Someone wishing to claim copyright are going to have to register for copyright in the United States, and the Copyright Office have said they will not approve requests of that nature, in no uncertain terms, so someone will need to win in the Supreme Court before they can claim copyright in the United States. ”
“ Email on page changes On Wikimedia Commons, the system emails users when pages are modified. As most users dont come back to Wikisource and regularly check their watchlist, I propose that this feature is also enabled on Wikisource. It will spread the anti-vandalism load as many people will be instantly notified of a vandal on a spree, initial contributors will usually take responsibility for verifying any fixes, and it will also allow "initial translators" to sanity check any subsequent improvements which may encourage translators like Terry0051 to entrust their work to our keeping. ”
“ Scripts Are there any editing scripts available on Wikisource other than those listed at WS:SCRIPTS? I'm looking for one that can automatically "pipe links" for Authors and Wikipedia articles. On the English Wikipedia, w:User:MarkS made an "extra edit buttons" script which automatically creates the brackets and | for categories and images, so creating a piped link edit button seems doable, and would certainly save time when editing. ”
“ An example semi-automated run is here. Currently the algorithm accepts contributors creating pages which match a particular pattern. e.g. new pages by Bochica (talk • contribs) under Journal of Discourses are A.OK. I'm curious if anyone has any reservations about this, as I would prefer to run this automated on the bot account rather than manually on my account. In order to be useful, it needs to be run regularly. If it helps, this list of automatically patrolled user/page tuples could be stored on a wiki page to allow it to be updated by any admin. ”
“ What parts of an orators presentation should be emphasized or omitted is not a decision Wikisource editors should be making. It is not possible for us to be evaluating works for neutrality and accuracy in abridgement objectively. ”
“ Move Max Havelaar to the page Max Havelaar (Siebenhaar) and then turn Max Havelaar into a disambiguation page, change the link on Siebenhaar's page to Max Havelaar (Siebenhaar) .—Zhaladshar (Talk) 15:15, 13 February 2008 (UTC) I agree. There seems to be an implicit assumption in Hesperian's question that a Wikisource translation is necessarily inferior to one that has already been published, and that it only exists to plug a hole while we are waiting for a published one that we can use. Wiki translations should be more generally encouraged, as should annotations. ”
“ Remember too that any legal action must be taken by the owners themselves; governments do not start civil actions to enforce private rights. In summary laws that create absurdities can and should to that extent be ignored. ”
“ Create a subpage at Strivings of the Negro People/annotated. The text of the page should simply be {{:Strivings of the Negro People}}. That's it! Now your non-annotated version will not show the comments, but will link to the annotated version, which does. (The annotated version will link back to the non-annotated version as well.) Compare Strivings of the Negro People and Strivings of the Negro People/annotated to see a real-live example. ”
“ A excerpt is an incomplete work. If one contributor only wants to contribute 25% of a work, I would welcome that, as others will do the other 75%. The works in question here are either not covered by copyright, and/or the author Chomsky is likely to approve their release into the public domain. He is more likely to release them if he can see them, so it is worth putting aside our copyright concerns until Iddo999 has presented them in format ready for Chomsky to review. ”
“ The risk is that low, much lower than the peril to our lives when we don't wear seatbelts, or we cross the street in the middle of the block through heavy traffic, or we eat junk foods. The risk to WMF is non-existent as long as it complies forthwith with any legal takedown orders. The more of us have the courage to accept the risks involved as personal risks, the sooner the whole issue can be put behind us. ”
“ Things that come to mind... Policy unification (except the copyright/licence policy, of course) . To the very least, everything that would allowed on Wikisource, were it not for copyright, should be allowed on Wikilivres. Policy unification makes it easier for editors to adhere to community standards. That's already the case: everything which is allowed on WS is also allowed on WL, but not the opposite. There are a few works without prior paper publication, and a lot of translations under *-NC. Yann 18:20, 28 February 2008 (UTC) That's not completely correct. ”
“ We are not interested in recent pictures that really have current marketability, or works authored by individuals who are still very much alive. We interpret, and should continue to interpret laws in a way that considers the interests of all concerned. We don't thumb are noses at the owners, daring them to come and sue us. ”
“ If the copyrights were not mentioned in the wills it's quite likely the rights are shared by all the great-grandchildren, any one of whom can grant a free licence without regard to the wishes of his second cousins. ”
“ I don't think that giving either version primacy is important, and I would be delighted if someone with access to the issue of the Saturday Review that first published the poem could be found and that version compared compared. We also need to be judicious in our selection of which versions of a multiply published text we are to include. Adding a separate, school edition of Macbeth just to show that the porter's speech was omitted would indeed be wasteful. Project Gutenberg's failure to acknowledge specific editions of a work has made our work harder. ”
“ With sister project prefixes, it's easy to create the backlinks. Maintaining them sounds like bot work (removing prefixes once a work has been moved, updating links pointing to soft redirects across sites, etc.) . The one thing a bot cannot do is to automatically fix genuine link-rot. But on a project such as Wikisource, I'd expect very few link-rot.--GrafZahl (talk) 10:21, 29 February 2008 (UTC) User education/vocabulary check. Wikisource speaks of "free content", Wikilivres of "free licences". An unwitting user might believe that's the same thing. ”
“ Patrollers should pay attention to human edits for vandalism and etc. If a bot breaks it is the responsibility of the bot operator not of patrollers. While bots like CommonsDelinker may need its edits reviewed, doing so through the entire RC feed may make such a task very difficult. Special:Contributions link of the bot account is probably a better way to check a bots activity than Special:Recentchanges. Please think this in terms of how wikisource will be in 5 years from now. Consider how many edits wikipedia gets. Wikisource may be no different in the near future. ”
“ While there are a number of benefits for Wikisource's naming standard, you have not explained how this in any way inconveniences you. You can set the name on Wikisource without changing it elsewhere simply by editing one line in the bot configuration, and you can redirect user:Computer so that you can link to it from your bot account lists without change. —{admin} Pathoschild 20:07:40, 19 March 2008 (UTC) Human usernames can contain the 'bot' string. Some real person names have "bot" string in them. ”
“ The reason why each image is investigated on Wikisource is that we only permit PD images, so images used on Wikisource are predominately PD, and if an image is removed from Commons, there is a high chance that something has gone wrong. John Vandenberg (chat) 08:15, 18 March 2008 (UTC) Never the less there is no reason not to fix them in an automated manner Interwikilinking is a process where interwiki linked pages are synched. "Same name" is not a criteria at all as far as the mindless bot is concerned. A trial process is fine. The bot would only operate if CommonsDelinker fails to operate. ”
Common terms
Similar works
Billinghurst/2010Scriptorium/Archives/2008-08 (Adam Smith…Scriptorium/Archives/2007-04 (|author_override…Billinghurst/2009Scriptorium/Archives/2006-07 (A. P. Sinnett…Cygnis insignis/Archive 2The Fables of Florian (Jean Pierre Claris de Florian…Scriptorium/Archives/2016-08Billinghurst/2012Scriptorium/Archives/2010-04 (Herbert Spencer…
