Wikisource talk:Translations

Latest comment: 8 years ago by Billinghurst in topic A couple of notes for deliberation

Links between translations hosted at oldwikisource:? edit

Is there a way to put a sidebar link to/from a translation hosted at oldwikisource:? Simply using [[oldwikisource:XXXXX]] doesn't work :(.--Imz 16:39, 9 November 2005 (UTC)Reply

As of right now, no. There was a discussion a little while back on the multi WS where it was considered, but I don't think anything ever became of that. We could try to resurrect that discussion, and if we get a consensus, we could propose a bug.—Zhaladshar (Talk) 17:14, 9 November 2005 (UTC)Reply

Updated translations edit

Discussion moved here from Wikisource:Scriptorium.

An anonymous user on Wikisource talk:Help, brought up a question about updating translations of works. Now, Wikisource wants to preserve the integrity of the works (which would include preserving typos and such), but would this policy extend to translations, since they aren't the original to begin with? Personally, I don't have a problem with updating a translation, unless it was of such historic import that we should leave it exactly as it was. But for most run-of-the-mill ones, would it be a better idea to correct a horrible translation, so that people will actually use this site to read works? Of course, any corrections would have to be released under the GFDL or put straight in the public domain, but that's another matter.—Zhaladshar (Talk) 21:12, 14 December 2005 (UTC)Reply

Personally I'd prefer not to add horrible translations, if a translation is to be added it should be a good one. However if a bad translation is added I think as it would be listed as "translation of X by Y" we couldn't really correct it/improve it because then it would be "translation of X by Y & a lot of wikisource editors", it'd no longer be the original translation.
I can see the argument for doing proper corrections/retranslations of poorly translated works but I'm not sure if that would be going beyong what wikisource was intended to do - creating in part a wiki translator (or at least corrector of poor translations). That said I'm not sure how many bad translations we have on wikisource or how much of a problem we're dealing with. I think though I would prefer to leave translations as they are until they can be superceded by better translations. AllanHainey 12:57, 15 December 2005 (UTC)Reply

I think offering updated versions of old translations is one of the main ways we could add value to texts. However, a translation should only be listed as an update of an old one if an unchanged parallel in the old version remains on Wikisource. There could be a template with a link to the old translation saying something like:

"The following translation of "text x" is a wiki revision/update of the translation by x."

Allan - while all of us would prefer not to have horrible translations added, remember that that is how Wikipedia works: Often terrible articles are improved by the community into excellent articles. We are, after all, a wiki, so we should be putting the power of the wiki behind the library we build at Wikisource, and creating wiki translations is one important aspect of this. It would probably also be good to have a template saying:

"This is an original wiki translation of "text x", created through community effort."

On the other hand, I completely agree that a wiki translation should not be started in normal cases if it cannot be justified, since a perfectly good free translation of the text is already on wikisource. If someone starts a new translation they should explain why, and if there is no good reason it can be deleted like any other inappropriate text. Dovi 14:33, 15 December 2005 (UTC)Reply

I believe there should be clear distinction between translations that were previously published (in this case we must be faithful to it, and if possible mention the name of the translator, edition, etc) and translations made on the wiki. we can host both, but we should not mix them. In the case of a translation made on the wiki, I think it is important to mention that the translation was produced by wikisource, rather than by some particular user. I do not like the idea of some user adding "translation by user:myself" to the page, because it sounds like other users are not supposed to improve the translation, for it would contradict this assertion. OTOH, if we mention that the translation is "by wikisource", then people will feel they are allowed to help. ThomasV 15:10, 15 December 2005 (UTC)Reply
Good ideas. Yes, we should keep the original translation, of course. And create a template that indicates that it is a wiki translation of a previously translated text. That way we can preserve the original, but offer an alternative if the original is too hard to read. Of course, I think this would only be beneficial if the original is a difficult read. Otherwise, it seems like it'd just be a phenomenal waste of time.—Zhaladshar (Talk) 15:42, 15 December 2005 (UTC)Reply
It might be a waste of time if a translation already exists. however, some texts are not translated, and the wiki is an interesting tool for that. I spent an incredible amount of hours translating Free Culture] to French. Given the time it takes, I believe translations on the wiki will always remain a minor source of texts for wikisource. ThomasV 16:04, 15 December 2005 (UTC)Reply
I completely agree, but if a user wants to spend the time doing it (heaven knows I don't--and I still wouldn't even if I did speak another language fluently), I think they should be allowed to "upgrade" a translation (following what was specified above), unless a better translation can be found to save the time altogether.—Zhaladshar (Talk) 20:04, 15 December 2005 (UTC)Reply
I also believe we should encourge anyone who wants to work on translations while still keeping any existing tranlations intact. Perhaps it could be done as a sub-page. Since we are only open to older translations because of copyright this would be very valuble. A great many of the older English translations tend to be a bit biased in the same way as the 1911 Encyclopedia. I don't think we should worry about the quality. We can always flag such article as "poor quality needing expert help" and advertise amoung qualified people on Wikipedia. The one thing we would have to keep a close eye on is POV issues.--BirgitteSB 21:09, 15 December 2005 (UTC)Reply

I've always thought this is one of the places we could really add value. However, I believe we ought to do this in a different namespace to clearly indicate that the translation is not archival of pre-existing material, but original to wikisource. In that case, I wouldn't worry too much about poor translations, any more than I worry about poor wikipedia articles. Eventually, they'll turn out alright. But best to make completely clear that they are works in progress with a namespace.

Some material here is already translated by our users, for example, the farewell speech by Salvador Allende. We couldn't post anything else for fear of copyright. There are probably many such cases. I posted 3 such in Copyvio this week, although one of those has now been cleared. Wolf man 20:26, 20 December 2005 (UTC)Reply

Check out Wikisource:Language policy. As there seems to be a very open policy toward tranlations written there. Could we possibly change that page name to Wikisource:Translations as that is all it is about.--BirgitteSB 20:45, 20 December 2005 (UTC)Reply

Yes, let's do that, plus let the Main Page link to it. Do others agree that we can replace the current list on Wikisource:Translations with this? They could be simply be added to Wikisource:Multilingual editions. Dovi 21:27, 20 December 2005 (UTC)Reply
Hm, that's a good idea. What namespace are you proposing, Wolfman? And will all user-contributed translations be in that namespace forever? (Either way, I don't mind; I'm just trying to get a feel for this.) I do, though, think we should indicate which translations are ours and which have been previously published.—Zhaladshar (Talk) 14:46, 21 December 2005 (UTC)Reply

I'm also trying to "get a feel" for where they should go, but I think we all agree they have to be properly indicated. It seems to me a very simple way to do this would be to entitle translations like this:

Plus we would also use templates, as above. Plus revised translations would link to original, as above.Dovi 15:20, 21 December 2005 (UTC)Reply

Are you suggesting we do this for all translations? Including classics like The Three Musketeers and The Little Mermaid. That will involve alot of name-changing--BirgitteSB 15:42, 21 December 2005 (UTC)Reply
I agree that we should avoid hard and fast rules, and to use suggestions only when they are appropriate. In cases like your examples, for instance, perhaps a classic text with an accepted, "standard" translation, should just be known by a plain title (although other translations of the same text would need something in their titles to distinguish them). Certainly, texts that are already here with reasonable titles are not a big priority to change.Dovi 20:39, 21 December 2005 (UTC)Reply

Looking at this afresh, it simply doesn't make sense, and the wording that we have in place is confusing. If we are talking about Wikisource-generated translations then we should look to move this to that section, and if necessary make it subsidiary. Further, why would we want multiple variations of a set of text. Reproduce the whole work due to a line change by someone? I would think that we would be requiring updates to be noted on the talk page, and move on. A translation=Wikisource will just have to bear with it, no one translator is more refined than another in that space, and we live with the document as it is, ESPECIALLY if we are getting these text modified in the PAGE ns. — billinghurst sDrewth 15:45, 28 January 2013 (UTC)Reply

Devil's Advocate edit

I am a bit bothered on how this might conflict with our policy about WS not hosting original writings by an editor. We are saying here we will accept a competely new piece of translation which has not been published elsewhere. But a piece of unpublished prose by an editor will be banned. At the same time we expect editors to contribute original work by way of commetary to documents. As an example, in my bottom drawer I have an unpublished study of contributors to Abraham Rees's Cyclopaedia (1802-1819) This is based on a list published in Philosophical Magazine in 1820, but to which I have added brief notes from sources like the DNB. Were I to place this on WS, would it banned as not being Peer-Reviewed and published in an academic journal somewhere first? As it stands the document is admirably suited to Wikification with links to WP. I would hate to see WS getting bogged down in the kind of nit-picking there is on WP about Original research. And worse editors migtrating here trying to impose that WP standard. Apwoolrich 18:53, 16 January 2006 (UTC)Reply

A collaborative translation is quite different from a collaborative original work in my eyes. I strongly feel we need to accept translations as we are severely limited by translations prior to 1923 with the muli-lingual contacts of this project. Perhaps we should require a link to the work in its original language for all Wikisource translations. If it is not in the native language the translator should create and as long as it is accepted there we will accept the translatin. But I do understand your point as we have bad machine translations like William Shakespeare.--BirgitteSB 21:50, 16 January 2006 (UTC)Reply
I agree with Birgitte. Original contributions and original translations are quite different. Original translations are still working with a previously published, authoritative text, while original contributions are creating something right out of the blue. I really think this rule is quite a lax one (there are few requirements that must be met: simply, take a source text to translate and add the proper title format to it). Much of WP doesn't apply to us, so I doubt WS will get bogged down with the same junk that's bogging WP down. (And I'm sure we'll be able to keep WP-migrated editors from imposing that standard here, as well.) From what your list sounds like, it sounds like it would be an appropriate material here at WS, so feel free to add it.—Zhaladshar (Talk) 19:22, 17 January 2006 (UTC)Reply

It seems to me that there is a rather easy solution to this problem, at least in normal cases. If Apwoolrich or any user has quality material reflecting their own personal expertise, and they would like to make it available to the public within the context of Wikisource, then all they need to do is post it within their user namespace!

Furthermore, while I agree with the dissatisfaction with nit-picking about original contributions, the specific text that Apwoolrich describes here is an excellent example of annotation: The exact original list could be published at Wikisource, linked to a complementary version with Apwoolrich's notes.Dovi 20:22, 28 January 2006 (UTC)Reply


In lieu of any better place... edit

The following works should be able to be easily given a PD translation by a member of Wikisource familiar with the language.

Template? edit

Is there, in fact, a standard template to identify Wikisource-generated translations? -- Visviva 14:40, 19 May 2007 (UTC)Reply

Translator information should be noted in the {{header}} notes; licensing should be noted with {{translation license}}. —{admin} Pathoschild 17:27:03, 19 May 2007 (UTC)

Suggest Translation namespace edit

Because ideally we really should be having multiple translations of every non-English text, I think it might be appropriate to establish a "Translation:" namespace, by analogy to the "Author:" namespace. This would provide a catalog of all the PD English translations of a text, without privileging one above the others.--Pharos 12:41, 12 June 2007 (UTC)Reply

I am not sure how that would be effectively any different than disambiguation pages in the Main namespace.--BirgitteSB 20:47, 15 June 2007 (UTC)Reply
Well, disambiguation pages are really for different works that only have the same name by chance. A translation namespace would be something considerably more developed. Major works of world literature will have multiple public domain English translations, and these exist in varying states of completeness, abridgment, and even serious modification by old translators (which might indeed be published under completely different names, belying the disambig analogy), that should be carefully annotated in a specific style befitting of a different namespace. I feel that these translations should be fully attributed to one foreign-language work as the source, in the same way that ordinary writings are attributed to their author pages.--Pharos 08:15, 19 June 2007 (UTC)Reply
A disambiguation page is for any works that could be ambiguous, they do not need to have the exact same name, and many of them are simply different editions. Each translation disambiguated by date is easily attributed to the correct foreign work through notes in the header as well as with interwiki links when the other language subdomain has the work. Translation are texts like any other we host and should be in the main namespace. None of the alternate namespaces (Author:, Portal:, Wikisource:, etc) contain texts.--BirgitteSB 13:29, 19 June 2007 (UTC)Reply
Reading this again I don't think I am understanding you 100%. Maybe you could make a mock-up in you userspace of what you want these pages to be.--BirgitteSB 14:58, 19 June 2007 (UTC)Reply
I would like to know how the translation namespace was started here, so Chinese Wikisource will have it as well.--Jusjih (talk) 05:53, 21 March 2014 (UTC)Reply
We had a discussion about translations (and other derivative works): Wikisource:Requests for comment/Annotations and derivative works#Translations. After that came to consensus, we filed a request on Bugzilla to create teh namespace: bugzilla:50007. There were a few details to work out about how we would use the new namespace but that's how it all started and got going. - AdamBMorgan (talk) 10:46, 21 March 2014 (UTC)Reply

Disagreement over translations edit

I work mainly on the Simple English projects, so I thought of starting a simple English Wikisource. Simple English projects have been created due to their very different, specific target group, which includes those who do not know English well. Some works are written in simplified English (Dr. Seuss, among others), others are translated into it (such as that one book on Shakespeare), and there are many other works that could be translated into it per this page. However, when I tried to create a main page for an SE Wikisource (on oldwikisource, supposedly the place for it), it was deleted and I was told that it could not be a source language and that all English works should be here regardless of level. I disagree, for a variety of reasons, most of which can be found on the Simple English Wikipedia, etc. Two of the other SE projects have survived a closure nomination and a third is still undetermined, so it is not the concept (nor its separation from "real" English) that is the problem. I know that this page is not an official policy, but the fact that the page exists and has been around for quite some time gives it credence, not to mention the fact that it is being followed by some. I also know that not everything that applies here necessarily applies to oldwikisource, but most of it does or should, and EN Wikisource is definitely a trendsetter. Therefore, I'd like to know what you all think. I'm also more than willing to hear on this page from the editor with whom I have the disagreement over there. Comments? --Cromwellt|talk|contribs 02:32, 27 July 2007 (UTC)Reply

"Simple" is far too subjective a term to base categories around, muchless entire projects. I've never really understood the Simple Wikipedias, and Simple Wikisource seems even more ridiculous, no offence - but if a Dr. Seuss book is public domain, why not host it here? Unlike "putting up your simply article on "bananas" on the main WP "where it might get complicated by further edits by other users", things simply "are what they are" here. Sherurcij Collaboration of the Week: Author:Maxim Gorky 02:46, 27 July 2007 (UTC)Reply
I agree with Sherurcij in that Simple English texts should be hosted here on the English Wikisource. We should, at some point, have a Simple Texts Portal or something so that English learners quickly find what they're looking for without having to wade through nonsimple navigation pages. One should not forget that simple English texts may be essentially multi-language. For example, a simplified version of The Canterville Ghost (a favourite of educational boards) made for Spanish speakers may be heavily annotated in Spanish. At some point, we'll need a method to properly recognise the multilingualism of certain texts.--GrafZahl (talk) 10:11, 27 July 2007 (UTC)Reply
I completely disagree that the English Wikisource should host simple English texts. Now, what I mean by this is not that works originally written in a simplified version of English (e.g., Dr. Seuss) should be excluded but that we should not take source texts and cut them up so they read much more simply than they did before. The way I see it, converting a text to Simple English is not a translation at all, but merely a transformation, and Wikisource explicitly excludes works which have been changed from the original text to something which is still the text but with modifications.
I think if we collect PD/GFDL texts which are simplistic (although, Sherurcij raises a good question as to the subjectivity of "simple") then I think we can collect them here. But I think making our own violates the inclusion policy for this project.—Zhaladshar (Talk) 15:32, 27 July 2007 (UTC)Reply
It would be preferable to have this matter discussed under two segregated threads. One issue is the publication of works which were simple to begin with such as Dr Suess books. But there is quite another matter of translation. It does violence to a translation to break it down from its level of sophistication into a "version" made simple. It is not the same book, at all. This is probably best discussed with a few examples of different types.
Note also there is a different audience in mind when we contrast English learners from young readers or cognitively impaired audiences. At any rate, I invite suggestions as to examples to fit the discussion. For starters, does Tom Sawyer for ESL students, or Hamlet for ESL students, constitute content for Wikisource? How about, Don Quixote, translated by Wikisource, version for ESL students? Geofferybard (talk) 22:13, 6 May 2011 (UTC)Reply

Stale? edit

This proposal has not been edited since 2008. Is this or is this not a policy? Bennylin (talk) 13:04, 24 November 2010 (UTC)Reply

No, it is not a policy. cygnis insignis 19:21, 27 January 2011 (UTC)Reply
Not yet perhaps, but it is a fine idea and well explained here. I certainly use it as a guideline, and great community translations have happened on wikisource. The ease of starting and sharing partial translations is one of the best reasons to post materials here. Sj (talk) 12:07, 7 July 2011 (UTC)Reply
Not a policy or "guideline" [1]. There has been a suggestion that 'authoritative' societies or published authors could use this site for that purpose, though this is more inline with the scope of wikibooks and wikiversity. Whatever these "great community translations" are, it would not be things like translation of religious text, eg. editions of the bible took teams of scholars and theologians twenty years to complete, here it is done by single anonymous accounts in their spare time. The wonders of wiki-technology and 'crowd-sourcing' do nothing to facilitate this form of self-publishing, which is against the policies of this site. CYGNIS INSIGNIS 13:21, 7 July 2011 (UTC)Reply
I agree that the Bible is a contentious case, because of the many conflicting ideas about what it means to engage in a translation in the first place, and because of the layers of translation variations that are considered significant here [as they are not for most works]. These sorts of translations have generally happened on wikisource, not other sites. The MediaWiki modifications to make side-by-side viewing of two different language versions of a text were developed for use by translators on wikisource texts. Could you provide links to the suggestions you mention having been made? I think wikisource is the right place for translations of primary sources - and I know it is one of the features that makes potential use of the site attractive for, e.g., Classics departments and collections such as the Perseus project. I would be glad to have in a more practical discussion about how to make source translations possible, valuable, and consistent, though this may not be the place. Sj (talk) 14:57, 8 July 2011 (UTC)Reply
The most recent discussion resulted in a user posting The case for translations at Wikisource CYGNIS INSIGNIS 17:32, 8 July 2011 (UTC)Reply

Updates edit

A community discussion at Wikisource:Requests for comment/Annotations and derivative works makes some changes to this policy. I am going to begin making updates to the text based on consensus defined at that discussion. JeepdaySock (AKA, Jeepday) 10:37, 31 May 2013 (UTC)Reply

Name Space edit

Will also need to research how to create the name space meta:Help:Namespace#Custom_namespaces and http://www.mediawiki.org/wiki/Manual:Using_custom_namespaces look like the two primary sources for details. JeepdaySock (AKA, Jeepday) 14:27, 4 June 2013 (UTC)Reply

What about simply renaming the articles in the form Translation:Name? --D.H (talk) 19:38, 4 June 2013 (UTC)Reply
Question: Exactly what advantage is there in having a separate namespace for original translations? The only reasons I'm aware of for having a separate namespace are (1) contents can be excluded from internet search results, (2) contents can be kept out of page statistics. As far as I'm aware, we don't want either of those things to happen with original translations. So, what then is the compelling reason for a separate namespace? Why not simply tag original translations with a template declaring that it's an original translation? --EncycloPetey (talk) 19:50, 4 June 2013 (UTC)Reply
In addition, some translations have been cited outside Wikisource, so if the articles get renamed, at least the original article names should remain (at least for some time) and redirect to the new one. --D.H (talk) 19:57, 4 June 2013 (UTC)Reply
EncycloPetey, I posted similar questions at Wikisource:Administrators'_noticeboard#New_Name_Space. The rationale for making the change is because that was what the community consensus was. It my understanding (from other conversations) that once the the name space is created we as a community can decide to include it in default searches, and of course logged on users can customize their searches.
D.H. I agree that leaving redirects is a basic expectation. Probably with {{Dated soft redirect}}, which are deleted after some time. JeepdaySock (AKA, Jeepday) 10:36, 5 June 2013 (UTC)Reply
So, we're doing it just because we can and there will still be redirects in the Main namespace? That makes absolutely no sense to me. (The circumstances, I mean. Your explanation of them was clear.) --EncycloPetey (talk) 16:30, 5 June 2013 (UTC)Reply
The redirects should be temporary, {{Dated soft redirect}} are deleted regularly. The rationale for name space is because of community consensus as part of the "clearly distinguished from previously published translations" requirement. JeepdaySock (AKA, Jeepday) 19:23, 5 June 2013 (UTC)Reply
I do not think we should use temporary redirects. A lot of incoming links to our translated works are from reddit, blogs, forums etc. Editing these media now is somewhere between hard and impossible; not to mention any printed URLs. It would needlessly invalidate all that work, outreach, communication and enthusiasm for Wikisource and Wikisource translations if we were to delete our end of the links. It is not normal behaviour for people to start internal searches when they find broken links and such breaks would undermine the reputation of our project. Alternative options include hard redirects, {{translations}} pages or some form of permanent soft redirects (including tailor-made templates for this purpose).
NB: The reason for the namespace is mostly to prevent our original translations getting mixed up with professionally published translations. The full debate is here and at times it came close to banning original translations entirely (which is already the case on some other Wikisources). - AdamBMorgan (talk) 19:04, 7 June 2013 (UTC)Reply
What about using the article ID No. ( wgArticleId / MediaWiki:pageinfo-article-id ) ?

That way, we'd still be leaving one namespace for another ( cross-namespace redirect ) but neither namespace designation needs to be present or given in the link text. Click the following & observe...

I'm pretty sure that can be templatized/Lua'd somehow to work inline, cross wiki and so on. -- George Orwell III (talk) 23:13, 5 July 2013 (UTC)Reply
OK, I've tried this with {{translation redirect}} on The Screaming, which is the only page I've moved to the new namespace so far (and in which I'm still testing things a bit). It seems to work so far. - AdamBMorgan (talk) 23:54, 5 July 2013 (UTC)Reply
I've tested it with Translation:The End of Matter. However, the proofread/index extension doesn't work. No links to the individual pages, no index link in the lead. --D.H (talk) 08:28, 6 July 2013 (UTC)Reply

Most recent changes edit

Review of changes after my changes. Most look good, but I do have some concerns, I like the rest, wordsmithing improved the readability without loss of agreed upon principles. Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply

  • Wikisource:Translations#Selecting_translations - I don’t see where this section adds value to a policy page, reads like a an essay and does not provide any clear direction.
    • Propose removal Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply
      Comment: If we had enough content for a separate Help page on the subject, I'd recommend having it there, but we don't really have enough to put on such a page. The reason I placed it into the text was to make people aware of the fact that there often are different translations, and that some forethought can make a big difference. A case in point is Euclid's Elements, a key work in mathematics and for which we have two abortive translations started here. Unfortunately, neither one actually contains the full original work; they are both partial translations to begin with. A little investigative work ahead of time could have saved a lot of trouble in both cases. --EncycloPetey (talk) 21:35, 5 July 2013 (UTC)Reply
  • Wikisource:Translations#Multiple_translations These words "Examples of well-known texts with such multiple translations include Anna Karenina, The Iliad, and the Bible. Wikisource may choose to host more than one translation, particularly when the original work is well-known, or when the translations themselves are well-known.
    In cases where more than one translation may appear, the methodology, style, and goal of each translator should be clearly spelled out and summarized in the header notes of the first page. This information may also appear in a preface or introduction to the work."
    - Does not add value, the concepts are (or should be) covered in the two linked policy/guidelines

The following discussion is closed and will soon be archived:

Thread copied to Scriptorium and continued there to prevent derailing the translations policy discussion.

  • Wikisource:Translations#Parallel_texts - "We need some guidance on community sentiment over how parallel published texts are to be handled." - not sure how this is a problem, they are previously published works, nothing new or different from any other previously published work.
    • Propose removal Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply
      No, we need to have a decision of some kind on this, and include it here. I've gotten various differing answers regarding this issue, and we have nothing definitive. As a result, I haven't started any of these sorts of works even though I'd very much like to. --EncycloPetey (talk) 21:35, 5 July 2013 (UTC)Reply
      I don't know if it should necessarily be part of this policy but, here or on another page, I would like to see some sort of guideline. Wikisource:What Wikisource includes currently states "English Wikisource does collect English translations of non-English texts, as well as bilingual editions in which the target language of the translation is English" (my emphasis). However, this is not always applied. As an example, off-and-on I've been working on Wiltshire, Extracted from Domesday Book, which shows the original Latin parallel to the English translation (the original alternates pages). Meanwhile, in The Statutes at Large, the French portions of the text have been eliminated (I think they might be planned for, or already on, French Wikisource) to leave only the English translation. I think having both in one place, as WS:WWI allows, is best but I'd like a little confirmation. - AdamBMorgan (talk) 14:28, 11 July 2013 (UTC)Reply
      As this would apply to translations, I'd like to see the issue addressed here. If there's already an applicable statement in policy elsewhere, then copying it here with a pointer of some kind back might be enough. I agree with you about hosting published parallel texts (the text of both languages presented here), and would like to do some Latin/English works, especially since some of them (even important ones) can be very hard to find even on the internet. The follow-up would then be to have one done as an example, and link it from the policy so that people can see how it's done. Displaying text side-by-side isn't quite as straightforward when the original has the two languages on facing pages. --EncycloPetey (talk) 18:41, 11 July 2013 (UTC)Reply
      I think the "percentage" or "ratio" of the secondary language (the language other than the one the work was originally published in) to the primary language should help to dictate whether or not we host those portions here.

      If the bulk of the entire work is in one language and only the occasional or excerpts are translated into another language then it makes sense to host both the original & the translation here since hosting excerpts is frowned upon (I believe) no matter what language wikisource you are calling home.

      If the bulk of the entire work consists of roughly 1:1 (or approx. half of which is) a translation vs. the original base [published] language, then it does not make sense to host both portions here -- e.g. the secondary language portion can stand pretty much on its own and cannot be considered merely an excerpt. Each portion should be hosted under each language's WS domain in these cases.

      And as far as Displaying text side-by-side isn't quite as straightforward when the original has the two languages on facing pages goes; just don't DoubleWiki the pre-transcluded Page: namespace versions but the finished post-transcluded mainspace versions (assuming the latter ~50%/50% scenario is in play of course). It seems to me if the content is such that one cannot "neatly" separate the primary language from the translated, we're going to wind up hosting one entire copy under each WS language domain anyway.

      Regardless, imho the existing guideline(s) of avoiding the hosting of excerpts plus the objective assessment of the ratio between original and translated portions should be governing the practices in the majority of these cases if not made [part of a] formal guideline itself. -- George Orwell III (talk) 21:32, 11 July 2013 (UTC)Reply

      Well, Wiltshire, Extracted from Domesday Book is close to 1:1 Latin:English and was printed with the two languages on facing pages. The latter was easy to solve (transclude with a step of 2 and transclude twice, with an offset of just one page). As for the former, 1:1, aspect: the purpose of the book would be completely invalidated if it were split. It isn't just a translation; it was intended as a translation with a comparison to the original (or a version of the original without the contractions and shorthand). Not to mention that, if it were split, neither would be a faithful transcription without the other half.
      If there were two separate versions of the Domesday Book (and that is an eventual goal) then using double wiki on those to show English alongside Latin would be great. There would also be potential for showing other translations alongside each other. But with Wiltshire, Extracted from Domesday Book, the original combined both languages, so any future version of this book (rather than its source material) should do the same. If not here, it should be transcribed complete on mul.ws. However, the book was intended for an English-reading audience. I think it should be hosted here, per the existing policy but mostly because it is an English book that happens to include a large amount of non-English text (call it 49% Latin). The same would be true of other bilingual works in my opinion. If I were to make a guideline, I would say the presence of an English preface/introduction and additional material, like the index of ancient-to-modern place names, puts it into the scope of en.ws.
      It's not very difficult to import it into mul.ws and finish it there if the consensus goes against my point of view but I do think en.ws is the most appropriate place for the book within the Wikisource project. - AdamBMorgan (talk) 22:28, 11 July 2013 (UTC)Reply
      Umm... If that is the way the work was formally published (in the "English" of 1788 via the publishing house located in city of London) - then that is the over-riding consideration to proofreading and transcribing the work in its entirety here on en.WS in the Page: namespace only. Your decision to transclude the proofread qualified content with a step of two to mimic a side-by-side presentation was your subjective choice and your choice alone. It doesn't matter (in my opinion) that the "left" page is in Latin and the "right" is in English; this is the English language specific Wikisource domain and such methods of presentation are contrary to our norms - not to mention pointless under dynamic layouts other than layout one anyway.

      Again, & also in my opinion, you also have made the assumption the potential en.WS visitor somehow benefits from presenting the Latin along with the English. For example, I personally find including the Latin distracting and much rather DoubleWiki-in these portions if I wanted to compare one language to the other. And since entire sections of the work typically spans several pages that are being trascluded in as a whole, the page by page synchronization of content inevitably becomes "lost", making some aspects of any meaningful side-by-side comparison pretty much moot in the process.

      So, imho, both the Latin and the English Page: namespaces should contain the entire proofread content, have each language transcluded to each WS language domain's mainspace and then have the ability to DoubleWiki these in on-the-fly if the reader wishes to compare the two. Otherwise, I think we'd need to come up with a new way to toggle the current presentation to default to 'show just the English' portions maybe???? -- George Orwell III (talk) 03:23, 12 July 2013 (UTC)Reply

  • Wikisource:Translations#Wikisource_original_translations - "For translations, the first priority at Wikisource is the contribution of previously published, public domain translations. However, in light of the fact that there are countless source texts published in other languages that might never be translated otherwise, plus the fact that new, complementary translations can improve on existing ones in many ways, Wikisource also allows user-created wiki translations." - This seems overly wordy, I am particularly opposed to the "first priority" statement, it implies a disregard for contributors interested in creating Wikisource translations, or considering them second priority contributors.
    • Propose rewrite. Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply
      Comment: I think this text was copied verbatim from another location, but can't recall for certain. --EncycloPetey (talk) 21:38, 5 July 2013 (UTC)Reply
      I have re-written this as "Wikisource also allows user-created wiki translations. This allows for the translation of texts that have never before been translated into English and for new, complementary translations that may improve on existing ones in many ways." I think it works. It places the point first and explains the reasons without favouring the published version. Please revert or amend as appropriate. - AdamBMorgan (talk) 13:18, 12 July 2013 (UTC)Reply
  • Wikisource:Translations#Categories - "Should the year category be that of the original, of the translation, or of both?" - Not a problem for this policy, would be addressed by categories guideline/policy.
    • Propose removal of these words, no objections to removal of the entire section. Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply
      Do we have a categories guideline/policy? Jeepday (talk) 11:51, 4 July 2013 (UTC)Reply
      We should have at least a guideline or recommendation, and as this issue most definitely applies to Translations, it logically should appear here. This is a special case of any category policy we might (or might not) have. I wouldn't mind seeing this worded explicitly as a recommendation, but would not want to see it removed entirely. We have enough problems already with items not being put into any categories. --EncycloPetey (talk) 21:35, 5 July 2013 (UTC)Reply
      Any work in the Translation namespace is likely to be closer to a living document than our regular works. I'm not sure what year we would even choose: the creation date, the last edit date or the most significant edit, for example? As such, I don't think we should categorise by the translation date in these cases; just the original. In the case of published translations in the mainspace, I think the date that particular edition was published, as with any other work, would be the one to use. (I admit that, in some cases in the past, I have entered the original or translation year as a category, in addition to the year in the header. We probably shouldn't do that, although it might seem odd listing something like an Ancient Greek work as late nineteenth centory.) tl;dr: original date in translationspace; publication date in mainspace. - AdamBMorgan (talk) 13:39, 11 July 2013 (UTC)Reply
      Thanks for that comment. I could agree to that, if that's the consensus. I have no personal opinions on the issue or I would have voiced them. --EncycloPetey (talk) 18:41, 11 July 2013 (UTC)Reply

Life of Malatesta move to Translation: ns? edit

This translation looks to be consistent with Wikisource translations. We should approach the contributor and have the worked moved to the Translator: namespace,

Interwiki link for the original in Wikidata? edit

Now that the interwiki links have moved to wikidata, what is the best way to use the {{interwiki-info}} code suggested in WS:Translations to mark the original? Is it appropriate to simply use a traditional interwiki link, or should I add an extra colon and type in the text 'original' as I have done?[2] The interwiki-info tags for multiple translations of The Raven seem to be invisible:[3]

{{interwiki-info|fr|(original)}} [[:fr:L'après-midi d'un faune|(French original)]]

--Hroðulf (talk) 14:02, 23 June 2015 (UTC)Reply

A couple of notes for deliberation edit

Luckily, this mess is not a policy. Unfortunately, in some other language versions it is presented as such. So, a couple of comments from an old translator as food for thought.

  • This page is written as if there weren't different kinds of translation with important differences or functions that cannot be mutually replaced. "There should only be a single translation to English per original language work" leaves no room for making, e.g., poetic and prose translations of the same work, or a scientific and literary translations.
  • "A scan supported original language work must be present on the appropriate language wiki, where the original language version is complete at least as far as the English translation. An inter-wiki link to the original language work must be present on the English translation." On "appropriate language" wiki, not Wikisource?
  • What happens if someone inserts that scan into a wiki and it gets deleted for some reason? Is it necessary to delete the translation, too?
  • What about translations from languages that have no wikis, like Sumerian, Akkadian, or Old Egyptian? Not allowed?
Just think about it. Policies should comply with common sense. Translation policies should probably be written by people who know more about translating than that it means finding words "with the same meaning" in different languages. --82.131.24.246 21:14, 16 October 2015 (UTC)Reply

We have principles and guiding documents as a preference, and consensus opinion where we have issues. We set and have minimal policies, and they are generally not a list of rules anyway. Re first dot point, we have enough problems getting translations completed, let alone worrying about variance. Here we are trying to get away from multiple documents being started and abandoned. Further we can only create one Index: ns file, so having multiple translations of the same work is technically impossible. AND we will cross that bridge when it is a problem, and the existing guidance will do for the moment. Second dot point generally that will be a wikisource, but the guidance is naturally broad, just in case. Third dot point all deletions are undertaken through a discussion process, and we will cross that bridge when we have to, and these processes take time here. Fourth dot point All languages have a wiki, if it is not a separated language, we host the remaining languages at www.wikisource.org. — billinghurst sDrewth 06:26, 17 October 2015 (UTC)Reply