Jump to content

Vicifons:Scriptorium/Vetera VII

Nexus addere
E Wikisource

Textes de la Norvège

[recensere]

La bibliothèque nationale norvégienne a commencé un programme pour numériser ses textes. Les textes qui sont PD sont tous publiés sur leur site web en version PDF, et peuvent être téléchargés par quiconque. La plus grande partie des livres sont en norvégien/danois/suédois, mais, il y a parmis eux des textes allemands, français, anglais, et aussi en latin. Peut-être ils peuvent être utiles pour vous. Ici on peut faire une recherche de tout le contenu de tous les textes PD disponibles. Faites une recherche pour un mot qui est "typique" en latin, et vous trouverez des textes dont vous pouvez vous servir. Mais faites attention: Ça peut arriver que ce que vous trouverez sont des citations latines dans un texte écrit dans une autre langue. S'il y a des questions n'hesitez pas à me poser des questions. V85 01:50, 7 Martii 2010 (UTC)[reply]

Merci and thanks for sharing. In English: the Norwegian National Library offers also scans of Latin texts. A search for e.g. "quam" yields 354 hits. --Matthead 02:29, 24 Martii 2010 (UTC)[reply]
Ipse conatus sum: ecce exempla ex atque et cum. - εΔω 20:21, 10 Aprilis 2010 (UTC)

Wikimania Scholarships

[recensere]
Disputatio conclusa :  

The call for applications for Wikimania Scholarships to attend Wikimania 2010 in Gdansk, Poland (July 9-11) is now open. The Wikimedia Foundation offers Scholarships to pay for selected individuals' round trip travel, accommodations, and registration at the conference. To apply, visit the Wikimania 2010 scholarships information page, click the secure link available there, and fill out the form to apply. For additional information, please visit the Scholarships information and FAQ pages:

Yours very truly, Cary Bass
Volunteer Coordinator
Wikimedia Foundation —Preceding unsigned comment added by Jyothis (talk • contribs) 08:27, 25 March 2010 (UTC)

Thanks for letting us know about the scholarships for Wikimania 2010 in Gedanum / Dantiscum. --Matthead 13:04, 25 Martii 2010 (UTC)[reply]

Agricola

[recensere]

Hi,

I just started Liber:Cornelii Taciti - Agricola.djvu but

  1. I don’t speak good German, so I think I will just add the latin text here, is it right ?
  2. I’m not used to the Vicifons and I don’t know very well the “formulae”

Cdlt, VIGNERON 14:12, 28 Aprilis 2010 (UTC)[reply]

thank you for your very good contribution!
I'm here to help. Just ask here, or leave a message in my talk page here or (better) on it.source.
I can't write in French, but If you like you can write in French and as an Italian native speaker (with some technical knowledge of other languages and some wikiexperience) I'll try to understand it.
nisi autem tibi verba Latine inscripta displicent, sic sane inter nos scribatur :D - εΔω 15:29, 28 Aprilis 2010 (UTC)
Another Question about Agricola. I tried to edit some of the bilingual pages, which have german Text eg. Pagina:Cornelii Taciti - Agricola.djvu/59, but in edit mode only the latin text appeared. Whats wrong? --Catrin 08:11, 11 Maii 2010 (UTC)[reply]
Catrin: Nothing wrong: edit a page: on the left, near the "magnifying lens" button : clic on it and you'll be able to edit the German text hosted in the lower separate box.
VIGNERON: I think we should take that German text outside the footer, put Latin and German texts in separate labeled sections and transclude the Latin text in namespace0. It's a little less smooth, but prevents what Catrin has just written. What do you think? - εΔω 16:39, 11 Maii 2010 (UTC)

Thank you, i actually didn't expect the german text in the footer. --Catrin 20:18, 11 Maii 2010 (UTC)[reply]

I just tried to use sections partial transclusion. It seams to work fine on Pagina:Cornelii Taciti - Agricola.djvu/15page 15, but fails with Pagina:Cornelii Taciti - Agricola.djvu/63. I don't know why. Do you see any german text in the main document? may be it is a cache problem? --Catrin 20:42, 11 Maii 2010 (UTC)[reply]

Indeed, the footer was a bad temporary solution. I will correct it. Section are far better but instead of section=1 and section=2, I would prefer section=la and section=de (it seems more explicit for me), is there an opposition ? Cdlt, VIGNERON 11:41, 12 Maii 2010 (UTC)[reply]

No opposition. The more explicit, the better they are. We are on a multilingual project. As for the German commentary, we have thee choices:
  • Leaving it on the page namespace: no harm, but no chance to read or print it decently.
  • Transcluding it here (but breaking the rule "Only Latin texts here")
  • Transcluding it on Oldwikisource through Iwpage transclusion (but it could cause some diplomatic incidents).
No haste, but let's discuss. - εΔω 13:10, 12 Maii 2010 (UTC)
Ok, I begin the change 1/2 to la/de.
  • Indeed.
  • Probably the less bad solution.
  • Oldwikisourcer will tell us that it has nothing to do on Oldwikisource (and they will be right) and will send us to de.wikisource… (back on the start…).
Cdlt, VIGNERON 13:29, 12 Maii 2010 (UTC)[reply]

New section about Agricola

[recensere]

Disputatio de libro, legenda est, quaeso... - εΔω 13:42, 12 Maii 2010 (UTC)

Protected edit request

[recensere]
Disputatio conclusa :  

Greetings. Could an administrator please add the interwiki link vi:Kinh Ăn năn tội to Actus contritionis? The page seems to be protected for some reason. Thanks, Jafeluv 15:22, 26 Maii 2010 (UTC)[reply]

Done, and unprotected. --Matthead 16:08, 27 Maii 2010 (UTC)[reply]

Lettere degli Sforza

[recensere]

(Meno male che posso scrivere in italiano...Da anni che non studio più latino!) Ho trovato queste: sono delle missive scritte dagli Sforza e trascritti a piccì. Però, in fondo alla pagina si può vedere che c'è "© 2002-2010 Regione Lombardia - Università degli Studi di Pavia". Chi vince? I 70 anni dalla morte dell'autore (e penso che l'ultimo sforza abbia batuto il record già da un po') o il simbolo di copyright dell'unipv? --→ Airon 90 13:39, 12 Augusti 2010 (UTC)[reply]

Noterai che chi ti risponde è lo stesso che rispose su it.source: non possiamo trasferire le immagini, né qui né su commons, ma il testo puro e semplice (leggasi ".txt") delle lettere da te creato (leggasi "non copiato da qualcuno che abbbia già trascritto tale testo") non è soggetto a copyright. Tu infrangeresi il copyright se copiassi la pagina web o una redazione scritta compiuta dall'unipv. Nel caso da te indicato, in cui è posta una discreta enfasi sulle operazioni di redazione, propenderei per una prudente astensione. - εΔω 06:14, 17 Augusti 2010 (UTC)

request import from fr.ws

[recensere]

there is a bunch of pages that should be imported from fr.ws. (pages from bilingual books) can we enable import from fr.ws ? ThomasV 08:02, 19 Septembris 2010 (UTC)[reply]

I alreedy ask for some months ago (Disputatio Usoris:OrbiliusMagister). I don’t know why it’s not done.
Maybe I’ll ask for transwiki importer rights to help here.
@Thomas, is Match and split activate on Vicifons ?
Cdlt, VIGNERON 11:24, 21 Septembris 2010 (UTC)[reply]
you have to ask on meta, that fr.ws be added to the list of import sources for la.ws
match& split : yes on the serverside, but you need to import the gadget, or call the script in vector.js
ThomasV 09:07, 22 Septembris 2010 (UTC)[reply]

2010 Fundraising Is Almost Here

[recensere]
Disputatio conclusa :  
Hello Wikipedians, my name is Kelly and I am working for the Wikimedia Foundation during the 2010 Fundraiser. My job is to be the liaison between the Latina community and the Foundation. This year's fundraiser is intended to be a collaborative and global effort; we recognize that banner messages which may perform well in the United States don't necessarily translate well, or appeal to international audiences.
I'm contacting you as I am currently looking for translators who are willing to contribute to this project by helping translate and localize messages into Latina and suggesting messages that would appeal to Latina readers on the Fundraising Meta Page. We've started the setup on meta for both banner submission, statistical analysis, and grouping volunteers together.
Use the talk pages on meta, talk to your local communities, talk to others, talk to us, and add your feedback to the proposed messages as well! I look forward to working with you during this year's fundraiser. If someone could translate this message I would really appreciate it so that everyone is able to understand our goals and contribute to this year's campaign.
Klyman 16:16, 21 Octobris 2010 (UTC)[reply]

Formula:Scriptor

[recensere]

Ave,

I just had a link to the special page index on Formula:Scriptor. Was it a good idea ? Should I had a parameter ?

Cdlt, VIGNERON 07:57, 28 Decembris 2010 (UTC)[reply]

Well, I doubt that these were useful changes. The Scriptor page should introduce an author and his works to the general public, and a link to a special technical tool for Wikisource editors is rather confusing. The Scriptor page itself lists the works of an author, and those works available within Wikisource have little progress indicators like shown next to them. Besides, the new link to Special:IndexPages is broken as it uses only the first name of an author.--Matthead 12:57, 28 Decembris 2010 (UTC)[reply]

WikiProject Translation

[recensere]

Announcing the creation of a new interlingual cooperative WikiProject- WikiProject Translation! The goal is inter-wiki collaboration with the aim of making source texts available in multiple languages. The project is very much in the formation phase, and would benefit from voices giving input. Please feel free to express any ideas, concerns, or questions at the project talk page. In the spirit of the project, please translate this message! --Eliyak 09:36, 10 Ianuarii 2011 (UTC)[reply]

Interwiki-Bot

[recensere]
Disputatio conclusa :  

EN: I would like to run an interwiki Bot on la.ws; I believe there are currently no active interwiki bots on la.ws and no flagged active interwiki bots on any ws.

  • Name: Interwiki-Bot
  • Operator: Doug (talk)
  • Purpose: Interwiki language links
  • Scope: All dela wikisource namespaces (especially Categoriae)
  • Language: Python
  • Mode: Semi-Automatic

Thank you,
DE: Ich werde einen interwiki Bot betreiben

  • Name:Interwiki-Bot
  • Betreiber: Doug (Diskussion)
  • Auftrag: Interwiki-Links (Internationalisierung)
  • Umfang: Der ganze Namensraum von dela.wikisource (besonderlich Categoriae)
  • Programmiersprache: Python
  • Methode: halbautomatisch

Danke,
--Doug.(Disputatio • Conlationes) 23:55, 9 Februarii 2011 (UTC)[reply]

Interwiki-Bot is beginning to make some demonstration edits very slowly and under full supervision.--Doug.(Disputatio • Conlationes) 05:43, 10 Februarii 2011 (UTC)[reply]
It looks good so far. Could you let us know when the bot has been approved on a bigger Wikisource project. John Vandenberg 06:21, 10 Februarii 2011 (UTC)[reply]
Bot has requested approval on de and has given notice on en, technically de incorporates en policy which says interwiki language bots don't need approval. I will let you know when the bot is flagged elsewhere.--Doug.(Disputatio • Conlationes) 11:29, 10 Februarii 2011 (UTC)[reply]

It still looks good. I'll ask the 'crat to take a look. John Vandenberg 19:01, 15 Februarii 2011 (UTC)[reply]

Flagged! --Accurimbono (disp) 11:39, 19 Februarii 2011 (UTC)[reply]

Multi-lingual instructions/mainpage

[recensere]

As I've worked on my interwiki bot, I've been interested to note that a lot of small projects like ours have a habit of having detailed instructions translated or at least summarized in English but hidden behind a mainpage that the average passerby can't read. Considering our particular draw to students and others who aren't fluent readers of Latin, what would people think about either 1) an English language version of the mainpage or 2) a set of multilingual intro pages linked from the main page with, e.g. "Don't know Latin?/Verstehen nicht lateinisch?/(etc.)"? The latter would be easier to maintain and more universal than the former; but the former would allow most users to get the idea of what the mainpage said. When I first came to la.ws, I was baffled by the apparent need to be nearly fluent in Latin just to get by the mainpage. As I poked around and got help from folks such as John Vandenberg and others, especially on IRC, I found it really isn't that hard to get around and to transcribe Latin but communicate in English; but this wasn't immediately obvious. At the very least, I think we need to have a section of the mainpage that is English and gives basic navigation. I'd be more than happy to set up some drafts for discussion, if there's no opposition to the idea. --Doug.(Disputatio • Conlationes) 20:12, 14 Februarii 2011 (UTC)[reply]

Retired Sysop

[recensere]
Disputatio conclusa :  

I notice that Usor:Aramgar is an op but has been retired from all projects since June 2009[1], with the exception of three edits on en.wp last June. His comment on retiring from this project is in reference to the entire Wikimedia Project, not just la.ws, as can be seen from his comments on en.wp and on la.wp. Although the idea of de-opping inactive users is rejected on many projects and I have no problem with inactive ops, especially on a small project where there is no reason to think they are actually gone; expressly retired users are often noted as a security risk since their accounts may be targets for hacking and may become compromised, particularly as older accounts may not have good passwords. Additionally, anyone who has expressly retired can be presumed to have resigned the mop. I suggest we consider de-opping Usor:Aramgar without prejudice towards re-opping should he ever return.--Doug.(Disputatio • Conlationes) 16:55, 18 Februarii 2011 (UTC)[reply]

In small projects like this I think that using common sense should still be enough. I'm always afraid that a decision on a single case could be used as a guideline like a machete, but let me be confident on your knowledge of this context.
As for Aramgar, if
  • His purpose to leave WMF project is out of any doubt,
  • He is not just "on wikivacancy", but he declares himself "retired"
  • He has been warned about this decision.
  • His resignment implies leaving his mop unguarded,
  • This decision comes out of a consensus signed by many users,
Then we can proceed: I have no opposition about his desysoping. Let other users put their sign under mine. - εΔω 17:11, 18 Februarii 2011 (UTC)
Notice given and e-mail sent: Disputatio_Usoris:Aramgar#De-oppying.3F --Doug.(Disputatio • Conlationes) 17:50, 18 Februarii 2011 (UTC)[reply]
OK, agree. But I (as Bureaucrat) can not desysop. Who is supposed to do that? --Accurimbono (disp) 11:51, 19 Februarii 2011 (UTC)[reply]
Good point, it requires a steward. If we have agreement, I'll ask Pathoschild or another one.--Doug.(Disputatio • Conlationes) 16:24, 19 Februarii 2011 (UTC)[reply]
I agree with desysoping, however they have my support if they ever wish to resume activity here. It is done by consensus here followed by a request at meta:Request for permissions#Removal of access.
With regards to the general point about desysoping, Commons has a regular sweep of inactive sysops, English Wikisource has annual reconfirmations, and Multilingual Wikisource has periodically removed inactive sysops. I think the Multilingual Wikisource approach is an appropriate level of bureaucracy for Latin Wikisource. While security concerns are a valid reason to remove inactive sysops as a preventative measure, I believe it is also important to keep the sysop list in sync with the set of people who can be called on to help. John Vandenberg 20:20, 19 Februarii 2011 (UTC)[reply]

I still remain unconvinced of the value of this project. There are so many better places on the Internet to find Latin texts of known provenance. The Latin Library is superior to this site in every respect. The Packard Institute will send you a free CD with the whole of Latin literature up to Late Antiquity on it. Vicifons, however, is filled with third rate editions and mongrel version made more idiosyncratic by drive-by 'improvements'. (Vicifons Horace, by the way, is not what it purports to be) Occasionally in my reading, I find something really obscure, the Anthologia Latina or the Cento Probae for instance, texts not included in either the Latin Library or the Packard CD. I frequently type out these sort of texts by way of becoming a more engaged reader. I have in the past uploaded these texts here, which seems rather silly now because the most recent editions of such works are usually available on GoogleBooks. I may yet add things here, but not as Aramgar. Aramgar is happy to cede the mop for a pointless wiki to somebody more qualified, perhaps somebody with OCD, Asperger's, or a wish to emulate Sisyphus. Aramgar 01:43, 20 Februarii 2011 (UTC) P.S. John Vandenberg used to seem like such a nice guy.[reply]

language user boxes

[recensere]
Disputatio conclusa : Implemented, but since overcome by Babel extension.

I have cleaned up Categoria:Language user templates and the corresponding Categoria:Linguae usorum to some extent, creating the missing cats and tweaking the templates. However, I haven't created any new templates, even where there are active users who need them, (e.g. Formula:Usor fr-1) because (well, because I'm don't have importer rights and) I'm not sure this is the best method. Do we want to use the Babel system or the User language system?--Doug.(Disputatio • Conlationes) 15:00, 20 Februarii 2011 (UTC)[reply]

I thought about importer rights for myself, but after reading the requirements it seems like you're asking for a gold medal in an Olympic contest. Until licence let me fiddle with the code we still can get through, even of with dirtier hands...

My concerns are the following:

  • are we going to wait for Babel extension forever.... just to discover that we don't like it?

If your answer is no, let me introduce the following:

  • Are we going to implement the "template:User language" system?
    1. If your answer is no, let's work for another system.
    2. If your answer is yes, let's plan a customization policy to tailor the system exactly to our needs and tastes.

My POV:

  • I've already introduced meta's system into a pre-existent babel system in it.wikisource. We should pay attention to some legacy issues that here can be handled before any further step.
  • It's been some time since I'm thinking about using labeled sections to store most of babel content into one or very few pages to which many babel template would point. That'd be a new approach but after some failed experimentation I need some technical advice to put it into action.

By the way: I'd be happy to share this both on en. and la.source. - εΔω 11:22, 22 Februarii 2011 (UTC)

Let's move the discussion to Disputatio Vicifontis:Babel/Linguae - εΔω 11:42, 22 Februarii 2011 (UTC)

[2] Babel extension is coming. Translators needed to review and add translations; e.g. Latin. John Vandenberg 20:59, 24 Februarii 2011 (UTC)[reply]

Jay, what do you mean? Translatewiki.net has had this a long time but is not an MWF project (and the link to MW in the article is spurious they really intend to link to Translatewiki). I don't see any indication here or at MW that this has ever been taken up for approval for use on WMF projects. It works but it isn't deployed and the last indication on MW was that it isn't going to happen any time soon unless someone can convince development to test it. See this discussion: mw:User talk:MinuteElectron#Babel extension - ready to deploy? and my other comments here: en:Wikisource:Scriptorium#Babel extension; I don't believe we can continue to wait indefinitely for this in the vain hope that it will be out soon.--Doug.(Disputatio • Conlationes) 09:11, 25 Februarii 2011 (UTC)[reply]
It is not ready to deploy yet because the messages havent been translated. translatewiki is not a WMF project, but translatewiki and mediawiki are becoming very closely linked together. John Vandenberg 07:20, 26 Februarii 2011 (UTC)[reply]
  • I've asked Pathoschild to import his "user language" system with support for a few major languages. He's looking at incorporating Orbilius's single page of data for language data over the next few days. If we like his system, we can deprecate the old babel userboxes. My understanding is that everyone agrees, Pathoschild included, that the extension would be the best solution for all but it is not an option now and won't be anytime soon.--Doug.(Disputatio • Conlationes) 11:01, 26 Februarii 2011 (UTC)[reply]

Enabling Import

[recensere]
Disputatio conclusa :  

I think this has been discussed before, maybe a year or two ago, but I've taken the liberty of filing a bugzilla to enable importing from most of the major Romantic language subspaces plus English, German, and Greek as well as from la.wp and la.wb. You can vote on the bug importance or add more languages by editing the bug at the link above. Statements in favor or opposed can go here. Thanks.--Doug.(Disputatio • Conlationes) 20:22, 3 Martii 2011 (UTC)[reply]

i support the request ThomasV 20:23, 3 Martii 2011 (UTC)[reply]
me too John Vandenberg 19:13, 4 Martii 2011 (UTC)[reply]
I just received a bug status update that his is done. Someone who has import rights please test it and confirm. Thanks.--Doug.(Disputatio • Conlationes) 23:11, 18 Martii 2011 (UTC)[reply]
ARGH! I tried it: it let me import only from meta and commons! Is there an error? John, take a look, please. - εΔω 07:27, 19 Martii 2011 (UTC)
It doesnt work. I have reopened the bug. John Vandenberg 14:59, 19 Martii 2011 (UTC)[reply]
✔ Perfectum est.BTW, this was been enabled[3].--Doug.(Disputatio • Conlationes) 08:57, 4 Augusti 2011 (UTC)[reply]

DougBot

[recensere]
Disputatio conclusa :  

I would like to run an DougBot on la.ws; DougBot is currently flagged on en.ws for the same purposes intended here.

  • Name: Usor:DougBot
  • Operator: Doug (talk)
  • Purpose: custom replace or add jobs on works that I'm editing such as basic formatting or adding a template across a work as well as running djvutext.py on works I'm about to edit. The bot would also be available for broader work when required such as replacing categories, but no work outside of individual works is planned.
  • Scope: All la wikisource namespaces but primarily pagespace
  • Language: Python
  • Mode: Semi-Automatic/supervised.

I request a flag. I can make demonstration runs if desired, though you can see the bot's work at en:Special:Contributions/DougBot. --Doug.(Disputatio • Conlationes) 00:35, 5 Martii 2011 (UTC)[reply]

There being no objections in a week, I'm going to start operating unflagged for the time being.--Doug.(Disputatio • Conlationes) 16:49, 12 Martii 2011 (UTC)[reply]

Extension:Babel

[recensere]
Disputatio conclusa :  

Other discussions: Vicifons:Scriptorium/Vetera_IV#Babel, Vicifons:Scriptorium#language_user_boxes, en:Wikisource:Scriptorium#Babel extension

If mw:Extension:Babel is approved by the devs (bugzilla:15308), would Latin Wikisource be willing to test it? Six other small projects have requested it to be installed. If there is more support, it is easier for the WMF to justify asking a dev to look at it. John Vandenberg 01:17, 5 Martii 2011 (UTC)[reply]

  • Bless you OrbiliusMagister! What customisation would you like? John Vandenberg 10:09, 26 Martii 2011 (UTC)[reply]
    • Well, John, after years spent wandering through projects and discussing about many features of this system there is almost none of them that I wouldn't like to be easily customized. Let me show some examples:
      1. I'd like to customize the text of a message in a template without having to get a wikiworldwide consensus
      2. I'd like to be free to decide if colours should use a linear or a logarithmic gradient from pink through blue to green.
      3. I'd like to customize if categories would be strictly "commons style" or "all inclusive"
      4. I'd like to customize the category of "Category:Users main language-0" (we are just discussing about it here)
      5. I'd like to customize the font used in single messages (translatewiki proposes an awful monospace font).
I can go on but I know I'd be boring... - εΔω 16:58, 26 Martii 2011 (UTC)

Deprecate cross-namespace redirects?

[recensere]

I propose we deprecate the old redirects from mainspace to authorspace (and any other cross-namespace redirects). The search engine is fully capable of finding the authorspace pages so these are unnecessary and they can create conflicts for works about the authors. Furthermore, I've found some pages that were never actually redirected and that had strange things done to them (e.g. Carl Friedrich Gauß), so it would be best to just remove them all.--Doug.(Disputatio • Conlationes) 21:57, 5 Martii 2011 (UTC)[reply]

that's a sound idea, but I'm afraid that some wikisources still have their interwikis pointing to those redirect. It would take a long survey to inspect this issue. - εΔω 18:06, 7 Martii 2011 (UTC)
That's a valid point, though interwiki languages links that are broken can be picked up by language link bots like my Interwiki-Bot. Links from la.wp would be harder to track down, but really should be limited to the article about the author. I can delink the pages and then blank the pages and nominate for deletion.--Doug.(Disputatio • Conlationes) 19:37, 7 Martii 2011 (UTC)[reply]
If you can work it out, that's fine with me. - εΔω 10:31, 8 Martii 2011 (UTC)
Strong support! --Accurimbono (disp) 20:23, 21 Martii 2011 (UTC)[reply]
Support, however we must include the Scriptor namespace in the default search by changing mw:manual:$wgNamespacesToBeSearchedDefault. This requires a bug be created and fixed first.. e.g. bugzilla:12867 John Vandenberg 10:07, 26 Martii 2011 (UTC)[reply]
If you put an author's name into the search box you get the Scriptor page, so this must be implemented here.--Doug.(Disputatio • Conlationes) 11:38, 15 Augusti 2011 (UTC)[reply]

Inactive bots - proposal to unflag

[recensere]

The following two accounts are for long inactive bots with inactive users. I propose we remove their flags. This is not suggested as a negative action but so that we can easily notice should they suddenly become active. I know that the first one is marginally active and highly respected elsewhere (en.ws in particular) and the second is active on commons and en.wp; but we should know if either suddenly starts using his bot on la.ws again. An inactive bot account can become a risk as if it were compromised it could do a lot of damage before it was noticed, especially on a project like ours where activity is very low; so the actual damage might go unnoticed but for the edits in recent changes. Additionally, bots that sit inactive for years with inactive users suggest the reasons they were originally flagged no longer exist. Two other bots are inactive but have relatively active handlers, so I do not suggest we remove their flags (ThomasBot and JVbot). For the two users below, I will notify them of this discussion and I suggest that the closing decision be posted to their talk pages with a clear statement that this is not derogatory re-flagging will not require discussion but me be requested at anytime, simply by leaving a notice here.

I propose removing the flags for both bots.--Doug.(Disputatio • Conlationes) 10:59, 23 Martii 2011 (UTC)[reply]

  • I approve the removal of the flag for White Cat's bot, however I think Zhaladshar's bot should remain an approved bot if he plans to occasionally use it for interwiki work. He is active on English Wikisource. John Vandenberg 09:55, 26 Martii 2011 (UTC)[reply]
    Really, I think he's done using it that way, the bot converted to a more general purpose bot on en.ws and hasn't been used there either, he can get it re-flagged anytime if he starts up again. The flag isn't really permission to do interwiki work, it's permission to do it without us having to watch it flood recent changes. I highly doubt that's going to ever happen but if it does we can re-flag the bot. There are some others who haven't requested flagging that I may suggest we flag anyway if they are back again soon. I also would not call him exactly active on en.ws - his bot ever so much more so.--Doug.(Disputatio • Conlationes) 11:11, 26 Martii 2011 (UTC)[reply]
    I've e-mailed Usor:Zhaladshar to get clarification.--Doug.(Disputatio • Conlationes) 12:21, 26 Martii 2011 (UTC)[reply]
I waited for some time because I'm going to learn from your words. My opinion is different, but I don'know if it's wrong.
If a bot isn't used it doesn't do any harm. A bot doesn't flood RC while inactive, nor we expect it to be run by a different user... so if it gets active again it shouldn't be a problem, so what harm is caused by keeping it flagged? If an inactive bot is to be unflagged we'll need a bureaucrat to unflag and possibly reflag it: is it necessary? I feel I'm missing some piece of policy. - εΔω 16:08, 26 Martii 2011 (UTC)
  • Because the only point to flagging is to say this user is both active and trusted to the point we don't need or want to see it's edits normally in the recent changes feed. If it's inactive there is no reason not to unflag it but plenty of reason to do so. Flags are not a reward, they're a technical tool for us, the other people. There is a risk if a bot account were compromised and the owner is inactive then the owner might not even notice and if flagged we wouldn't notice either until a lot of damage had occurred. It's very easy to re-flag later and none have responded even though I e-mailed them.--Doug.(Disputatio • Conlationes) 13:13, 30 Aprilis 2011 (UTC)[reply]
Done as per Doug request and discussion above:
--Accurimbono (disp) 07:36, 9 Augusti 2011 (UTC)[reply]

Wikisource.fr

[recensere]

Sur Wikisource.fr, il y à ce texte en latin

http://fr.wikisource.org/wiki/Livre:Tamizey_de_Larroque_-_Deux_testaments_in%C3%A9dits_:_Alexandre_Scot,_Jean-Jacques_Bouchard.djvu

Il fait huit petites pages : quelqu'un pourrait-il le relire et le corriger, je m'occuperai de la forme et des notes, mes connaissances en latin sont si faibles que j'ai peur de rajouter des fautes. Merci de votre aide.

Voici le lien vers ma page de discussion sur wikisource.fr

http://fr.wikisource.org/wiki/Discussion_utilisateur:Le_ciel_est_par_dessus_le_toit

Well, there's no use in being chauvinists. That user made the best choice and we don't pride ourselves if we don't have all the exclusive control over all Latin texts: I think we should create here a page listing all such texts which are not completely in Latin, and are hosted on other wikisources: After all what they need is a willing proofreader, and I find no problem proofreading here or there.
The idea of a "multilingual hub page" in every wikisource is already present in many projects: let's revamp it. - εΔω 08:22, 28 Martii 2011 (UTC)
I'm not sure where the chauvinism is; I'm not suggesting Latin is better than French or vice versa. The general rule (actually the practically exclusive rule) is that text that falls within the scope of one project should be considered outside the scope of other projects. If text is Latin, it belongs on la.ws, if text is French it belongs on fr.ws. When the scans are of annotations, they create a conflict between the rules. We shouldn't be transcribing them in two projects and they may well be the best available support for the original work that we have available but we don't want the annotations to be transcluded in our mainspace here and they are the very point that makes it within fr.ws's scope. The solution becomes a very awkward set of #ifeq's OR separate transcription in both projects, neither of which is really the best answer. This is because we have Balkanized into projects that are largely disconnected. I'm also ranting slightly about the larger problem with it's more day-to-day issues of different formatting and different templates, which don't relate directly to the user's request. I'm finding this particularly frustrating as I'm working on several bilingual English/Latin and French/Latin works, albeit unannotated ones.
I was not criticizing the user who posted. She or he may have even intended that we transcribe it here not just help, I don't know. I was just pointing out to anyone what we ought to do. I'm tending towards the #ifeq solution until someone comes up with a better system.--Doug.(Disputatio • Conlationes) 18:56, 28 Martii 2011 (UTC)[reply]
er.. here's my en-2 gap about lexical meaning: the word chauvinism was meant with humour. Now I can't answer clearly to this problem which affected me and VIGNERON when we tried an agreeement with de.source to host the German notes in this book. I'll elaborate an answer tomorrow. - εΔω 21:08, 28 Martii 2011 (UTC)
Oh, that's probably my fault for taking you too serious ;-)--Doug.(Disputatio • Conlationes) 05:18, 29 Martii 2011 (UTC)[reply]
I look forward to hearing of your situation with the above work. Though I'm wondering if we might want to spin this off into more general discussion since I've brought us pretty far afield.--Doug.(Disputatio • Conlationes) 05:22, 29 Martii 2011 (UTC)[reply]

Interproject transclusion

[recensere]

In my experience with interwiki transclusion I faced some problems when dealing with this book. The footnotes could easily be divided through labeled sections and passed to de.source, but when I tried to share this idea with the de.source community I found these negative answers. The bold sentencs that followed

Wenn der Text sich hier befindet, hat man VOR der Neueinstellung unsere Regeln zu beachten und da gibt es nichts dran zu deuteln. So läuft das nicht --134.130.68.65 16:57, 11. Mai 2010 (CEST)

enlightened me: each project has different approaches about rules or restrictive criteria, and we are in no position to force them to do anything in their project, so sometimes text in different languages have to stay outside their proper place. I think that creating a special page to list such examples from all wikisources could be an idea. The core concept is: it doesn't matter if a page in Latin is proofread here or there, if it is proofread!

however I know that I'm proposing something of an exception to the general rule "every wikisource with its proper language" but the general principle holds true with a fair amount of pages entirely in different language. Let's go on discussing. - εΔω 17:21, 29 Martii 2011 (UTC)

Fabrice Dury has been even transcluding parts of pages - if I understand what he's doing at all - and I'm not at all sure that I do. This seems a very problematic way to handle things and an example of why our balkanized projects are bad - they just don't work for multilingual texts.--Doug.(Disputatio • Conlationes) 13:39, 25 Iulii 2011 (UTC)[reply]

Several regulars on German Wikisource, admins and anons alike, are rather elitist and rude. Apart from personal traits, German Wikisource is not tolerant towards "construction sites" that remain incomplete or without proofreading by others. If a user wants to add a large project, the user should have proof-read other projects before, and should provide support by other users that promise to do the proofreading. --Matthead 16:03, 28 Iulii 2011 (UTC)[reply]

Yes, I ran into this there as well, it's a ridiculous rule and it destroys the ability to work on a multilingual work. They also have an additional layer of proofreading and you have to have make sure there is someone to do that too I believe. Their rules are particularly shocking when you go there thinking you can set up a German work or the German side of a multilingual work and they simply delete it, as happened to me. They then tried to get me to validate the text from a photo of a gravestone to "get me started". It was quite insulting. I'm not fluent in German and I can't read their policies in detail, but I can transcribe ancient works, apparently they don't want us to. This is just one very big example of the serious problem of our Balkanization.--Doug.(Disputatio • Conlationes) 21:11, 29 Iulii 2011 (UTC)[reply]

A new liber with Iwpage trasclusion from it.source

[recensere]

I'm going to work into Liber:Il Catilinario ed il Giugurtino.djvu (part), which contains latin fragments by Scriptor:Gaius Sallustius Crispus paired with 13° century Italian translation by F. Bartolommeo di S. Concordio. Please take a look to general file settings. I had too to create here some formatting templates, Formula:Xx-larger, Formula:X-larger, Formula:Larger, and Formula:Center, very similar to recommended templates into en.source, to save formatting while cross-transcluding Italian and Latin texts with Formula:Iwpage. I only created Liber and one Pagina only: Pagina:Il Catilinario ed il Giugurtino.djvu/226, please review them and fix any mistake, so that I can learn by example.

Looking at that page, you'll see too a css issue. There are running tests into it.source, one of them is related to page quality data transclusion; and you'll see a strage "226,3,Silvio Gallio" in the top of italian part of the page. If you go into it.source, those data (number of page; pagequality level; last contributor) are invisible, since there's a Common.css statement span.SAL {display:none;}. How to solve this minor issue? --Alex brollo 21:19, 7 Aprilis 2011 (UTC)[reply]

I saw that test page has been reviewed. Thanks OrbiliusMagister! I consider that edit an encouragement to go ahead as I began, and that inserting here new, cross-running templates is acceptable, when Iwpage procedure is needed. Stop me as soon as possible if I'm wrong. ;-) --Alex brollo 08:18, 8 Aprilis 2011 (UTC)[reply]
Well, you're welcome and I encourage you to go ahead. Just pay a little attention before importing many template: Just check if those templates are already present here (even with a Latin name). Then I think that if your example is followed by every user popping in from other wikisources, our Template namespace would soon become a complete babelic mess. I think that interwiki transclusion can accept a reasonable amount of "ugliness" (and in our homewiki we shouldn't indulge too much in exoteric templates :D) for the sake of simplicity. - εΔω 16:36, 8 Aprilis 2011 (UTC)
I'd guess it, but perhaps saw some "red templates" into the text imported here by it.source, and I suppose that I'll see "red templates" into it.source if I use here, in Latin text, local templates unknown into it.source. Or - am I wrong? This is why I used only "standard" (en.source) templates. Luckily, there's something moving into "interwiki transclusion", and one of aims is exactly the use of templates fron other projects, without any need of importing their code. Well, I suppose that Center, Larger, X-larger, XX-larger templates are both simple and useful, and I'll do any effort to import how less templates I can. --Alex brollo 21:32, 8 Aprilis 2011 (UTC)[reply]

Poem formatting

[recensere]
Disputatio conclusa :  

After pulling the pages over from enWS for Pyramus et Thisbe (which I know duplicates another version of Metamorphoses, though this one is paired English and Latin), I see that your poem formatting is one that we used to use at enWS, though we changed to prevent the spacing between close and open poem tags. Can I recommend that you have a look at en:Mediawiki:Common.css and steal our poem formatting. Billinghurst 12:00, 16 Aprilis 2011 (UTC)[reply]

YEAH! I'm a jiff away from transcluding this text and I've been thinking about this issue for some days. I'll do it very gladly. - εΔω 15:05, 16 Aprilis 2011 (UTC)
✔ Perfectum est. Everything's fine now. - εΔω 15:59, 16 Aprilis 2011 (UTC)


Tituli formulae - Header templates

[recensere]
Disputatio conclusa :  

Well, the issue is quite complex, so I'm breaking it into parts:

  1. there are three header templates: they should be merged them into one and only one.
  2. I propose to try and implement a modern header template: in the last two years, through many wikisources, header templates underwent many changes and improvements: we need
    • a clean way to merge Formula:Liber into the header
    • a simple way to have subtitle parameters and transcluded titles from proofread pages visually coexist.

To have this roadmap completed I can develop by myself only part of the process: I need

  • Consensus about this idea
  • consensus about the designated template
  • and finally a bot and its manager willing to help me.

I'm going to prepare in a sandbox this new template. Feedback is welcome! - εΔω 07:00, 17 Aprilis 2011 (UTC)

  • What are the three templates? I know {{titulus}} which is junk and {{titulus2}}, what's the other one?
  • I think it's important first to clarify do we want the header to be in addition to or in place of the the title on the title page? They seem to be frequently used "in place of" here and on fr.ws but on en.ws where a different sort of header is used altogether, they are always "in addition to" because the complete text is always to be transcribed. With the current titulus/titulus2 format, this looks awfully redundant but using it in place of the title often changes the title from the genitive to the nominative, which means it's not like the original. Another issue is where we want meta data to display and why.
  • I can provide my bot when the time comes.

  • --Doug.(Disputatio • Conlationes) 14:34, 21 Maii 2011 (UTC)[reply]

Call for image filter referendum

[recensere]
Disputatio conclusa :

The Wikimedia Foundation, at the direction of the Board of Trustees, will be holding a vote to determine whether members of the community support the creation and usage of an opt-in personal image filter, which would allow readers to voluntarily screen particular types of images strictly for their own account.

Further details and educational materials will be available shortly. The referendum is scheduled for 12-27 August, 2011, and will be conducted on servers hosted by a neutral third party. Referendum details, officials, voting requirements, and supporting materials will be posted at Meta:Image filter referendum shortly.

Sorry for delivering you a message in English. Please help translate the pages on the referendum on Meta and join the translators mailing list.

For the coordinating committee,
Philippe (WMF)
Cbrown1023
Risker
Mardetanha
PeterSymonds
Robert Harris

Admin nomination

[recensere]
Disputatio conclusa :  

Since it's been over a month and no one has commented, I thought maybe, just maybe, I should let folks know that John Vandenberg nominated me for admin in May here: [[5]], please take notice. Thanks. --Doug.(Disputatio • Conlationes) 18:54, 7 Iulii 2011 (UTC)[reply]

Thanks!--Doug.(Disputatio • Conlationes) 10:37, 17 Iulii 2011 (UTC)[reply]

Carmina Nicolai Hussoviani

[recensere]

Salvete!
Duos libros a Nicolao Hussoviano scriptos addere volo:

  • Carmen Nicolai Hussoviani de statura, feritate ac venatione Bisontis, 1523 (paginae hic) et
  • Nova Et Miranda De Turcis Victoria, 1524 (paginae hic).

Potestne aliquis me in his paginis ad Commons addendis ac in paginis librorum creandis adiuvare? Gratias ago --Trevas 16:56, 19 Iulii 2011 (UTC)[reply]

[recensere]

Phe-Bot takes over for ThomasBot

[recensere]
Disputatio conclusa :  

Phe-Bot is now doing match & split instead of ThomasBot. I have requested our crat flag it. Until then, he may flood the recent changes from time to time.--Doug.(Disputatio • Conlationes) 16:08, 5 Augusti 2011 (UTC)[reply]

Done, flagged. --Accurimbono (disp) 07:31, 9 Augusti 2011 (UTC)[reply]

Index clean up

[recensere]

I have been cleaning up the indices (Liber namespace), there were several bad file names, redirects that were messing up special pages reports, etc. I moved a few files on commons and did a lot of work with one to get it right. There is an odd blank entry at Specialis:IndexPages (item 25 currently, though it tends to move around as indices are moved). Let me know if you see anything amiss or if you can figure out the problem with the blank index entry.--Doug.(Disputatio • Conlationes) 13:50, 6 Augusti 2011 (UTC)[reply]

Petronius

[recensere]

Scriptor:Titus Petronius Arbiter aut Scriptor:Gaius Petronius Arbiter? Candalua 13:25, 7 Augusti 2011 (UTC)[reply]

cf. w:en:Gaius Petronius Arbiter, w:Publius Petronius Niger#Scriptor, w:Satyrica#De_auctore, w:en:Satyricon#Date_and_authorship.--Doug.(Disputatio • Conlationes) 14:59, 7 Augusti 2011 (UTC)[reply]
I will merge the two authors. I'm not even clear that Gaius Petronius Arbiter is a real name; it's used on en.wp and some other online references but it appears to me to be a conflation of Gaius Petronius/Publius Petronius Niger and Petronius Arbiter based on the conclusion by some that they were the same person. Although I think there is strong evidence that they were, I do not believe it has been established in the scholastic community as fact.--Doug.(Disputatio • Conlationes) 08:28, 8 Augusti 2011 (UTC)[reply]
On second thought, I am not going to merge them until there is further comment. They have different life dates listed.--Doug.(Disputatio • Conlationes) 10:45, 15 Augusti 2011 (UTC)[reply]
The dates 27-66 p.C.n. agree with the dates for Gaius Petronius / Publius Petronius Niger, the Roman statesman; so I believe the answer above the name of the author is still correct, but I don't know where the dates for Titus Petronius Arbiter come from.--Doug.(Disputatio • Conlationes) 11:12, 15 Augusti 2011 (UTC)[reply]

I think we should just stick to what the scholars generally agree about, that seems to be like this: his name was Petronius Arbiter, he wrote the Satyricon, and he died in 66 after the Pisonian conspiracy. And let's leave it to the scholars to decide whether his praenomen was Titus or Gaius and whether he was the same Petronius Niger that was consul in 62 or 63. Candalua 18:28, 18 Augusti 2011 (UTC)[reply]

Agreed, which would also indicate that we shouldn't link the author to either w:Publius Petronius Niger or w:en:Gaius Petronius Arbiter, but rather explain the situation and link in the body of the page to w:Satyrica#De auctore.--Doug.(Disputatio • Conlationes) 15:31, 24 Augusti 2011 (UTC)[reply]
I have moved Scriptor:Gaius Petronius Arbiter to Scriptor:Petronius Arbiter. For now there is a redirect, but I will make it a soft redirect with comments. I have not removed Scriptor:Titus Petronius Arbiter yet, as I want it for a separate discussion, but I will make it a redirect soon.--Doug.(Disputatio • Conlationes) 08:45, 25 Augusti 2011 (UTC)[reply]

Bot Flag Request

[recensere]
Disputatio conclusa : Flagged

I would like to run Mjbot on la.ws; Mjbot is currently flagged on en.ws for the same purposes intended here.

  • Name: Usor:Mjbot
  • Operator: Usor:Mattwj2002 (Mattwj2002)
  • Purpose: running djvutext.py on request as well as running custom replace or add jobs on request such as basic formatting or adding a template across a work. The bot would also be available for broader work when required such as replacing categories, but no work outside of individual works is planned.
  • Scope: All la wikisource namespaces but primarily pagespace
  • Language: Python (en:Python)
  • Framework: m:Pywikipediabot
  • Mode: Semi-Automatic/supervised.

I request a flag; as I intend to run djvutext.py, I expect to be running several hundred pages at a time. --Mattwj2002 18:17, 7 Augusti 2011 (UTC)[reply]

  • Strong support - I asked matt to bring his bot here because I need his help on some projects. I request he start running immediately for demonstration. Matt is also an admin on en.ws and also uses the bot to upload to commons, so he's experience and trusted and I'll be watching the work as I'm editing the texts.--Doug.(Disputatio • Conlationes) 18:28, 7 Augusti 2011 (UTC)[reply]
    • Since I needed matt's help on some particular jobs and since the recent changes aren't going to be any different whether he runs fast or slow, I asked him to run to djvutext.py jobs for me at full speed. I hope no one is too put out by this. Hopefully, he'll be flagged shortly and it won't matter.--Doug.(Disputatio • Conlationes) 21:43, 7 Augusti 2011 (UTC)[reply]
Flagged. --Accurimbono (disp) 07:40, 9 Augusti 2011 (UTC)[reply]


Template:Scriptor - style?

[recensere]

I think we should consider changing the style of {{Scriptor}} to be more like fr:Modèle:Auteur. We have one or two authors, at least, that do not use {{Scriptor}} but instead use the something closer to the French style. Thoughts?--Doug.(Disputatio • Conlationes) 08:30, 25 Augusti 2011 (UTC)[reply]

Questions about multilingual works and template iwpage

[recensere]

There are at least two serious issues with {{iwpage}} and its kin:

  1. There are problems with template content transcluded across subdomains being further transcluded
  2. There is no effective way to control changes to formatting or even content on the remote wiki
  • The two issues are closely related. One editor in particular has gone through and used {{iwpage}} to transclude thousands of partial pages to fr.ws (see Specialis:Conlationes/Fabrice_Dury). The problem with further transclusion is that these cannot then be transcluded to fr.ws mainspace without loss of all the latin content and vice versa unless both projects have implemented another complex and problematic template: {{iwpages}} which fr doesn't have. To do it for sections requires a third such template: {{iwpageSection}} which neither fr nor we have, so the whole process seems pointless, at least until the relevant templates are imported. None of the templates are well documented anywhere, the best documentation being at en.ws: en:Template:Iwpages
  • The second issue is even more serious. Should we wish to set the latin (or even the bilingual) text up here we would want to format it to our standards but it would be in use on a remote project. On a page where parts of a single page are in one language and parts are in another this is particularly problematic. The best solution, I think, would be each project transcribes (or imports and formats to local standard) every page that they wish to use locally in any form and that {{iwpage}} be deprecated. Otherwise, at best there will always be a work that is formatted differently on the same page or on facing pages, since even if we wanted to format the same we would have to import all of the templates as well as the .css in order to do so and a change on either wiki to style would throw the work out of sync. I have run into this myself with Liber:The poems of Gaius Valerius Catullus - Francis Warre Cornish.djvu which would work great to support Catullus's works but would be very difficult to format the same as preferred on en.ws.
  • My inclination is to not use {{iwpage}} at all and to set up all works on both projects. Pages which currently use {{iwpage}} can easily be imported. The problem is, if I wish to set up a work locally, that is already invoking {{iwpage}} I can't without either 1) notifying the other project that they need to import the work if they don't want the formatting to change, or 2) uploading another scan of the same work under a different name so that I can work with it independently here. I have many objections against the entire division of subdomains; however, if we are going to be divided we cannot be beholden to all the subdomains that want to transclude latin works. Thoughts?--Doug.(Disputatio • Conlationes) 12:30, 25 Augusti 2011 (UTC)[reply]

template for errata corrige

[recensere]

Do you have some template to signal that a word is misprinted and must be substituted with another? If not, may I create {{Errata|wrong word|correct word}}, on the example of it:Template:Pt, en:Template:ShowTransclude and their siblings? Candalua 08:27, 26 Augusti 2011 (UTC)[reply]

Let me look around before you create anything. Can you give a link to the example? We don't have a policy here on correcting obvious typos, so the important thing is that it's marked. But we don't want to unnecessarily duplicate templates, so I'll look around. Two other choices would be en:Template:SIC which shows the correction as a tooltip an en:Template:Sic, which does nothing and merely provides a marker. Generally the latter is used when the "error" is not a typo at all but presumed to be an error by the author (or predates current spellings) and probably isn't useful here. It's important in en.ws to mark things that should not be changed. I think we should either use the one you are talking about or SIC.--Doug.(Disputatio • Conlationes) 09:52, 26 Augusti 2011 (UTC)[reply]

Hm, interesting. So if I get it right, on en.source you don't actually correct the error, but simply show the proposed correction with SIC, or just mark the wrong word with Sic and nothing else? On it.source we have a very different rule: if we are sure about the correction, because it's really a trivial error or because the original source has an Errata corrige section where the publisher shows errors made during printing and corrections, we correct them and the correction will show up in ns0 instead of the error. Otherwise, if we're not sure, we just leave it as it is. Candalua 18:33, 26 Augusti 2011 (UTC)[reply]

Yes, though if there is an errata published with the work, we make the normally make the correction and link to the errata. For other errors, the policy there is that there is no way to know what was a typographic error and what was the author's mistake or even intent. Normally {{Sic}} is used just as a marker on works where the "errors" were in the original of a very important work, like the US Declaration of Independence. Whereas {{SIC|Foobare|Foobar}} is used to show apparent typographic errors. The former does nothing, the latter creates a tool tip that would display "SIC:Foobar" below the displayed word "Foobare". The philosophy is essentially that we are curators not "editors", in the publishing sense. Errata are an exception because the publisher obviously would have fixed them but for the unreasonable effort required at the time - and they were identified in the original work. Any change from what is shown in scans beyond that is considered an annotation and those are the subject of current dispute at en.ws--Doug.(Disputatio • Conlationes) 15:10, 29 Augusti 2011 (UTC)[reply]

Ok, and how do you do the correction? Do you have a template, or simply write the corrected word in the place of the wrong one? Candalua 16:04, 29 Augusti 2011 (UTC)[reply]

Well, on en.ws with the template {{Sic}} no correction is made; with the template <nowkiki>{{{1}}}</nowiki> the correction is in the template as show above, but to clarify {{SIC|error|corrected text}}. On some works, errata are shown in a more express way on the page but the correction shows in the mainspace. This is done with statutes and things like that where the original is important but the errata are officially published. I think that {{SIC}} is still used but with a conditional.--Doug.(Disputatio • Conlationes) 10:19, 18 Septembris 2011 (UTC)[reply]

Aide pour mise en place d'un Liber en latin/français, SVP

[recensere]

Vale,

Pour les besoins de l'édition du "De Amicitia" de Cicero en bilingue français/latin, j'ai transféré les pages paires sur Vicifons, mais je ne parle pas couramment latin, même si je suis tout à fait capable de relire un texte (7 ans de latin à l'école). J'ai néanmoins besoin d'aide pour la mise en place sur le site de Liber:Cicéron - Œuvres complètes, Lefèvre, 1821, tome 28.djvu - les pages françaises (impaires) étant sur fr: - Merci pour toute l'aide que vous pourrez me fournir :) --Hsarrazin 13:30, 27 Augusti 2011 (UTC)[reply]

La création d'un livre n'est pas très différente ici de fr.ws. Il y a même moins de champs ici que sur fr.ws.
Je viens de retirer ton message et d’ajouter les liens interwiki entre les deux indexs.
Cdlt, VIGNERON 15:55, 27 Augusti 2011 (UTC)[reply]
Merci Vigneron, c'était pour le titre et le sommaire (que je ne sais pas dire en latin) que j'avais besoin d'aide : "Oeuvres complètes" = "Opera ??"
Par ailleurs, sur fr, il suffit d'indiquer le numéro de la page pour afficher l'image de couverture... ça n'est pas le cas ici : peux-tu y remédier, STP ? --Hsarrazin 17:03, 27 Augusti 2011 (UTC)[reply]
Visiblement Doug s'en est chargé entretemps. Malheureusement, je ne pas aussi souvent que je l'aimerais ici, ie. la prochaine laisse moi un message sur ma page perso.
Cdlt, VIGNERON 17:04, 8 Septembris 2011 (UTC)[reply]

Help sysop

[recensere]

Hi,

Could a sysop create MediaWiki:Proofreadpage header template ? (and delete my mistake : Proofreadpage header template).

Cdlt, VIGNERON 15:57, 27 Augusti 2011 (UTC)[reply]

  • This was actually something I recently added to my list of mw pages I'm working on. Can you put the code you were thinking of somewhere, say the talk page to my list or somewhere in your userspace, so we can work out what we want it to do? e.g. the fr version of this page is very complex, the en version just redirects to their standard header. On a related topic, personally, I'm not in favor of every work having a header on the top of the first mainspace page when it really just duplicates part of the work. It also causes confusion because users think the template should show the author in the nominative whereas the title page in the work is usually in the genitive and we should be reproducing the text as per the work. de.ws omits the header on the first page to good effect in my opinion (though their infobox eats a column down the right hand side of the page). I am not suggesting we don't need this template, I'm simply saying we should work out what it's going to do and think about application.
  • I've been working on this but have also been implementing dynamic layouts so, too many things changing at once. I also have been working on a concept for the proofreadpage header template similar to the de.ws textdaten box, which I think could work really well in our layouts where we center the text with relatively tight margins, similar to fr.ws So please, don't implement broadly right now; use {{titulus}} instead.--Doug.(Disputatio • Conlationes) 12:25, 2 Septembris 2011 (UTC)[reply]

paginae protectae

[recensere]

some pages are fully protected (only sysop can edit), against vandalism I guess. But with this kind of protection, I can't fix interwiki links on them. Is it possible to make them semi-protected? here's the list: [6] Candalua 23:21, 27 Augusti 2011 (UTC)[reply]

  • I will temporarily reduce the protection to semi so you can edit them. I'm not sure if they need to stay at semi. I will re-protect if there is no other discussion since at some point there was either a decision or a practice to lock texts that had been completed, as is done on de.ws and I don't want to override that without discussion. Personally, I think it's a good practice to protect stable works on a low traffic project (I think I'm the only one actually patrolling the recent changes); but now it may be better to consider pending/flagged revisions and then we could simply give flagged bots the reviewer/autoreviewer rights. Thanks for bringing this up. Here's a full list since the pages will no longer show up on the SpecialPages report:
   *Magnificat‎ 
   *Pagina prima‎ 
   *Ave Maria‎
   *Pater noster
   *Salve Regina‎
   *Angele Dei
   *Te Deum‎
   *Gloria Patri
   *Requiem aeternam‎
   *Symbolum Apostolicum‎
   *Angelus Domini‎
   *Veni, Sancte Spiritus
   *Signum Crucis‎
   *Regina Caeli‎
   *Sub tuum praesidium‎
   *Benedictus
   *Veni, Creator Spiritus
   *Anima Christi‎
   *Memorare
   *Actus fidei‎
   *Actus spei
   *Actus caritatis
   *Symbolum Nicænum Costantinopolitanum‎
  • ✔ Perfectum est. - except Pagina prima, please post the interwiki links (here or in userspace with a link here) for the main page and an admin will make that edit. I found only one other page that was already semi-protected, Actus contritionis, it had been reduced last year, apparently. Please let us know when these are done and we'll re-protect, subject to further discussion. Thanks.--Doug.(Disputatio • Conlationes) 14:16, 29 Augusti 2011 (UTC)[reply]

Thanks. Sorry, I didn't say that, but of course Pagina prima should stay fully protected. As for the others, I will run the bot this evening, so tomorrow you can reprotect them if you want. Anyway, if we want to open a discussion, since there does not seem to be much vandalism or edit wars here, I propose to keep semi-protection. Candalua 14:31, 29 Augusti 2011 (UTC)[reply]

See my new thread below for my thoughts.--Doug.(Disputatio • Conlationes) 13:07, 30 Augusti 2011 (UTC)[reply]

protection of completed works - Flagged Revisions as an alternative?

[recensere]

See the above discussion. Protecting works that are validated/100% has apparently been practiced here in the past and is common on some other projects (e.g. de.ws). The procedure has it draw backs, mainly as above with bots doing mass formatting or template changes, interwiki language links, and categorization; but can also affect trusted editors trying to correct errors by earlier editors. On the other hand, this site has low traffic and I believe I'm the only active patroller of the recent changes lately, or at least the only admin. I'm bound to miss something or be away. I recently noticed a request for a deletion that had been around for several months. I only saw it because it was apparently someone exercising the right to vanish as it was acted on by a Steward or Global Sysop and showed up in the recent changes.

An alternative might be to implement flagged/reviewed revisions, as is active on mediawiki and some other wikisources. This creates a stable version of the page, which I think is exactly what we want to have, without requiring draconian measures like full protection. All active users and approved bots could be immediately given reviewer/autoreviewer status and more than 90% of new edits would be confirmed immediately; new editors who are active on other projects would be automatically be given the status as soon as we saw them. Vandalism would not show, even if unnoticed for several weeks. I propose we implement this on la.ws page space and main space.--Doug.(Disputatio • Conlationes) 14:57, 29 Augusti 2011 (UTC)[reply]

  • This is an example of a page with flagged revisions: [7] This is the default/"stable" version. If you click on the "Pending Revisions" tab you see the unreviewed version. (BTW, the unreviewed edits are mine ;) ). More and more, I'm thinking this would be an excellent tool for us. We'd make every current editor a reviewer and as new pending changes popped up we'd quickly check to see if the editor was in good standing elsewhere. If so, we'd simply give them reviewer status. If not, we'd keep an eye on their edits for a bit or, if they turned out to be a vandal, block them. We'd avoid ever having to worry that some vandalism would stay around ruining a lot of work for weeks or months but at the same time avoid ever having to protect any pages. If it ever became a problem, we'd simply have it turned off.--Doug.(Disputatio • Conlationes) 17:45, 10 Septembris 2011 (UTC)[reply]
  • I like the idea of a stable version. Sounds like a good idea for the smaller wikis like this Latin wikisource. I support this idea. --Mattwj2002 17:53, 10 Septembris 2011 (UTC)[reply]
  • I saw it in action in small and big wikis. While I think that an active wiki doesn't need such a feature, a Wikisource and a quiet one like this project would take advantage using this feature. - εΔω 16:38, 1 Octobris 2011 (UTC)
  • Flagged revisions are tested for quite some time on German and English WPs, possibly elsewhere, and I'm not fully convinced yet. For a small wiki like la-WS, a low maintenance option like semi-protection would possibly be the better approach, preventing vandalism (and useful edits) by anons without much further ado. It's somewhat rude, but straightforward. The system with flagged revisions, on the other hand, allows edits by anons, but does not display them, and then asks other editors to review those edits. That creates extra work load, and some confusion, too. But I'm not opposed to a test here. --Matthead 01:54, 17 Octobris 2011 (UTC)[reply]
  • Considering the time that has passed and the number of participants which is about as much as can be expected here, I'm going to submit a bugzilla to implement with the understanding that consensus is to at least try it. Matthead's points are good, we're small enough that if we don't like it after several months we'll just say so without any process. --Doug.(Disputatio • Conlationes) 20:37, 22 Novembris 2011 (UTC)[reply]
    • Be care full with vague statements like "lets try it". Do you mean that you wanted it enabled and then at any time later will need a another consensus to remove it? Or do you mean that after some time X, that it unless there is consensus to keep it, then it should be disabled? There should be more specific agreement on this first. Aaron Schulz 20:55, 22 Novembris 2011 (UTC)[reply]
      • Aaron, for this project, the above is a fairly clear consensus but a consensus to change wouldn't take more than the same number of people, one experienced editor he didn't object to a test and 3 said they support it. "Let's try it" in this case just means that I understand Matthead's concern that he's not fully convinced and we could remove it later if there are problems, but that would take further discussion. I understand the phrase could seem squirrelly, but I confident we agree enough to simply implement it.--Doug.(Disputatio • Conlationes) 21:06, 22 Novembris 2011 (UTC)[reply]
  • Bugzilla:32591--Doug.(Disputatio • Conlationes) 21:06, 22 Novembris 2011 (UTC)[reply]
  • I support this (not as a trial), on the understanding that we will review it in a few months (and form a new consensus if its not working). John Vandenberg 21:33, 22 Novembris 2011 (UTC)[reply]
    • It has been enabled.
  • I agree with John re the review in a few months - though I think it should be optional, that is, if no one brings it up I don't think we need to raise the issue as a formality.
  • A few notes on this
    • There are two rights, editor and reviewer, the former can mark a page as "checked", the latter can mark a page as "quality" (this is confused by the fact that the "editor" right to mark edits as "checked" is called "review", whereas the "reviewer" right to mark edits as "quality" is called "validate" - not to be confused with proofread validation)
    • Admins can grant and revoke editor rights, crats can grant and revoke reviewer rights
    • Even admins and crats have to have the rights given it seems, subject to objections, I will go through and give all admins and crats reviewer rights and any other user who is in good standing on another WMF wiki I will give editor rights unless anyone objects.
    • One thought that has immediately come to me on seeing the first few edits it applies to: when text is added to mainspace without supporting scans, it can only be effectively reviewed by those who can positively identify the source AND know sufficient Latin to verify its integrity. Notwithstanding, all crats and admins should also be reviewers, since we can be fairly certain of scanned texts and since we hopefully all know what we're doing and when not to do it.
    • Do we want to require two checks of texts without scans, even if the first check comes from OM or one of the others who are very good in Latin? I.e. a separate check and validation? I think that's probably unnecessary, though on the other hand it would be consistent with proofreading in pagespace.
    • In the (rather unlikely) event that a page with scans is validated (as in second proofreading) by a user without reviewer rights, we could grant a bot reviewer rights. No need to do this until and unless that happens but just something to think about.
    • Pages in namespaces other than page and main still need to be checked. Not a big deal at our volume and it will point to users who need rights. Later we might want to ask to have that changed.
    • Approved Bots' edits don't need to be checked but do need to be validated. --Doug.(Disputatio • Conlationes) 22:45, 29 Novembris 2011 (UTC)[reply]
  • More information:
    • Apparently, the extension is retroactive but appears to apply in main and pagespace (not sure what others, I read the documentation when I mentioned it months ago, but can't recall, I will re-read). I will work on getting a bot job set up to mark all page space pages where the status = proofread to "checked" and all pages where the status = validated to "quality". I don't think we need to go back through validated pages and review them. Though it may not be practicable for the bot to check whether there has been another editor since the validation, which could be a small problem.
    • I've made all admins + Accurimbono reviewers.
    • I've made several trusted users editors and suggest we all make everyone an editor whom we know from another subdomain--Doug.(Disputatio • Conlationes) 00:14, 30 Novembris 2011 (UTC)[reply]
  • It appears that it was incorrectly set up to cover mainspace, template space, and image space. I will re-open the bugzilla with a request that image be replaced with page space.--Doug.(Disputatio • Conlationes) 05:10, 30 Novembris 2011 (UTC)[reply]

OCR button

[recensere]
Disputatio conclusa : Notice, nothing more to do here.

LA: Quia id non operatur, ego remōvī OCR-bullam.
EN: I have disabled the OCR-button in the common.js as the button hasn't been working for some time.
DE: Ich habe die OCR-Schaltfläche entfernen, weil sie längst gebrochen ist.
FR: J’ai désactivé le bouton OCR dans le common.js, parce que cela ne fonctionne pas.

--Doug.(Disputatio • Conlationes) 13:07, 30 Augusti 2011 (UTC)[reply]

Problems with importing and with namespaces

[recensere]
  1. There is a problem with the import function. See the Specialis:Acta/import. From fr:page:Foo, it records the import coming from fr:pagina:foo, from fr:Modèle:Foo, it incorrectly identifies the target as Formula:Modèle:Foo.
    Bugzilla submitted for number 1.--Doug.(Disputatio • Conlationes) 07:29, 3 Septembris 2011 (UTC)[reply]
  2. There is another problem with links using namespace "Wikisource:" Wikisource:Scriptorium links to en:Scriptorium (a non-existent page) instead of Vicifons:Scriptorium; however, Page:Sandbox.djvu/1 links locally. I need to test further namespaces and then I'll submit a bugzilla.--Doug.(Disputatio • Conlationes) 12:32, 2 Septembris 2011 (UTC)[reply]
    Bugzilla submitted for number 2.--Doug.(Disputatio • Conlationes) 07:04, 3 Septembris 2011 (UTC)[reply]
    Fixed. I tested in my userspace and see no further issues with this bug. Please post if you notice anything.--Doug.(Disputatio • Conlationes) 17:06, 4 Octobris 2011 (UTC)[reply]

Dynamic Layouts and collapsible tables are enabled

[recensere]

I've added two major chunks of code to the common.js, both imported from other js pages for ease of use:

  1. MediaWiki:Collapse.js makes class="wikitable collapsible" and class="wikitable collapsible collapsed" function.
  2. MediaWiki:Layouts.js enables dynamic layouts. It appears that layout 2 is the default at present which is nearly identical to our standard mainspace format. Let me know if there are issues. <div class="indented-text"></div> should no longer do anything.

Both of these were imported (actually copied) from en.ws.--Doug.(Disputatio • Conlationes) 20:06, 2 Septembris 2011 (UTC)[reply]

  • The comment about Layout 2 was apparently a caching error on my end. I have rearranged the code so that the format that is most like our standard is Layout 1. Please let me know if text doesn't appear centered with wide margins by default.--Doug.(Disputatio • Conlationes) 21:53, 5 Septembris 2011 (UTC)[reply]

pages dropped number bug and work-around

[recensere]
Disputatio conclusa : Issue resolved on multilingual wikisource by implementing Inductiveload's workaround.

There is a known bug with <pages/> in which it drops the last page number when pages are skipped. The only solutions thus far have been to 1) ensure the skipped page is marked as "no text" (and either blank or contains {{iwpage}} and include the page number in the range (this is not always possible, for example if the page has local content but it not desired in a particular transclusion) or 2) use {{page}} for transclusion of at least the final page. This has resulted in some cases where {{iwpage}}, a problematic template itself, has been used prophylacticly on this site. Now there is a .js work-around (though not truly a solution) and it will hopefully be implemented soon (it would be best to be done on old.ws as it's part of an imported script - though I may test it here by replacing the imported script with the hack). Thanks to Inductiveload for the hack. --Doug.(Disputatio • Conlationes) 07:52, 9 Septembris 2011 (UTC)[reply]

  • ✔ Perfectum est. Inductiveload's solution was implemented on old.ws after testing here. It's not the ideal solution, which would be to actually figure out why the PageNumbers.js script doesn't work right, but it does solve the problem. If anyone notices any problems with page numbers please let me know.--Doug.(Disputatio • Conlationes) 17:57, 10 Septembris 2011 (UTC)[reply]

Etat d'avancement ?

[recensere]

Vale, fr :Y a-t-il ici un/des modèles permettant d'indiquer l'état d'avancement d'un travail en cours dans une liste, similaire au code {{1/4}} {{2/4}} {{3/4}} {{4/4}} que nous avons en français (voir [8]) ? en: Hello, are there here templates to indicate the level of completion of a text in a list like those we use on fr. (see [9]) ? --Hsarrazin 06:31, 10 Septembris 2011 (UTC)[reply]

In fact, I meant an indicator that you can put on the Author's page, for example, after each text indicated : so that, people looking for texts by Cicero can know that "De Amicitia" is "completed and validated", while "In Verrem" need to be reviewed (that's just an example, I did not check) - we use them very much on Author's pages on fr, and it's very useful to easily check what needs to be done :) --Hsarrazin 18:31, 10 Septembris 2011 (UTC)[reply]
Oh, sorry, I saw the word "list" but didn't know what you meant. I've never seen that. I've often wondered if there were a way to display the status bar beside works. Maybe we should consider importing the template from fr.--Doug.(Disputatio • Conlationes) 20:22, 10 Septembris 2011 (UTC)[reply]
Well, I'm no technician, but on it.source there's a template which adds automatically updating information about a text: the system is not smooth to implement, but is worth studying. Please ask Candalua or Alex brollo to have more details. - εΔω 09:49, 11 Septembris 2011 (UTC)

Babel extension is live

[recensere]
Disputatio conclusa : Babel now in use and all other systems are deprecated on this project.

The title says it all. What shall we do now? - εΔω 16:41, 1 Octobris 2011 (UTC)

  • It has been long talked about, how does it work? Is it better than our system? In what ways? Is Meta or it.ws switching? They both use similar systems to us. For other wikis that use the old babel system, it's a no-brainer, for us I'm not sure it's a big deal either way.--Doug.(Disputatio • Conlationes) 09:32, 4 Octobris 2011 (UTC)[reply]
  • You can see a test of the new system on my user page below our system. It seems to largely duplicate our system. Not sure if it has categorization advantages/disadvantages. Also see m:Talk:Babel extension for a lot of discussion about this. John Vandenberg was a proponent of the system for a long time and was instrumental in getting it moving again. I would like to see his thoughts. The comments on meta suggest that it was deployed hastily without real development (it was stalled for years and then rushed to deployment when a board member and then a super developer got involved, as I recall). I think we might be better to opt-out until the bugs are worked out at least. Fortunately, since we don't use english anymore in our category or template names related to babel, we should find none of the conflicts that some other wikis have.--Doug.(Disputatio • Conlationes) 10:40, 4 Octobris 2011 (UTC)[reply]
  • I'd also be curious what Pathoschild has to say.--Doug.(Disputatio • Conlationes) 11:03, 4 Octobris 2011 (UTC)[reply]

    Hello Doug. Although I'm not fond of the old fluency levels used by the extension (we put a lot of thought into Meta's new fluency level descriptions), I don't think we should maintain conflicting systems with incompatible translations. We're already migrating Metawiki to use the extension exclusively.

    The main problem we're encountering on Meta is the extension's inflexibility, which εΔω has already mentioned. We have some CSS tweaks on Meta to enable custom page layouts, but the extension doesn't support the one-category-per-language structure used on Meta. A request to make it configurable (#31074) was recently rejected, and the outlook is bleak on a request to allow new-style unified categories (#31311). We have temporarily disabled the categories until we can find a solution. —Pathoschild 01:54:35, 10 octobri 2011 (UTC)

I was concerned about costumizability... It looks like many hacks can be achieved through common.css, but I currently agree with Doug's well written thoughts. We don't really need to opt-out, we'd rather try to get this system going like we actually want and then replace the old system with this new one (notice, I'm the guy who spent quite a lot of time tailoring three different Babel systems through five years: this words are far form painless for me to write). - εΔω 09:59, 7 Octobris 2011 (UTC)
I'm currently searching through meta and MediaWiki.org for information about the css classes involed in the extension, and in the meanwhile I'm making some experiments in my personal vector.css in it.source... stay tuned. - εΔω 06:23, 9 Octobris 2011 (UTC)

Deletiones Propositae

[recensere]

I've cleaned up Category:Deletiones Propositae, but left Historia Augusta - L. Verus for now. It is currently empty, as it was blanked by the creator, but the original version contains about 18K of possibly useful text. --Matthead 02:35, 17 Octobris 2011 (UTC)[reply]

Looks like it was delete 10 days later by VIGNERON, not sure if they were aware of this discussion.--Doug.(Disputatio • Conlationes) 20:46, 23 Novembris 2011 (UTC)[reply]

Some indexes

[recensere]

I was looking around for some texts about the Sámi ("Lappish") people in Norway/Scandinavia (using the names Knud Leem and Rasmus Rask, two of the people who first studied them and their langauge). Sadly (for me), these texts from the 18th/19th century contain some Latin text. I have uploaded one such document that is written entirely in Latin: Liber:Anniversaria in memoriam reipublicæ sacræ et literariæ.djvu‎. Another is the file File:Samer.djvu which is bilingual with Dano-Norwegian and Latin text published side-by-side. There is another similar volume with side-by-side Dano-Norwegian text as well. My suggestion would be to let this be an interwiki-project, where :la: proofreads the Latin text, and :no: proofreads the Dano-Norwegian, and then we provide interwiki links to one another. :-)

When it comes to the specifics of proofreading Sámi words, this seems to present some problems. Several letters seem to have a macron above them, with the macron having a downwards hook at the end. I have so far chosen to proofread them according to modern Sámi spelling. So instead of "C̄", I use "Č". The reason is that these letters were inspired by Slavic languages which do use the háček, (and it's easier to input than the macron). The sign "ɔ:" frequently occurs in Danish/Norwegian texts from the 19th century as an abbreviation for "det er" (id est, i.e.). This sign is also used in some of these Latin texts. V85 12:49, 19 Octobris 2011 (UTC)[reply]

Line feed bug - Bot nomination

[recensere]
Disputatio conclusa : Issue resolved. sDrewthbot flagged.
Reference en:Wikisource:Scriptorium#Extra_linebreaks_being_inserted_in_Page_space, there is a linefeed bug whereby extra linefeeds (returns) are being inserted at the end of pages in pagespace and can affect the mainspace transclusions negatively. Usor:Billinghurst has a bot on the English Wikisource, en:User:SDrewthbot and has written a script to repair the problem until the bug is fixed. I have asked him and he's willing to run the script here. I propose flagging Usor:SDrewthbot locally. Subject to objections, I will flag his bot and if there are objections after the fact, he can be unflagged.--Doug.(Disputatio • Conlationes) 11:33, 25 Octobris 2011 (UTC)[reply]

Terms of Use update

[recensere]

I apologize that you are receiving this message in English. Please help translate it.

Hello,

The Wikimedia Foundation is discussing changes to its Terms of Use. The discussion can be found at Talk:Terms of use. Everyone is invited to join in. Because the new version of Terms of use is not in final form, we are not able to present official translations of it. Volunteers are welcome to translate it, as German volunteers have done at m:Terms of use/de, but we ask that you note at the top that the translation is unofficial and may become outdated as the English version is changed. The translation request can be found at m:Translation requests/WMF/Terms of Use 2 -- Maggie Dennis, Community Liaison 01:02, 27 Octobris 2011 (UTC)[reply]

Line feed clean-up

[recensere]
Disputatio conclusa : Issue resolved. sDrewthbot remains flagged.

At Doug's request, I have run SDrewthbot through the laPage: ns to correct the line feed edits; now ✔ Perfectum est. The fix covers all edits from the 1th Oct when the error was introduced. Billinghurst 03:30, 29 Octobris 2011 (UTC)[reply]

  • Thanks Billinghurst, that's 10th of October I believe, just to clarify. If anyone wants me to unflag sDrewthbot, please just say so, but it's an active maintenance bot with a trusted user operator so I don't see any good reason to - except that it wasn't discussed. We may need the bot's help again.--Doug.(Disputatio • Conlationes) 14:27, 30 Octobris 2011 (UTC)[reply]

Flag for CandalBot

[recensere]
Disputatio conclusa : Flagged.
✔ Perfectum est.--Doug.(Disputatio • Conlationes) 12:43, 19 Novembris 2011 (UTC)[reply]
Receptum de "https://la.wikisource.org/w/index.php?title=Vicifons:Scriptorium/Vetera_VII&oldid=155146"