Re: [Wikisource-l] Takedown of BUB book on Internet Archive

[Luiz Augusto]

The funniest thing is that the very same digitization is still available on
Google Book Search (just downloaded the PDF version) and the same title is
available on dozens of records at the HathiTrust consortium [1].

Are some volunteers of Internet Archive lazy to research basic things on
copyright as some of the volunteers of Wikimedia Commons?

If anyone is interested, I'll be glad to convert this file to djvu and
upload to the Wikimedia Commons using my local copy of ABBYY.

[1]
https://catalog.hathitrust.org/Search/Home?type%5B%5D=title&lookfor%5B%5D=a%20manual%20of%20ancient%20history&bool%5B%5D=AND&type%5B%5D=author&lookfor%5B%5D=Rawlinson&page=1&pagesize=20&ft=ft

On Wed, Mar 6, 2019 at 7:39 PM Federico Leva (Nemo) 
wrote:

> Seriously, a takedown for a 1870 book by an author died in 1902?
> https://en.wikipedia.org/wiki/George_Rawlinson
> https://books.google.com/books?id=5mwTYAAJ
>
> Federico
>
>   Messaggio inoltrato 
> Oggetto: archive.org item disabled
> Data: Wed, 6 Mar 2019 17:30:31 -0500
> Mittente: Internet Archive
>
> Hello,
>
> Access to the following item has been disabled following receipt by
> Internet Archive of a copyright claim issued by The Publishers Association:
>
> https://archive.org/details/bub_gb_5mwTYAAJ
>
> Some general information about take down notices and processes may be
> found at https://lumendatabase.org, including information about
> submitting a counter-notice, if applicable:
>
> https://lumendatabase.org/topics/29
> https://lumendatabase.org/topics/14
>
> The Internet Archive provides these links as a potential resource and
> cannot guarantee that any specific information posted at
> lumendatabase.org is accurate or complete.
>
> The Internet Archive Terms of Use, including our Copyright Policy, are
> posted at https://archive.org/about/terms.php.
>
> As a general note: repeated posting of infringing material may result in
> the disabling of a user’s account.
>
> ---
> The Internet Archive Team
>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikimedia-l] Reviewing our brand system for our 2030 goals

[Luiz Augusto]

As usual, they've forgotten to fwd to project lists.

-- Forwarded message -
From: Zack McCune 
Date: Tue, Feb 26, 2019 at 12:14 AM
Subject: [Wikimedia-l] Reviewing our brand system for our 2030 goals
To: , Wikimedia Mailing List <
wikimedi...@lists.wikimedia.org>


:: Apologies for cross-posting to multiple mailing lists. We want to ensure
we spread the word about this opportunity to as many people as possible. ::

Hi all,

We are writing today to invite you to be a part of a community review on
Wikimedia brand research and strategy.

Recently, the Wikimedia Foundation set out to better understand how the
world sees Wikimedia and Wikimedia projects as brands.[1] We wanted to get
a sense of the general visibility of our different projects, and evaluate
public support of our mission to spread free knowledge.

We launched a global brand study to research these questions, as part of
our planning toward our 2030 strategic goals.[2] The study was commissioned
by the Board, carried out by the brand consultancy Wolff Olins, and
directed by the Foundation’s Communications team.[3][4] It collected
perspectives from the internet users of seven countries (India, China,
Nigeria, Egypt, Germany, Mexico and the US) on Wikimedia projects and
values.

The study revealed some interesting trends:

- Awareness of Wikipedia is above 80% in Western Europe and North America.

- Awareness of Wikipedia averages above 40% in emerging markets,[5] and is
fast growing.

- There is awareness of other projects, but was significantly lower. For
example, awareness of Wikisource was at 30%, Wiktionary at 25%, Wikidata at
20%, and Wikivoyage at 8%.

- There was significant confusion around the name Wikimedia. Respondents
reported they had either not heard of it, or extrapolated its relationship
to Wikipedia.

- In spite of lack of awareness about Wikimedia, respondents showed a high
level of support for our mission.

Following from these research insights, the Wolff Olins team also made a
strategic suggestion to refine the Wikimedia brand system.[6] The
suggestions include:

- Use Wikipedia as the central movement brand rather than Wikimedia.

- Provide clearer connections to the Movement projects from Wikipedia to
drive increased awareness, usage and contributions to smaller projects.

- Retain Wikimedia project names, with the exception of Wikimedia Commons
which is recommended to be shortened to Wikicommons to be consistent with
other projects.

- Explore new naming conventions for the Foundation and affiliate groups
that use Wikipedia rather than Wikimedia.

- Consider expository taglines and other naming conventions to reassert the
connections between projects (e.g. “__ - A Wikipedia project”).

This is not a new idea.[7][8]

By definition, Wikimedia brands are shared among the communities who give
them meaning. So in considering this change, the Wikimedia Foundation is
collecting feedback from across our communities. Our goal is to speak with
more than 80% of affiliates and as many individual contributors as possible
before May 2019, when we will offer the Board of Trustees a summary of
community response.

We invite you to look at a project summary [9], the brand research [10],
and the brand strategy suggestion [11] Wolff Olins prepared working with us.

For feedback, please add comments on the Community Review talk page [12] or
email brandproj...@wikimedia.org with direct feedback. You can also use
either of these channels to request to join a group meeting.

We know this is big topic and we’re excited to hear from you!


- Zack McCune and the Wikimedia Foundation Communications department


[1]
https://wikimediafoundation.org/2019/02/07/how-does-the-world-see-wikimedia-brands/

[2] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20

[3] https://www.wolffolins.com/

[4] https://meta.wikimedia.org/wiki/Communications

[5]
https://meta.wikimedia.org/wiki/Community_Engagement/Defining_Emerging_Communities

[6]
https://wikimediafoundation.org/2019/02/26/leading-with-wikipedia-a-brand-proposal-for-2030/

[7] https://lists.wikimedia.org/pipermail/foundation-l/2007-May/029991.html

[8]
https://commons.wikimedia.org/w/index.php?title=File%3AStrengthening_and_unifying_the_visual_identity_of_Wikimedia_projects_-_a_step_towards_maturity_-_Wikimania_2007.pdf&page=56

[9]
https://meta.wikimedia.org/wiki/Communications/Wikimedia_brands/2030_research_and_planning/project_summary

[10]
https://commons.wikimedia.org/wiki/File:Global_Wikipedia_and_Wikimedia_Brand_Research_Report.pdf

[11]
https://commons.wikimedia.org/wiki/File:A_Wikimedia_brand_strategy_proposal_for_2030.pdf

[12]
https://meta.wikimedia.org/wiki/Talk:Communications/Wikimedia_brands/2030_research_and_planning/community_review



-- 

Zack McCune (he/him)

Senior Global Brand Manager

Wikimedia Foundation 
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimed

Re: [Wikisource-l] Errare humanum est, perseverare diabolicum

[Luiz Augusto]

On Sun, Nov 29, 2015 at 8:22 PM, Ankry  wrote:

> > What about two multilanguage Wikisources? One for RTL languages, another
> > for LTR languages.
>
> ... and the third for some Asian scripts:
> https://phabricator.wikimedia.org/T60729 ?
>
> And maybe a separate one for French:
> https://phabricator.wikimedia.org/T14752 ?
>
> If you dig deeper then more such issues.
>
>
Those are related on how MediaWiki renders text, so can be easily
circumvented in a multilingual wiki adding a new feature to instruct
MediaWiki to renders based in a given language. If in Page namespace,
adding to the current

tag a lang parameter


or, for pages with texts in more than one language (such quotations), on
LabeledSectionTransclusion tags, making


as



(T14752 is not related to ProofreadPage extension, but the language trick
can be added on this way as a shortcut for some possible new MediaWiki
parser tags)
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Errare humanum est, perseverare diabolicum

[Luiz Augusto]

On Sun, Nov 29, 2015 at 3:39 PM, Andrea Zanni 
wrote:

> (...)
>
> Unfortunately, for the time being, we hare scattered communities with no
> software support whatsoever: we don't have a Proofread page for
> Right-to-left languages, just imagine how much time it would take to
> redesign a MediaWiki for being a  multilanguage, unique digital library, in
> which anyone can contribute.
> (...)
>

What about two multilanguage Wikisources? One for RTL languages, another
for LTR languages. Or at least one multilanguage Wikisource for languages
based on roman script

It's very disturbing to work on Wikisource if you is interested in a
subject and is able to read in more than one language. On the very specif
subject of "slavery on Brazil" you will find works in Portuguese, Spanish,
English, French, German and Latin, with at least 90% of them never
translated to another language.

Also is very annoying to create thousands of Author pages to simply show
snippets of biographical data for persons mentioned in a given work, since
any regular research work (current or ancient) *will* refer to works in
more than one language; most of those persons don't have any work
translated to your language, PD-old or copyrighted, but you still will need
to create an Author page if you is interested to help readers to proper
understand a given text.

BTW this need pointed me to create a new local innovation: a template to
point the reader to the Wikisource edition that will have works by a given
person ({{autor-idioma}}). And, to prevent good faith users uploading
copyrighted translations, there's also the need to put an old local
innovation from es.Wikisource (currently adopted in many subdomains,
en.Wikisource including). See the

https://pt.wikisource.org/wiki/Autor:Bonaventure_des_P%C3%A9riers

Not to mention that each subdomain have their own way to sort and store
data on Author namespace, that certainly is the crossing barrier for those
that searchs for a subject on libraries OPACs to never adopt Wikisource as
a search point (eventually going to Wikisource pages thanks to Google
search): they don't have time to be trained on 60 subdomains website
designs to research to find information in a language that they are able to
read (or to translate using a software).

In this current subdomain approach, Wikisource will be able to proper store
only fiction works (since language is the main criteria for adopting a
fiction work to read), but never non-fiction works (neither non-fiction
works that describes fiction works: the world was culturally globalized
centuries ago).
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Wikimedia Digitization User Group

[Luiz Augusto]

FYI,
https://meta.wikimedia.org/wiki/Wikimedia_Digitization_User_Group
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Better way to validate pages

[Luiz Augusto]

("Didn't read the entire thread; too long" warning)

I must agree with PL folks: the BGB isn't an improvement. Probably the OCR
quality is great on English, Italian and French for doing such thing, but
it certainly isn't also for Portuguese (PT).

A good improvement will be if a Yellow Big Button wold be implemented.
Maybe you don't find it useful, as many pages are reviewed on creation, but
it is because we, experienced users, do it in this way.

Simply putting an Index page or an external link to get the digitization is
the worst thing we currently do.

Why not our bots starts extracting all and every pages, to make Page
namespace working in similar way that Google Book Search works (you can
choose if you need to browse on image view or OCR view on that platform).
If a random Internet user goes to Wikisource after doing a Web search due
to the correct recognized portion of text (as he go to GBS), he can start
immediately to fix the OCR and, voila! A new user just discovered an
ancient text and a promising website that collects ancient texts!

This approach makes sense on attracting new user and presenting how to work
on Wikisource, and not downgrading our compromise to flag pages fully
reviewed.

Side note: Portuguese language still is "unstable" on orthography and how
to spell words. From time to time we change our conventions (Brazil and
Portugal are yet implementing the Acordo Ortográfico de 1990 and some are
arguing on a new one change). PD-old digitizations came in A VERY OLD
ORTHOGRAPHY CONVENTION. Creating the Big Green Button will make us unable
to do a last check if the wikitext follows the way that words are on
digitization or in the current way of writing. So, it isn't an improvement,
only a trouble finding.

[[User:555]]
Em 11/08/2015 7:09 PM, "Alex Brollo"  escreveu:

> Rough but running code of BGB is ready, and Andrea can test it to find
> bugs and/or drawbacks by now, if he likes.
>
> To lower the risk of a nonsense-click, BGB should pop out after some
> reasonable delay - something less than the time needed to carefully compare
> the page  text and its image. To make simpler to monitor its use, a
> standard message could be added to edit, so that BGB edits could be fastly
> selected in RecentChanges.
>
> Alex
>
>
>
>
> 2015-08-11 21:21 GMT+02:00 Nicolas VIGNERON :
>
>> 2015-08-11 20:39 GMT+02:00 Wiera Lee :
>> >
>> > On pl.wikisource each correction level means that another person did
>> the correction again. The green status means the page was corrected three
>> times by three another persons.
>>
>> The colours are just for marking the status page, it's not per se a
>> correction and only two people are actually needed ; but yes, it's the more
>> or less the same on each wikisource with the proofred system.
>>
>> > Corrected, not read.
>>
>> Uh? Correcting without reading?
>>
>> > In my opinion Big Green Button Correction is useless. New users can
>> click only for stats, not for proofreading. And nobody would check it
>> again, because the book would be finished.
>>
>> Please dont bite the new users or imagine that they're all evil. Maybe
>> you had a bad experience on plwiki but that's not always true.
>>
>> Think about it: When you were new users, did you edit only for stats?
>>
>> I check *a lot* the green pages since *sometimes* there is still little
>> correction to do (a new and better templates, some strange typo like «
>> wo­rd » - with invisible hyphen - or « wоrd » - with a cyrillic о - instead
>> of « word », ).
>>
>> > We are asking new users to validate the pages for the second time (from
>> red to yellow level): new users can learn how the templates and raw codes
>> are working, but when they do something wrong, an experienced user would
>> check it one more time -- to make it green. If they would not edit the
>> page, they would never know how the templates works. So they would not
>> become a better editors...
>>
>> Can't they do both?
>>
>> And should we really make the life of users (new and old) hard when it's
>> not needed ?
>>
>> > We all can do only red pages, why not. We'll get a "perfectly readable
>> and functional book" with some errors. But should we give its the same
>> status as a proof-read three times book? Green status means "almost
>> perfect". We shouldn't make green pages automatically, only to make our
>> stats better.
>>
>> No, only red pages is not "perfectly readable and functional book.
>>
>> How many is « almost » perfect? 80%? 90% 95%? 99%? that's a tricky
>> question.
>> And if a book made of 500 yellow pages already at 99% perfect, isn't the
>> BGB usefull?
>>
>> > Correction without correction is not a good idea. It's a lie.
>>
>> Very true but the BGB is not about correction, it's about marking as
>> correct something that already is.
>>
>> Cdlt, ~nicolas
>>
>> ___
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
>>
>

Re: [Wikisource-l] Gadgets broken around the place & js errors

[Luiz Augusto]

Don't know if it's related but I've just noticed that "proofread tools"
section have disappeared from enhanced toolbar on some subdomains (pt,fr)
but it's still working at en.

Any thoughts?

On Fri, Aug 7, 2015 at 9:24 AM, billinghurst 
wrote:

> Following reports of gadgets being broken and javascript errors I have had
> to do some editing on enWS at
>   https://en.wikisource.org/wiki/MediaWiki:Gadgets-definition
> and to note that I did similar at Meta.
>
> I have basically made every gadget utilise ResourceLoader. Whether it is
> right or wrong, it has stopped the errors.
>
> I am told that the OCR tool button and the horizontal layout button have
> disappeared, and I think that might be for the new toolbar, I have no issue
> in the old toolbar. More info will come if anything comes to light.
>
> Regards, Billinghurst
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] VIAF aligning to Wikidata is helpful for Wikisource

[Luiz Augusto]

There isn't reason to celebrate, unfortunately.

The blog post mentions only Wikipedia links. And, in fact, doing a search
on test.viaf.org, you will get only records containing links to Wikipedia.

See for example the JSON formated record for Jane Austen:

http://rdap02pxdu.dev.oclc.org:8080/viaf/102333412/justlinks.json

Wikidata entry for Jane Austen points also to 1 Wikibooks page, 22
Wikiquote pages, & Wikisource pages and 1 Wikimedia Commons page.

https://www.wikidata.org/wiki/Q36322

I'm not particularly surprised on this, since the Wikimedia Foundation
never does nothing to help "sister" projects (in fact, only puts dozens of
barriers to allow/approve changes in MediaWiki for those and, recently,
started to put barriers to approve local chapters actions on non-Wikipedias
wikis, as we can see on some past messages on this list).

[[User:555]]

On Sat, Mar 28, 2015 at 9:18 PM, billinghurst 
wrote:

> From the Wikidata weekly newsletter, I was led to the VIAF blog
> post[1] which talks about how VIAF is going to re-orientate their
> linking from English Wikipedia to Wikidata. This should have a
> positive effect for the Wikisources in general, and non-English WSes
> especially, in making more overt the authors that you have in your
> wikis.
>
> We should also be aware of the issue that (more?) people will arrive
> at our pages directly via WD.
>
> [http://outgoing.typepad.com/outgoing/2015/03/moving-to-wikidata.html]
>
> Regards, Andrew
> PS. Some of the more WD-aligned personnel will presumably already know
> this.
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] facebook.com/Wikisource

[Luiz Augusto]

Hi,

Please take a look at
https://en.wikisource.org/wiki/Wikisource:Scriptorium#facebook.com.2FWikisource
and share your views, if possible

Many thanks,
Luiz
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Creating an OPDS feed for Wikisource (was Re: [KIWIX][GUTENBERG] 50.000 public domain books available to everybody, everywhere, offline)

[Luiz Augusto]

On Wed, Nov 19, 2014 at 10:18 AM, Emmanuel Engelhart 
wrote:

> [...]
>
> We also plan to use this code base to aggregate other online PD/free books
> libraries. Wikisource is one of the first we would love to add, this might
> be done pretty easily as soon as an OPDS feed is available.
>
> How we can develop an OPDS feed for Wikisource?

Maybe this is the big chance to us start to ignore some misunderstandings
that we've inherited from Wikipedia ("local communities autonomy") and
remember that in the Libraries world standardization of practices is a big
plus?

I mean specially on ways to deliver to users contents by subject or author
despite it's language of production...
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikisource 11th Anniversary Contest

[Luiz Augusto]

On Mon, Nov 3, 2014 at 9:39 AM, Carles Paredes Lanau <
carlespare...@gmail.com> wrote:

> (...) Digitalitzations come from google books, but they were free access
> (it doesn't mean no cost) only with USA IPs. In addition, they were hard to
> access because metada was wrong and different books were displayed in a
> same file. We didn't find 3 books, but we are seeking them in libraries.
> Almost all books are poetry book, but some editions include theatre and
> novel. We know that our scope is too ambicious, but we expect that almost
> all editings will be in no more than ten books.
>
Have you tried HathiTrust ? [1] [2]

In short, some libraries that have allowed Google to digitize their books
realized the big mess that was done on metadata an scan quality and managed
to create a kinda of fork with very powerful search capabilities plus a
feedback space that you can request to re-digitize some books.

They restrict the download in the very same way as Google Book Search does
regarding year of publication and USA IP address. But using a third part
download manager [3] you can get scans in JPEG/PNG up to "400%" resolution,
what makes the OCR quality and DjVu generation very improved.

I personally download from them using a Virtual Machine with a Hotspot
Shield [4] installation, that provides me a IP from USA.

If you or someone else needs, I will be glad to generate/regenerate DjVus
for those titles (ATM I've generated few dozens to pt.wikisource, but I'm
uploading those very slowly most to personal laziness xD )

[1] - http://www.hathitrust.org/
[2] - https://en.wikipedia.org/wiki/HathiTrust
[3] -
http://qt-apps.org/content/show.php/Hathi+Download+Helper?content=158702
[4] - http://www.hotspotshield.com/
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Scanner purchase

[Luiz Augusto]

You'll certainly be interested on what Wikimedia Argentina is doing with
DIY Book Scanners [1].

They tried to submit a Wikimania presentation, but the team behind it's
organization simply refused the paper with no further details (sigh). At
least, you can check some interesting infos both on [2] and [3].

I'm CC'ing Evelin. She is the person behind this successful approach.

Best,
[[m:User:555]]



[1] -
https://meta.wikimedia.org/wiki/Wikimedia_Argentina/Reportes/2014-02#New_scanner_at_our_office

[2] -
https://wikimania2014.wikimedia.org/wiki/Submissions/Open_hardware_and_Open_Source_for_Open_Content:_GLAM,_the_DIY_Book_Scanner_community_and_Wikimedia_digitalize_public_domain_books._Case_study_from_Argentina

[3] -
https://wikimania2014.wikimedia.org/wiki/Talk:Submissions/Open_hardware_and_Open_Source_for_Open_Content:_GLAM,_the_DIY_Book_Scanner_community_and_Wikimedia_digitalize_public_domain_books._Case_study_from_Argentina



On Sat, Sep 6, 2014 at 1:58 PM, Pierre-Yves Beaudouin <
pierre.beaudo...@gmail.com> wrote:

> Hi Carles,
>
> Wikimedia France bought a bookscanner in June [1]. It is not yet
> operational but I've tried a similar book scanner. It is easy and very fast
> (>500p/hour).
>
> Pyb
>
> [1] http://www.bookscanner.fr/about-this-bookscanner.html
>
>
> 2014-09-06 18:20 GMT+02:00 Carles Paredes Lanau :
>
>> Hi,
>>
>> Amical Wikimedia is examining the possibility of purchasing a
>> professional scanner for the digitalization of collections in local
>> libraries.
>>
>> I have seen this cheap prototype but I dunno if it's the best option:
>>
>> http://diybookscanner.org/forum/viewtopic.php?f=1&t=1192
>>
>> Have anyone a professional scanner? Any chapter? Have you any
>> recommendation?
>>
>> Regards,
>>
>> Carles
>>
>> ___
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
>>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Custom progress level for Index pages

[Luiz Augusto]

I've tried to create a new progress level for Index pages on pt.wikisource
with no success (new level isn't being displayed on selection menu if I try
to edit an Index page).

I need to do more than those edits to get it working properly?

https://pt.wikisource.org/w/index.php?diff=prev&oldid=278685
https://pt.wikisource.org/w/index.php?diff=prev&oldid=278686
https://pt.wikisource.org/w/index.php?diff=prev&oldid=278702
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] A proposal for "work" pages into wikisource

[Luiz Augusto]

Your idea is very interesting, but how to deal with works made by two or
more authors?

[[WORKTITLE]] pointing to [[NewCustomNS:WORKTITLE]] containing a
{{magicWikidataTemplate}} that automatically embebeds metadata from the
associated [[d:QXXX]] page (including authorship metadata
automagicallybeing set as categories) makes more sense to me.


On Sat, Jul 19, 2014 at 10:20 AM, Alex Brollo  wrote:

> Wikidata property values are effectively retrieved by #property inclusion
> syntax, but it work only when used into the wikisource page directly linked
> to a wikidata element.
>
> An effective management of a  "book" (best, a literary work) needs
> creation of two different elements ("work" and "edition"); ns0 wikisource
> pages can be linked to "edition" wikidata element just as Author: pages are
> linked to author's wikidata element; on the contrary, presently there's no
> wikisource page that could be  linked to "work" wikidata element, so the
> data of the latter can't be retrieved into wikisource by #property
> inclusion syntax.
>
> I'm testing a strange idea: to create wikisource "work" pages as subpages
> of author's page. It seems a nonsense location, but it has a long series of
> advantages and few disadvantages IMHO:
>
> * omonimies decrease sharply;
> * there's a logical and implicit link between author and his works;
> * work pages can be very simply self-categorized as [[Category:Works by
> {{BASEPAGENAME}}]]
> * joining {{#property:...}} and {{subst:#property:...}} codes, such work
> pages both show data and run as templates to access the data from any other
> page.
> * the code can be completely standardized and can be easily
> created/updated by bot, simply posting the same base code into any work
> page, new or old.
>
> Tests are going on working using
> https://it.wikisource.org/wiki/Autore:Silvio_Pellico and its related
> wikidata elements.
>
> Alex brollo
>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] "Google Search and wikisource.org"

[Luiz Augusto]

FYI,

https://meta.wikimedia.org/wiki/Wikimedia_Forum#Google_Search_and_wikisource.org
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Commons-l] Evacuation

[Luiz Augusto]

A tool to move/copy files from Commons to local wikis
-- Mensagem encaminhada --
De: "Magnus Manske" 
Data: 03/07/2014 17:48
Assunto: [Commons-l] Evacuation
Para: "Wikimedia Commons Discussion List" 
Cc:

An attempt to alleviate the tensions caused by file deletions on Commons:

http://magnusmanske.de/wordpress/?p=218

___
Commons-l mailing list
common...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/commons-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikimedia-l] The Wikipedia Library: New Free Accounts Available

[Luiz Augusto]

Em 19/06/2014 20:03, "Federico Leva (Nemo)"  escreveu:
>
> Luiz Augusto, 20/06/2014 00:23:
>
>> May will be useful also to found some PD-old scans to proofread?
>
>
> What? Is there some JSTOR PD document not yet uploaded to archive.org? ;-)
>

On my last check, this entire collection was missing:

http://about.jstor.org/content/19th-century-british-pamphlets

:P
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikimedia-l] The Wikipedia Library: New Free Accounts Available

[Luiz Augusto]

May will be useful also to found some PD-old scans to proofread?

-- Forwarded message --
From: Jake Orlowitz 
Date: Thu, Jun 19, 2014 at 6:00 PM
Subject: [Wikimedia-l] The Wikipedia Library: New Free Accounts Available
To: Wikimedia & Libraries , North American
Cultural Partnerships ,
cultural-partn...@wikimedia.ch, wikimedi...@lists.wikimedia.org


The Wikipedia Library has new, free research account signups available:

New
* British Newspaper Archive  (50 accounts)
* Keesing's World News Archive  (25 accounts)

Expanded
* Credo Reference  (200 new accounts)
* JSTOR!!  (400 new accounts).

Medical
* BMJ  (25 accounts)
* Cochrane Library  (100 accounts)

Other
*Questia Online Library 
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Subpages on Wikidata

[Luiz Augusto]

On Sat, Jun 14, 2014 at 4:15 AM, Luiz Augusto  wrote:

>
> "The Game" is really very funny to play and, unlike most online games, it
> results in some useful actions (defining if a page is about a person, their
> gender, their birth and death dates, their country of citizenship and their
> most relevant image/media). Perhaps requesting to it's developer to allow
> to set not only languages but also prefered projects to work on, will help
> us?
>
> [1] - https://tools.wmflabs.org/wikidata-todo/creator.html
>


FIY I've already suggested it, on

https://bitbucket.org/magnusmanske/wikidata-game/issue/117/allow-to-set-prefered-wikimedia-projects

"The Game" currently have tons of bug reports and features request. If you
think that this idea will be helpfull, please "vote" on the mentioned page.
It will require an account on bitbucket, but a new can be easily created
with two clicks if you owns a Google account (Gmail and so on).
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Subpages on Wikidata

[Luiz Augusto]

On Sat, Jun 14, 2014 at 2:29 AM, billinghurst 
wrote:

>
> Personally, I am more concerned with the likes of
>   https://en.wikisource.org/w/index.php?title=Special:UnconnectedPages
> and more particularly
>
>
> https://en.wikisource.org/w/index.php?title=Special:UnconnectedPages&page=Author:-
>
> (Noting that at enWS, I have inbuilt a couple of placeholders to namespace
> utilising [[Mediawiki:wikibase-unconnectedpages-summary]])
>
> I try to pick of one of those authors properly each day.


Days ago I've created ~300 Author pages from en.wikisource on Wikidata,
using [1].

"The Game" is really very funny to play and, unlike most online games, it
results in some useful actions (defining if a page is about a person, their
gender, their birth and death dates, their country of citizenship and their
most relevant image/media). Perhaps requesting to it's developer to allow
to set not only languages but also prefered projects to work on, will help
us?

[1] - https://tools.wmflabs.org/wikidata-todo/creator.html
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Subpages on Wikidata

[Luiz Augusto]

On Sat, Jun 14, 2014 at 2:29 AM, billinghurst 
wrote:

>
> If "the game" is presenting pages that it shouldn't, then it needs its
> rules refined for the WSes


"The Game" was presenting such pages due to their default behaviour:

- display a page with no P31 ("instance of") values defined. The user must
choose between "Person", "Not sure" or "Not a person"
- If "Person" is picked, the page on Wikidata is edited and "P31: Q5"
(instance of: person) is added to the page;
- If "Not sure" is picked, the page is skiped;
- If "Not a person" is picked, the page is skiped and removed from the
internal list of pages to check

It was very common to such pages being displayed for me because I've
changed my "prefer languages" to "pt, es, ca, it, gl". It was very boring
and, since the real intention of "The Game" is to fulfill Wikidata with
some kind of initial data, I've created a workaround to remove such pages
from "The Game": setting an "instance of" thought a set of scripts [1] [2].

I was initially working on a title basis (if "The Game" displays "Book
title: 098", I'll look on es.wikisource to get the main work category,
generally, Categoría:Book_title), but later I've done some research on
es.wikisource and found [[Categoría:Subpáginas
]] and added
my instance of-workaround to the pages already created on Wikidata (luckily
a very minor amount).

But even at the end of this workaround run I was still able to found some
pages, mostly because their book_title-category wasn't still created on
es.wikisource, or because the category wasn't on Subpáginas tree. I've
managed to add my workaround also for those, but possibly there's still
some pages without it at some place on Wikidata.

[1] https://tools.wmflabs.org/bene/itemsbycat/ +
https://tools.wmflabs.org/wikidata-todo/autolist2.php

[2] - Random sample:
https://www.wikidata.org/w/index.php?title=Q15893114&diff=137555158&oldid=114016434
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Subpages on Wikidata

[Luiz Augusto]

I don't recall what is the current stage of consensus regarding Wikisource
subpages on Wikidata, but because while playing "The Game" [1] I keep
getting this kind of item (mostly from es.wikisource), I've managed a way
to at least track those stuff [2]

I didn't did an exhaustive search for such items and I keep finding new,
but at this momment it returns 2k of items.

[1] - https://tools.wmflabs.org/wikidata-game/

[2] -
http://tools.wmflabs.org/wikidata-todo/autolist.html?q=CLAIM%5B31%3A17152355%5D
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Wikisource core feature is broken for more than 50 hours

[Luiz Augusto]

So sorry for the cross-posting and for this shout for help that some can
read as a forum shopping, but this is really annoying.

https://bugzilla.wikimedia.org/show_bug.cgi?id=64622

In short, we on all Wikisource wikis are unable to start working on new
pages from digitized books (or for newly overwritten uploads) without
poking the server N times in order to generate a single resized image.

Please fix it ASAP. Please see also #c18 on the mentioned bug.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Community logo for Wikisource

[Luiz Augusto]

Hi all,

I and [[User:Danilo.mac]] ve created some proposals of community logos, as
in the same spirit the Wikimedia Community logo was created years ago.

You are free to use, fork or simply ignore their existence =)

(BTW Dear Wikimedia Foundation, please don't trademark those logos as
you've tried to do at the Wikimedia Community one.)

https://commons.wikimedia.org/wiki/File:Wikisource_Community_Logo_globe_notext.svg


https://commons.wikimedia.org/wiki/File:Wikisource_Community_Logo_globe_text.svg

https://commons.wikimedia.org/wiki/File:Wikisource_Community_Logo_scroll_notext.svg

Best,
Luiz
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikimediaindia-l] Fwd: Re: Gujarati Wikisource - completes 50 books

[Luiz Augusto]

Congratulations!

I've just found
https://wikisource.org/wiki/Category:Gujarati
, a very large category on "oldwikisource".

All those pages have been imported into gu.wikisource?


On Fri, Mar 28, 2014 at 12:20 AM, John Mark Vandenberg wrote:

>
>
> -- Forwarded message --
> From: Vishnu 
> Date: Thu, Mar 27, 2014 at 11:22 PM
> Subject: [Wikimediaindia-l] Fwd: Re: Gujarati Wikisource - completes 50
> books
> To: Wikimedia India Community list 
>
>
>  Please see the below email from Sushant Savla.
>
> Congratulations to Sushant and other Gujarati Wikimedians for their
> efforts in achieving this milestone!!
>
> Best,
> Vishnu
>
>   Original Message   Subject: Re: Gujarati Wikisource -
> completes 50 books  Date: 27 Mar 2014 15:01:24 -  From: sushant savla
>To:
>  
>
>
> Dear Vishnu,
>
> this is in continuation to our telecon regarding i am not able to get my
> name registered in Wikimedia India list hence writing this email to you.
>
> Gujarati Wikisource has achieved yet another milestone on its second
> birthday (29.03.2014) completed uploading full 50 books which has come in
> public domain.
>
> The collection of these 50 books includes well known Gujarati literary
> creations in the form of Autobiography, Novels, Plays, Collection of Poems,
> Essays, Moral Stories etc. This includes works of prominent writers such as
> Mahatma Gandhi, Zaverchand Meghani, Kavi Nhanalal, Surasinhji Gohil,
> Educationist Gijubhai Badheka, Kavi Dalapatram, Ramanlal Nilkanth etc.
>
> This feat was achieved in 2 years time.
>
> As OCR is not available, volunteers of Gujarati wiki Community have typed
> this books. The community proceeds in a planned manner. A book is selected
> and its announcement is made at common platform on source. Volunteer
> interested joins the project. Chapters are distributed among the particants
> and proof reading is done. Once completed, another book is undertaken.
>
> Kindly inform this on Indian Community List
>
> Regards
>
> Sushant
>
>
>
> ___
> Wikimediaindia-l mailing list
> wikimediaindi...@lists.wikimedia.org
> To unsubscribe from the list / change mailing preferences visit
> https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
>
>
>
>
> --
> John Vandenberg
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Preservation Week

[Luiz Augusto]

>From 27 April to 3 May many GLAM institutions will be holding events for
the Preservation Week [1]:

"ALA [American Library Association] encourages libraries and other
institutions to use Preservation Week to connect our communities through
events, activities, and resources that highlight what we can do,
individually and together, to preserve our personal and shared collections."

This is a kind of event that IMHO Wikisource communities should take part.

Is anyone interested? A well designed + written page on oldwikisource (or
in subdomains) can help both to promote Wikisource at Wikimedia level and
in GLAM institutions level.

We have one month left!

[1] - https://www.facebook.com/preservationweek/ ,
http://www.ala.org/preservationweek
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Requests for comment/Standardize ProofreadPage namespaces across Wikisources

[Luiz Augusto]

FYI,

[[User:Ricordisamoa]] started the RfC available at
https://meta.wikimedia.org/wiki/Requests_for_comment/Standardize_ProofreadPage_namespaces_across_Wikisources
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikimedia-l] Press Release: Wikimedia Indonesia Receive Grant from The Ford Foundation to Preserve Indonesian Culture By Content Digitalization

[Luiz Augusto]

Wikisource specific info at

http://wikimedia.or.id/wiki/Proyek_Penciptaan_dan_Digitalisasi_Konten/Rencana_Anggaran

-- Forwarded message --
From: Isabella Apriyana 
Date: Tue, Mar 4, 2014 at 10:56 AM
Subject: [Wikimedia-l] Press Release: Wikimedia Indonesia Receive Grant
from The Ford Foundation to Preserve Indonesian Culture By Content
Digitalization
To: wikimedi...@lists.wikimedia.org


Hello all,

We are happy to announce that Wikimedia Indonesia is awarded a grant by The
Ford Foundation to support our projects on Indonesian content
digitalization. Please find below the official press release. Thank you.


*Press Release*
To be distributedJakarta, 3 March 2014


*Wikimedia Indonesia Receive Grant from The Ford Foundation to Preserve
Indonesian Culture By Content Digitalization*



Wikimedia Indonesia, an independent association established by Indonesian
Language Wikipedia volunteers, has received a grant from The Ford
Foundation for two separate programs that will be carried through 2014 and
2015. This follows the successful completion of the first grant from Ford
Foundation to Wikimedia Indonesia awarded in 2011 to support Creative
Commons Indonesia  and Cipta Media
Bersama from
2011-2013.

The first program is to Preserve Indonesian Culture by Content
Digitalization, an effort supported by the Indonesian Coordinating Ministry
for People's Welfare under PNPM Pusaka program, and coordinated under SAPA
(Stratetic Alliance for Poverty Alleviation).

The project has a budget of USD 125,000 (1,4 billion rupiah) to be used by
Wikimedia Indonesia for the following wikimedia projects:

   1. Indonesian Wikipedia (Free Your Knowledge
2014 in
   Jakarta, Bandung, and Yogyakarta)
   2. Javanese Wikipedia (Semarang, Yogyakarta, and Solo)
   3. Sundanese Wikipedia (Bandung)
   4. Banjar Wikipedia (Samarinda and Banjarmasin)
   5. Minankabau Wikipedia (Pekanbaru)
   6. Digitalization of Indonesian content for the Wikisource project
   (online)

Ten universities from Jakarta, Bandung, and Yogyakarta have signed up to
participate in Free Your Knowledge 2014, Indonesian Wikipedia writing
competition, which will commence in March 2014. The other wikimedia
projects will commence in mid 2014.

The second program is Cipta Media Seluler , a joint
effort between Wikimedia Indonesia, ICT Watch, Independent Journalist
Alliance Indonesia, and Ford Foundation with the total value of USD 750,000
to fund cellular initiatives with social justice goals via open call for
proposals.


** * END * **

   - For more information, please contact Ivonne
Kristiani,
   Secretary General of Wikimedia Indonesia at info[image:
px]
   wikimedia.or.id.


--
*Isabella Apriyana*
*Wakil Sekretaris Jendral 2013-2015*
*Deputy Secretary General 2013-2015*
*Wikimedia Indonesia*
Seluler (Ph.) +628889752858
Surel (E-mail) isabella.apriy...@wikimedia.or.id


Dukung upaya kami membebaskan pengetahuan
http://wikimedia.or.id/wiki/Wikimedia_Indonesia:Donasi
___
Wikimedia-l mailing list
wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] RfC: Creation of a Global Wikimedia Commons

[Luiz Augusto]

Hi all,

I've just created a RfC related to the recent open letters from some local
chapters.

Please see my reasoning and focus debate on that proposal in the specific
page:

https://meta.wikimedia.org/wiki/Requests_for_comment/Creation_of_a_Global_Wikimedia_Commons

Best,
[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Bug 57813] Google Books > Internet Archive > Commons upload cycle

[Luiz Augusto]

FYI \o/
Em 03/03/2014 15:13,  escreveu:

>  Rohit Dua <8ohit@gmail.com> changed bug 
> 57813
>  What Removed Added  CC   8ohit@gmail.com
>
>  *Comment # 2 
> on bug 57813  from
> Rohit Dua <8ohit@gmail.com> *
>
> (In reply to vladjohn2013 from comment #0 
> )> Google Books > 
> Internet Archive > Commons upload cycle
> >
> > Wikisources all around the world use heavily GB digitizations for
> > transcription and proofreading. As GB provides just the PDF, the usual cycle
> > is:
> >
> > go to Google Books and look for a book
> > check if the book is already in IA
> > if it's not, upload it there
> > get the djvu from IA
> > upload it on Commons
> > use it on Wikisource
> >
> > For point 4, we have this awesome tool:
> > https://toolserver.org/~tpt/iaUploadBot/step1.php What we miss right now is
> > a tool for point 2.1, that would serve many other users outside the
> > Wikimedia movement too. Eventually, we could think of a bot/script which
> > would do all the work altogether, notifying the user when their help is
> > needed (eg metadata polishing, Commons categories, etc.) Mentors: Aubrey is
> > available for "design" mentorship, paired with a technical expert. We can
> > maybe ask help from a IA expert.
> >
> > URL:https://www.mediawiki.org/wiki/Mentorship_programs/
> > Possible_projects#Google_Books_.3E_Internet_Archive_.3E_Commons_upload_cycle
>
>
> Hi
>
> This is to inform that I am working on Bug 57813 
>  - Google Books > 
> Internet
> Archive > Commons upload cycle, via GSOC-2014 project.
> I'm ready with with the outline of google-books download script.
>
> --
> Rohit Dua
> 8ohit.dua
> New Delhi,India
>
>  --
> You are receiving this mail because:
>
>- You voted for the bug.
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Commons and URAA

[Luiz Augusto]

Wikipedia Signpost coverage [1], with mention to some updates [2], [3]

[1] -
https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2014-02-26/News_and_notes

[2] -
https://meta.wikimedia.org/wiki/Legal_and_Community_Advocacy/Wikimedia_Server_Location_and_Free_Knowledge

[3] -
https://commons.wikimedia.org/wiki/Commons:Massive_restoration_of_deleted_images_by_the_URAA


On Tue, Feb 25, 2014 at 12:46 AM, Luiz Augusto  wrote:

> Days ago Jan-Bart de Vreede, Chair from Wikimedia Foundation Board of
> Trustees answered the original letter from Wikimedia Israel:
>
>
> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA#Response_from_Wikimedia_Foundation_Board_of_Trustees
>
> Now Wikimedia Argentina just sent their open letter too:
>
>
> https://meta.wikimedia.org/wiki/Wikimedia_Argentina/Open_letter_regarding_URAA
>
>
> On Wed, Feb 19, 2014 at 9:36 PM, Luiz Augusto  wrote:
>
>> Wikimedia España just published a similar letter:
>>
>>
>> https://meta.wikimedia.org/wiki/Wikimedia_España/Letter_to_the_BoT_regarding_URAA
>>
>>
>> On Tue, Jan 28, 2014 at 8:24 AM, Andrea Zanni 
>> wrote:
>>
>>> Folks from Wikimedia Israel wrote to the board for a problem with the
>>> URAA and Commons.
>>> I also wrote in the talk page to assert that Commons problem is also
>>> Wikisource problem,
>>> and we would really benefit from a solution
>>>
>>> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA
>>>
>>> Aubrey
>>>
>>> ___
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>>
>>>
>>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Commons and URAA

[Luiz Augusto]

Days ago Jan-Bart de Vreede, Chair from Wikimedia Foundation Board of
Trustees answered the original letter from Wikimedia Israel:

https://meta.wikimedia.org/wiki/Talk:Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA#Response_from_Wikimedia_Foundation_Board_of_Trustees

Now Wikimedia Argentina just sent their open letter too:

https://meta.wikimedia.org/wiki/Wikimedia_Argentina/Open_letter_regarding_URAA


On Wed, Feb 19, 2014 at 9:36 PM, Luiz Augusto  wrote:

> Wikimedia España just published a similar letter:
>
>
> https://meta.wikimedia.org/wiki/Wikimedia_España/Letter_to_the_BoT_regarding_URAA
>
>
> On Tue, Jan 28, 2014 at 8:24 AM, Andrea Zanni wrote:
>
>> Folks from Wikimedia Israel wrote to the board for a problem with the
>> URAA and Commons.
>> I also wrote in the talk page to assert that Commons problem is also
>> Wikisource problem,
>> and we would really benefit from a solution
>>
>> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA
>>
>> Aubrey
>>
>> ___
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
>>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] ProofreadPage documentation

[Luiz Augusto]

I've started it on [1].

It's unfortunate that due to licensing issues (ns:Help is CC0 on
mediawiki.org wiki) we can't transwiki some existing pages from
Wikisources. So, specially because it, a lot of help is needed.

While writing those initial pages I just realized that there is no guide to
help new subdomain wikis (or some already created) to learn our very
specific topics (copyright and public domain issues, how to research for
digitizations, scans quality issues etc), only the specific help pages on
each subdomain.

In my view this will be helpful not only for those new or small
Wikisources, but also for subdomain coordination. The [2] is messy and
almost unmanageable...

Is anyone interested to work on it?

[1] - https://www.mediawiki.org/wiki/Help:Extension:ProofreadPage
[2] - https://wikisource.org/wiki/Wikisource:Subdomain_coordination


On Thu, Feb 20, 2014 at 10:43 AM, Thomas Tanon  wrote:

> Hi!
>
> The ProofreadPage lack of documentation is a real problem since the
> creation of the extension. For example, I discovered in 2012 that some
> en.wikisource administrators didn't know the very useful header=1 parameter
> of the  tag.
>
> Currently the installation and configuration documentation is stored on
> the extension page on MediaWiki.org [1]. But, about the user documentation
> (parameters of  tag...) there is no authoritative source, only some
> partial pages on oldWikisource and on help pages of language based wikis.
>
> I really believe that this big issue should be fix. I think the best way
> to do it is to create a central documentation page for end users in the
> Help namespace of MediaWiki.org, that would document all the features of
> the ProofreadPage extension and be updated when things change in the
> extensions. It would be written in English and then translated in the same
> place using the Translate extension, so all Wikisources should be able to
> replace their own partial documentation with this centralized version.
>
> But, because of my lack of free time, I don't feel able to archive this
> goal alone. Is there someone ready to start the work by collecting data
> disseminated on oldWikisource and one some language based Wikisource and
> start this page [3]? I'm ready to help for the not documented yet parts. It
> doesn't requires technical skills, only a knowledge on how to use
> ProofreadPage. So I think that any experienced Wikisource contributor is
> able to do it.
>
> Many thanks to the person that will do it, who will have the eternal
> gratitude of the Wikisource community.
>
> Thomas
>
> [1] https://www.mediawiki.org/wiki/Extension:Proofread_Page
> [2] https://wikisource.org/wiki/Wikisource:ProofreadPage
> [3] https://www.mediawiki.org/wiki/Help:Extension:ProofreadPage
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Special:ProofreadIndexOai

[Luiz Augusto]

Hi, Billinghurst,

I think that you have misunderstood the mentioned special page.

The Oai portion on [[Special:ProofreadIndexOai]] reffers to OAI-PMH (Open
Archives Initiative Protocol for Metadata Harvesting), not OAuth =)


On Thu, Feb 20, 2014 at 2:26 AM, billinghurst wrote:

> Luiz,
>
> I don't see it listed at
>   https://www.mediawiki.org/wiki/Special:OAuthListConsumers
> which is where all approved clients are listed at this time (though the
> plan is to move the process to meta at some point).
>
> Regards, Billinghurst
>
>
>
> On Wed, 19 Feb 2014 18:54:18 -0300, Luiz Augusto 
> wrote:
> > I've just found [[Special:ProofreadIndexOai]] and loved it!
> >
> > Firstly, why this special page isn't listed at [[Special:SpecialPages]]?
> >
> > Second, [1] points to [2], that returns a 404 error.
> >
> > Oka, now I'll ask the most important thing: how to implement it!? =)
> >
> > The doc page [3] mentions a page stored in the MediaWiki namespace, but
> > that page is almost empty on it.wikisource and don't ever was created on
> > en.wikisource. Those domains contains DC fields such as title, creator,
> > issued.
> >
> > The MediaWiki page was also ever created on pt.wikisource, but all
> metadata
> > that it returns to me is type and format.
> >
> > 
> > As a side note, I really love all efforts done in ProofreadPage
> extension.
> > It's amazing that a plugin developed entirely in a volunteer basis, with
> > little or none input from the main product (MediaWiki) developer team,
> has
> > achieved such level of quality and complexity.
> >
> > But, please, give some love and attention to maintain it's
> documentation.
> > Do it remembering that it will be crucial for small Wikisources, since
> most
> > of the time only one or two users retains all the very specific
> knowledge
> > necessary to try to develop and atract new users for that subdomain.
> >
> > Reverse engineering to discover how something works is a time consuming
> > task, like all the remaining core tasks. At the end, those local experts
> > users ends in getting no fun contributing to Wikisource because firstly
> > needs to do lots of additional and sometimes bureaucratic work if really
> > wants to not being the only user in such wiki.
> >
> > We all are in the same boat, trying to colect works in copyleft or
> public
> > domain in a project that the main organization behind we (Wikimedia
> > Foundation) neither try to help us or know how to help us (in fact,
> mostly
> > of us, myself included, don't know also on what can be helped), please
> help
> > each other on what is possible.
> >
> > [what a melodramatic message I just wrote LOL]
> >
> > 
> >
> > [1] -
> >
>
> https://wikisource.org/wiki/Special:ProofreadIndexOai?verb=ListRecords&metadataPrefix=prp_qdc
> >
> > [2] - http://mediawiki.org/xml/proofreadpage/qdc/
> >
> > [3] - https://www.mediawiki.org/wiki/Extension:Proofread_Page#OAI-PMH
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Commons and URAA

[Luiz Augusto]

Wikimedia España just published a similar letter:

https://meta.wikimedia.org/wiki/Wikimedia_España/Letter_to_the_BoT_regarding_URAA


On Tue, Jan 28, 2014 at 8:24 AM, Andrea Zanni wrote:

> Folks from Wikimedia Israel wrote to the board for a problem with the URAA
> and Commons.
> I also wrote in the talk page to assert that Commons problem is also
> Wikisource problem,
> and we would really benefit from a solution
>
> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA
>
> Aubrey
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Special:ProofreadIndexOai

[Luiz Augusto]

I've just found [[Special:ProofreadIndexOai]] and loved it!

Firstly, why this special page isn't listed at [[Special:SpecialPages]]?

Second, [1] points to [2], that returns a 404 error.

Oka, now I'll ask the most important thing: how to implement it!? =)

The doc page [3] mentions a page stored in the MediaWiki namespace, but
that page is almost empty on it.wikisource and don't ever was created on
en.wikisource. Those domains contains DC fields such as title, creator,
issued.

The MediaWiki page was also ever created on pt.wikisource, but all metadata
that it returns to me is type and format.


As a side note, I really love all efforts done in ProofreadPage extension.
It's amazing that a plugin developed entirely in a volunteer basis, with
little or none input from the main product (MediaWiki) developer team, has
achieved such level of quality and complexity.

But, please, give some love and attention to maintain it's documentation.
Do it remembering that it will be crucial for small Wikisources, since most
of the time only one or two users retains all the very specific knowledge
necessary to try to develop and atract new users for that subdomain.

Reverse engineering to discover how something works is a time consuming
task, like all the remaining core tasks. At the end, those local experts
users ends in getting no fun contributing to Wikisource because firstly
needs to do lots of additional and sometimes bureaucratic work if really
wants to not being the only user in such wiki.

We all are in the same boat, trying to colect works in copyleft or public
domain in a project that the main organization behind we (Wikimedia
Foundation) neither try to help us or know how to help us (in fact, mostly
of us, myself included, don't know also on what can be helped), please help
each other on what is possible.

[what a melodramatic message I just wrote LOL]



[1] -
https://wikisource.org/wiki/Special:ProofreadIndexOai?verb=ListRecords&metadataPrefix=prp_qdc

[2] - http://mediawiki.org/xml/proofreadpage/qdc/

[3] - https://www.mediawiki.org/wiki/Extension:Proofread_Page#OAI-PMH
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Wikitech-l] The tag to be known as

[Luiz Augusto]

I've just sent two comments on this:

https://bugzilla.wikimedia.org/show_bug.cgi?id=52061#c38

https://bugzilla.wikimedia.org/show_bug.cgi?id=6810#c8


On Mon, Feb 10, 2014 at 1:53 PM, Luiz Augusto  wrote:

>
>
> -- Forwarded message --
> From: This, that and the other 
> Date: Sat, Feb 8, 2014 at 5:00 AM
> Subject: [Wikitech-l] The  tag to be known as 
> To: wikitec...@lists.wikimedia.org
>
>
> For some time, work has been ongoing on a merge of the Poem extension into
> MediaWiki core [1] [2]. (For those not aware, this extension [3] implements
> a simple  tag which, among other things, preserves newlines.)
>
> Several developers have expressed the desire for an alternative name for
> this tag, alongside  (which of course will be kept for backward
> compatibility). This is because the tag is sometimes used for various other
> uses besides poetry.
>
> There were many suggestions (see the bug report [1]), but it was
> eventually agreed to use Michael M.'s suggestion of . This name puts
> the focus on the individual "lines" of the content, which is exactly what
> the tag is doing.
>
> We almost had a collision with a previous proposal ( conflicted
> with a tag in use on Wikia), so we wish to ensure that no-one else is using
> . No-one is yet aware of any MediaWiki extensions or other code
> using a tag named  in wikitext.
>
> If you think the name  will be an issue, or if you have any other
> concerns with this merge, please speak up, either here or at the bug report.
>
> TTO
>
> --
> [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=52061
> [2] https://gerrit.wikimedia.org/r/#/c/106861/
> [3] https://www.mediawiki.org/wiki/Extension:Poem
>
>
> ___
> Wikitech-l mailing list
> wikitec...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikitech-l] The tag to be known as

[Luiz Augusto]

-- Forwarded message --
From: This, that and the other 
Date: Sat, Feb 8, 2014 at 5:00 AM
Subject: [Wikitech-l] The  tag to be known as 
To: wikitec...@lists.wikimedia.org


For some time, work has been ongoing on a merge of the Poem extension into
MediaWiki core [1] [2]. (For those not aware, this extension [3] implements
a simple  tag which, among other things, preserves newlines.)

Several developers have expressed the desire for an alternative name for
this tag, alongside  (which of course will be kept for backward
compatibility). This is because the tag is sometimes used for various other
uses besides poetry.

There were many suggestions (see the bug report [1]), but it was eventually
agreed to use Michael M.'s suggestion of . This name puts the focus
on the individual "lines" of the content, which is exactly what the tag is
doing.

We almost had a collision with a previous proposal ( conflicted
with a tag in use on Wikia), so we wish to ensure that no-one else is using
. No-one is yet aware of any MediaWiki extensions or other code
using a tag named  in wikitext.

If you think the name  will be an issue, or if you have any other
concerns with this merge, please speak up, either here or at the bug report.

TTO

--
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=52061
[2] https://gerrit.wikimedia.org/r/#/c/106861/
[3] https://www.mediawiki.org/wiki/Extension:Poem


___
Wikitech-l mailing list
wikitec...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Language categories on Commons

[Luiz Augusto]

I've started the page discussion
https://wikisource.org/wiki/Wikisource:Language_categories_on_Commons

Any inputs are welcomed.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikimedia-l] A letter from WMIL to the Board of Trustees regarding the deletion of images from Commons under URAA

[Luiz Augusto]

Ooops, didn't looked on my wikisource-l gmail label before fwding the
message. Sorry for duplicating the announce done by Aubrey
Em 30/01/2014 06:00, "Luiz Augusto"  escreveu:

> May be an interesting read for those of us that lives outside the USA and
> curates public domain contents.
> -- Mensagem encaminhada --
> De: "Yael Meron" 
> Data: 28/01/2014 06:52
> Assunto: [Wikimedia-l] A letter from WMIL to the Board of Trustees
> regarding the deletion of images from Commons under URAA
> Para: 
>
> Hi everyone,
>
> Here is a letter I just sent on behalf of the Board of Wikimedia Israel to
> the WMF Board of Trustees, regarding the deletion of images from Commons
> under URAA.
> The letter is also posted on Meta:
>
> https://meta.wikimedia.org/wiki/Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA
>
> We would love to hear your thoughts on this, preferably in the discussion
> page on Meta.
>
> Regards,
>
> Yael Meron
> WMIL Board Member
>
>
> -- Forwarded message --
> Date: Tue, Jan 28, 2014 at 10:36 AM
> Subject: A letter from WMIL regarding the deletion of images from Commons
> under URAA
> To: wmfbo...@wikimedia.org
>
>
> Dear Board of Trustees,
>
> As you might know, there was a discussion on Wikimedia Commons regarding
> the Golan v. Holder copyright case, where the copyright status of a massive
> amount of non-US images was changed from public domain to copyrighted. The
> conclusion of the discussion was that there was indeed a problem with such
> images, but that they would be deleted on a case-by-case basis. The actual
> effect is not only that masses of public domain images be deleted from
> Commons (with the burden of proof lying on the uploader), but also millions
> of PD images waiting to be uploaded to Commons which are now in limbo. This
> will certainly hinder or eliminate many GLAM partnerships around the world
> and, again, deprive Commons of millions of images, many of them
> historically important or iconic.
>
> The reason behind the community decision was that, since Commons' servers
> are located in the United States, all public domain images must
> specifically be in the public domain in the United States, regardless of
> their status in any other country. The Foundation's legal team issued a
> legal position, which did not actually take any position but gave the
> pertinent legal arguments. It is clear however that the community was in
> fact trying to legally protect the Wikimedia Foundation from lawsuits,
> therefore it stands to reason that the Foundation should specifically
> address where it stands on this issue.
> We believe that Wikimedia's position is not just to interpret the current
> legal status, but to act and change it.
>
> In light of this, we implore you to speak out and act in favor of uploading
> public domain images to Commons that are not necessarily PD in the United
> States, whether by allowing it directly, or making other arrangements to
> allow such uploads without risking legal backlash. Millions of images are
> at stake. This is possibly more than the amount of content that would be at
> risk had PIPA/SOPA passed, and the Foundation made its position on
> PIPA/SOPA very clear. It goes without saying that blocking access to public
> domain images on Commons goes against the stated aims of our movement and
> deals a severe blow to its legitimacy.
>
> This is a similar case to PIPA/SOPA, and the Foundation can and should do
> everything in its power to allow the use of these images in the Commons and
> making them available to the public. Clearly the community is starting to
> delete these images reluctantly, thinking it protects the legality of all
> Wikimedia projects, but this only has to be true if the Foundation stands
> on the sidelines. We believe that should the Foundation get involved, as
> with the PIPA/SOPA case, the matter will be resolved quickly.
>
> It should be noted that we the volunteers, both in Israel and in other
> countries, are doing the utmost to obtain official documents that make it
> clear that the relevant images are in the public domain. However, this can
> only be done for images owned by governments. For images owned by
> individuals the process is next to impossible, and is no different from the
> process of asking every individual to release copyright on any image. As we
> are frantically looking for all sorts of solutions, we expect the
> Foundation to act on the behalf of the entire community and by extension,
> the public.
>
> This brought our chapter, as well as other chapters, to rethink about the
> operation of Commons, and to seek alternatives. We may be forced, if this
> issue is 

[Wikisource-l] Fwd: [Wikimedia-l] A letter from WMIL to the Board of Trustees regarding the deletion of images from Commons under URAA

[Luiz Augusto]

May be an interesting read for those of us that lives outside the USA and
curates public domain contents.
-- Mensagem encaminhada --
De: "Yael Meron" 
Data: 28/01/2014 06:52
Assunto: [Wikimedia-l] A letter from WMIL to the Board of Trustees
regarding the deletion of images from Commons under URAA
Para: 

Hi everyone,

Here is a letter I just sent on behalf of the Board of Wikimedia Israel to
the WMF Board of Trustees, regarding the deletion of images from Commons
under URAA.
The letter is also posted on Meta:
https://meta.wikimedia.org/wiki/Wikimedia_Israel/Letter_to_the_BoT_regarding_URAA

We would love to hear your thoughts on this, preferably in the discussion
page on Meta.

Regards,

Yael Meron
WMIL Board Member


-- Forwarded message --
Date: Tue, Jan 28, 2014 at 10:36 AM
Subject: A letter from WMIL regarding the deletion of images from Commons
under URAA
To: wmfbo...@wikimedia.org


Dear Board of Trustees,

As you might know, there was a discussion on Wikimedia Commons regarding
the Golan v. Holder copyright case, where the copyright status of a massive
amount of non-US images was changed from public domain to copyrighted. The
conclusion of the discussion was that there was indeed a problem with such
images, but that they would be deleted on a case-by-case basis. The actual
effect is not only that masses of public domain images be deleted from
Commons (with the burden of proof lying on the uploader), but also millions
of PD images waiting to be uploaded to Commons which are now in limbo. This
will certainly hinder or eliminate many GLAM partnerships around the world
and, again, deprive Commons of millions of images, many of them
historically important or iconic.

The reason behind the community decision was that, since Commons' servers
are located in the United States, all public domain images must
specifically be in the public domain in the United States, regardless of
their status in any other country. The Foundation's legal team issued a
legal position, which did not actually take any position but gave the
pertinent legal arguments. It is clear however that the community was in
fact trying to legally protect the Wikimedia Foundation from lawsuits,
therefore it stands to reason that the Foundation should specifically
address where it stands on this issue.
We believe that Wikimedia's position is not just to interpret the current
legal status, but to act and change it.

In light of this, we implore you to speak out and act in favor of uploading
public domain images to Commons that are not necessarily PD in the United
States, whether by allowing it directly, or making other arrangements to
allow such uploads without risking legal backlash. Millions of images are
at stake. This is possibly more than the amount of content that would be at
risk had PIPA/SOPA passed, and the Foundation made its position on
PIPA/SOPA very clear. It goes without saying that blocking access to public
domain images on Commons goes against the stated aims of our movement and
deals a severe blow to its legitimacy.

This is a similar case to PIPA/SOPA, and the Foundation can and should do
everything in its power to allow the use of these images in the Commons and
making them available to the public. Clearly the community is starting to
delete these images reluctantly, thinking it protects the legality of all
Wikimedia projects, but this only has to be true if the Foundation stands
on the sidelines. We believe that should the Foundation get involved, as
with the PIPA/SOPA case, the matter will be resolved quickly.

It should be noted that we the volunteers, both in Israel and in other
countries, are doing the utmost to obtain official documents that make it
clear that the relevant images are in the public domain. However, this can
only be done for images owned by governments. For images owned by
individuals the process is next to impossible, and is no different from the
process of asking every individual to release copyright on any image. As we
are frantically looking for all sorts of solutions, we expect the
Foundation to act on the behalf of the entire community and by extension,
the public.

This brought our chapter, as well as other chapters, to rethink about the
operation of Commons, and to seek alternatives. We may be forced, if this
issue is not properly addressed by the Foundation, to consider moving the
images to alternative servers located in other countries.

Thank you in advance,
--Wikimedia Israel Board

-
Yael Meron
WMIL Board Member
___
Wikimedia-l mailing list
wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] upload from InternetArchive tool

[Luiz Augusto]

Found a new small issue after your fix: the creator page should be placed
on Creator namespace, not in the main namespace


On Mon, Jan 27, 2014 at 3:58 PM, Thomas Tanon  wrote:

> @Luiz Augusto
> I've just fixed this issue. Thanks for the report.
>
> @Aubrey
> There is already [1] that should be reusable by other wikisources for
> Commons -> Index: importation.
>
> Thomas
>
> [1]https://fr.wikisource.org/wiki/MediaWiki:Gadget-Fill_Index.js
>
> Le 27 janv. 2014 à 15:55, Luiz Augusto  a écrit :
>
> > Found a minor issue while playing with
> https://archive.org/details/dictionnairedarc03rola:
> >
> > text inviting to create an Creator page on Wikimedia Commons is
> displayed as raw text with HTML tags visible
> >
> > BTW many thanks for another great tool!
> >
> >
> > On Mon, Jan 27, 2014 at 9:32 AM, Federico Leva (Nemo) <
> nemow...@gmail.com> wrote:
> > Andrea Zanni, 27/01/2014 10:54:
> >
> > We should improve Help pages then.
> >
> > I think it's kinda easy to create a .zip file from a folder of raw scans
> > with the suffix
> > "_images.zip"
> >
> > You just have to write it crystal clear :-)
> >
> > When I wrote <
> https://en.wikisource.org/wiki/Help:DjVu_files#The_Internet_Archive>,
> things were less easy and we still only have a footnote "You can also try
> the new _images archive format".
> > We can probably add a TL;DR version at top "just upload your scans in a
> PDF or compressed in a file _images.zip" and leave the rest for the cases
> where automatic detection of language or resolution fails etc.
> >
> > Nemo
> >
> >
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> >
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] upload from InternetArchive tool

[Luiz Augusto]

Found a minor issue while playing with
https://archive.org/details/dictionnairedarc03rola:

text inviting to create an Creator page on Wikimedia Commons is displayed
as raw text with HTML tags visible

BTW many thanks for another great tool!


On Mon, Jan 27, 2014 at 9:32 AM, Federico Leva (Nemo) wrote:

> Andrea Zanni, 27/01/2014 10:54:
>
>  We should improve Help pages then.
>>
>> I think it's kinda easy to create a .zip file from a folder of raw scans
>> with the suffix
>> "_images.zip"
>>
>> You just have to write it crystal clear :-)
>>
>
> When I wrote  Internet_Archive>, things were less easy and we still only have a
> footnote "You can also try the new _images archive format".
> We can probably add a TL;DR version at top "just upload your scans in a
> PDF or compressed in a file _images.zip" and leave the rest for the cases
> where automatic detection of language or resolution fails etc.
>
> Nemo
>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Our first IW link solving talk on Wikidata

[Luiz Augusto]

Just found that some are already talking about there:

https://en.wikisource.org/wiki/Wikisource:Scriptorium#Facilitating_interwiki_bots_for_Wikidata_migration

Messages starting at "Another potential error-situation: Two versions on
one Wikisource linking" are especially relevant to IW links like this one
(Bible)


On Wed, Jan 15, 2014 at 11:56 AM, Andrea Zanni wrote:

> You probably need to make much clearer that we need separate items for
> editions.
> We should make the Bible a sort of example, as it has thousands editions
> and translations.
> And we should also write some sort of documentation.
> Should we discuss it here on the ML or there:
> https://www.wikidata.org/wiki/Wikidata_talk:Books_task_force?
>
> Aubrey
>
>
>
> On Wed, Jan 15, 2014 at 2:00 PM, Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il> wrote:
>
>> I am so *un*-surprised about the text in question :)
>>
>>
>> --
>> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
>> http://aharoni.wordpress.com
>> ‪“We're living in pieces,
>> I want to live in peace.” – T. Moore‬
>>
>>
>> 2014/1/15 Luiz Augusto 
>>
>>> https://www.wikidata.org/wiki/Talk:Q1845
>>>
>>> ___
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>>
>>>
>>
>> ___
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
>>
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Our first IW link solving talk on Wikidata

[Luiz Augusto]

https://www.wikidata.org/wiki/Talk:Q1845
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Advocacy Advisors] Blog post about Wikipedia and the public domain

[Luiz Augusto]

BTW it's funny that in 2007 somebody argued to create a fork saying
something like to "Wikimedia don't care with your issue" and this subject
was back to live again by just another lack of attention to non-Wikipedia
wikis... *sigh*


On Fri, Jan 10, 2014 at 7:09 PM, Luiz Augusto  wrote:

> Back in 2007 I've proposed something similar to it, but some argued
> agains't:
>
> http://lists.wikimedia.org/pipermail/commons-l/2007-April/001703.html
>
>
> On Fri, Jan 10, 2014 at 8:14 AM, Andrea Zanni wrote:
>
>> Hi Dmytro,
>> yes, Wikilivres is great, but is yet another website.
>> Wikisource communities are pretty small (compared to Wikipedia ones) and
>> we even have another multilingual Wikisource (oldwikisource), and again
>> another non-WMF multilingual one (Wikilivres)
>> I think it's too much :-)
>> we'd need to coordinate and focus our efforts.
>>
>> My idea is: if we had a *server* with Wikisource content in Canada, for
>> example, we could simply use the normal copyright of the country of the
>> user of the local Wikisource?
>> It's a question, I don't know the answer.
>>
>> But maybe it's worth asking the lawyers.
>>
>> Aubrey
>>
>>
>>
>> On Fri, Jan 10, 2014 at 10:23 AM, Dmytro Dziuma wrote:
>>
>>> Hi Andrea,
>>>
>>> Don't we have Wikilivres for that? Ideally it would be great if it was
>>> operated by WMF though.
>>>
>>> Best regards,
>>> Dmytro Dziuma
>>>
>>>
>>> On Fri, Jan 10, 2014 at 11:16 AM, Andrea Zanni >> > wrote:
>>>
>>>> Thank you Lugusto, I made mine.
>>>> I was wondering: would it be crazy to ask the WMF Legal team if
>>>> something could be done, for Wikisource, for the URAA problem?
>>>>
>>>> I mean: could it be possible to store all the Wikisource content in a
>>>> server outside US? Would it change anything?
>>>>
>>>> Aubrey
>>>>
>>>>
>>>> On Fri, Jan 10, 2014 at 4:22 AM, Luiz Augusto wrote:
>>>>
>>>>> I've already made my remarks on
>>>>>
>>>>>
>>>>> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain
>>>>>
>>>>> but your help to make this post less Wikipedia-oncentric would be
>>>>> welcome =)
>>>>>
>>>>> -- Forwarded message --
>>>>> From: Yana Welinder 
>>>>> Date: Thu, Jan 9, 2014 at 9:39 PM
>>>>> Subject: [Advocacy Advisors] Blog post about Wikipedia and the public
>>>>> domain
>>>>> To: advocacy_advis...@lists.wikimedia.org
>>>>> Cc: "legalt...@lists.wikimedia.org" ,
>>>>> Corynne Mcsherry , Jake Orlowitz ,
>>>>> Parker Higgins , Daniel Mietchen <
>>>>> daniel.mietc...@googlemail.com>, Andrea Zanni <
>>>>> zanni.andre...@gmail.com>, Mitch Stoltz 
>>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>> We have prepared a guest blog post for EFF about how Wikipedia relies
>>>>> on the public domain:
>>>>>
>>>>>
>>>>> https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain
>>>>>
>>>>> The final post will be published on January 14 as part of a copyright
>>>>> activism week that EFF and other organizations are doing next week.  You
>>>>> can find more information below about the different themes for the week.
>>>>> It’s a great opportunity to raise awareness of the importance of the 
>>>>> public
>>>>> domain, so I'd love to get your input on the draft.
>>>>>
>>>>> Thanks,
>>>>> Yana
>>>>>
>>>>> --
>>>>> Monday Jan 13 - Transparency:
>>>>> Copyright policy must be set through a participatory, democratic and
>>>>> transparent process. It should never be decided through back room deals
>>>>> or secret international agreements.
>>>>>
>>>>> Tuesday Jan 14 - Building and Defending a Robust Public Domain:
>>>>> The public domain is our cultural commons and a public trust. Copyright
>>>>> policy should seek to promote, and never

Re: [Wikisource-l] Fwd: [Advocacy Advisors] Blog post about Wikipedia and the public domain

[Luiz Augusto]

Back in 2007 I've proposed something similar to it, but some argued
agains't:

http://lists.wikimedia.org/pipermail/commons-l/2007-April/001703.html


On Fri, Jan 10, 2014 at 8:14 AM, Andrea Zanni wrote:

> Hi Dmytro,
> yes, Wikilivres is great, but is yet another website.
> Wikisource communities are pretty small (compared to Wikipedia ones) and
> we even have another multilingual Wikisource (oldwikisource), and again
> another non-WMF multilingual one (Wikilivres)
> I think it's too much :-)
> we'd need to coordinate and focus our efforts.
>
> My idea is: if we had a *server* with Wikisource content in Canada, for
> example, we could simply use the normal copyright of the country of the
> user of the local Wikisource?
> It's a question, I don't know the answer.
>
> But maybe it's worth asking the lawyers.
>
> Aubrey
>
>
>
> On Fri, Jan 10, 2014 at 10:23 AM, Dmytro Dziuma wrote:
>
>> Hi Andrea,
>>
>> Don't we have Wikilivres for that? Ideally it would be great if it was
>> operated by WMF though.
>>
>> Best regards,
>> Dmytro Dziuma
>>
>>
>> On Fri, Jan 10, 2014 at 11:16 AM, Andrea Zanni 
>> wrote:
>>
>>> Thank you Lugusto, I made mine.
>>> I was wondering: would it be crazy to ask the WMF Legal team if
>>> something could be done, for Wikisource, for the URAA problem?
>>>
>>> I mean: could it be possible to store all the Wikisource content in a
>>> server outside US? Would it change anything?
>>>
>>> Aubrey
>>>
>>>
>>> On Fri, Jan 10, 2014 at 4:22 AM, Luiz Augusto  wrote:
>>>
>>>> I've already made my remarks on
>>>>
>>>>
>>>> https://meta.wikimedia.org/wiki/Talk:Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain
>>>>
>>>> but your help to make this post less Wikipedia-oncentric would be
>>>> welcome =)
>>>>
>>>> -- Forwarded message --
>>>> From: Yana Welinder 
>>>> Date: Thu, Jan 9, 2014 at 9:39 PM
>>>> Subject: [Advocacy Advisors] Blog post about Wikipedia and the public
>>>> domain
>>>> To: advocacy_advis...@lists.wikimedia.org
>>>> Cc: "legalt...@lists.wikimedia.org" ,
>>>> Corynne Mcsherry , Jake Orlowitz ,
>>>> Parker Higgins , Daniel Mietchen <
>>>> daniel.mietc...@googlemail.com>, Andrea Zanni ,
>>>> Mitch Stoltz 
>>>>
>>>>
>>>> Hi all,
>>>>
>>>> We have prepared a guest blog post for EFF about how Wikipedia relies
>>>> on the public domain:
>>>>
>>>>
>>>> https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain
>>>>
>>>> The final post will be published on January 14 as part of a copyright
>>>> activism week that EFF and other organizations are doing next week.  You
>>>> can find more information below about the different themes for the week.
>>>> It’s a great opportunity to raise awareness of the importance of the public
>>>> domain, so I'd love to get your input on the draft.
>>>>
>>>> Thanks,
>>>> Yana
>>>>
>>>> --
>>>> Monday Jan 13 - Transparency:
>>>> Copyright policy must be set through a participatory, democratic and
>>>> transparent process. It should never be decided through back room deals
>>>> or secret international agreements.
>>>>
>>>> Tuesday Jan 14 - Building and Defending a Robust Public Domain:
>>>> The public domain is our cultural commons and a public trust. Copyright
>>>> policy should seek to promote, and never diminish, this crucial
>>>> resource.
>>>>
>>>> Wednesday Jan 15 - Open Access: The results of publicly funded research
>>>> should be made freely available to the public online, to be fully used
>>>> by anyone, anywhere, anytime.
>>>>
>>>> Thursday Jan 16 - You Bought it, You Own It: Copyright policy should
>>>> foster the freedom to truly own your stuff: to tinker with it, repair
>>>> it, reuse it, recycle it, read or watch or launch it on any device, lend
>>>> it, and then give it away (or re-sell it) when you're done.
>>>>
>>>> Friday Jan 17 - Fair Use Rights:
>>>> For copyright to achieve its purpose of encouraging creativity and
>>>> in

[Wikisource-l] Fwd: [Advocacy Advisors] Blog post about Wikipedia and the public domain

[Luiz Augusto]

I've already made my remarks on

https://meta.wikimedia.org/wiki/Talk:Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain

but your help to make this post less Wikipedia-oncentric would be welcome =)

-- Forwarded message --
From: Yana Welinder 
Date: Thu, Jan 9, 2014 at 9:39 PM
Subject: [Advocacy Advisors] Blog post about Wikipedia and the public domain
To: advocacy_advis...@lists.wikimedia.org
Cc: "legalt...@lists.wikimedia.org" ,
Corynne Mcsherry , Jake Orlowitz ,
Parker Higgins , Daniel Mietchen <
daniel.mietc...@googlemail.com>, Andrea Zanni ,
Mitch Stoltz 


Hi all,

We have prepared a guest blog post for EFF about how Wikipedia relies on
the public domain:

https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts/Wikipedia_Shows_the_Value_of_a_Vibrant_Public_Domain

The final post will be published on January 14 as part of a copyright
activism week that EFF and other organizations are doing next week.  You
can find more information below about the different themes for the week.
It’s a great opportunity to raise awareness of the importance of the public
domain, so I'd love to get your input on the draft.

Thanks,
Yana

--
Monday Jan 13 - Transparency:
Copyright policy must be set through a participatory, democratic and
transparent process. It should never be decided through back room deals
or secret international agreements.

Tuesday Jan 14 - Building and Defending a Robust Public Domain:
The public domain is our cultural commons and a public trust. Copyright
policy should seek to promote, and never diminish, this crucial resource.

Wednesday Jan 15 - Open Access: The results of publicly funded research
should be made freely available to the public online, to be fully used
by anyone, anywhere, anytime.

Thursday Jan 16 - You Bought it, You Own It: Copyright policy should
foster the freedom to truly own your stuff: to tinker with it, repair
it, reuse it, recycle it, read or watch or launch it on any device, lend
it, and then give it away (or re-sell it) when you're done.

Friday Jan 17 - Fair Use Rights:
For copyright to achieve its purpose of encouraging creativity and
innovation, it must preserve and promote ample breathing space for
unexpected and innovative uses.

Saturday Jan 18 - Getting Copyright Right:
A free and open Internet is essential infrastructure, fostering speech,
activism, new creativity and new business models for artists, authors,
musicians and other creators. It must never be sacrificed in the name of
copyright enforcement.

-- 
Yana Welinder
Legal Counsel
Wikimedia Foundation
415.839.6885 ext. 6867



___
Advocacy_Advisors mailing list
advocacy_advis...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/advocacy_advisors
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Mass deletions on pt.wikisource

[Luiz Augusto]

In the next hours I will start a mass deletion of pages on pt.wikisource
(64k on ns:0 and 6k on ns:Page).

ns:0 mass deletion is due to an (still) incomplete import of contents from
a PD-old dictionary proofreaded by Distributed Proofreaders. The content
still is valid and relevant to Wikisource, but the task that my bot had
done years ago contains lots of tecnical issues (and certainly 1 definition
per content page wasn't the right choice from my side). Content is anyway
available at http://www.dicionario-aberto.net ;

ns:Page mass deletion is to prevent BLP issues, since it reproduces raw
unformated texts from Commission d'enquête parlementaire done to inquire
political corruption scandals. The very few amount of pages proofreaded
from this set will be keept.

More on

https://pt.wikisource.org/wiki/Utilizador:Delete.Bot#janeiro_de_2014

https://pt.wikisource.org/wiki/Wikisource:Esplanada/Eliminações_via_bot_(jan2014)_

I'm sending this note since it will change significantly some global
Wikisource statistics.

[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Issues with ProofreadPage

[Luiz Augusto]

Browsers tested:
* Google Chrome 31.0.1650.63 m
* Firefox 26.0
* Internet Explorer 11.0.9600.16476
all on Windows 7 Home Premium SP1 x64

skin Vector with WikiEditor

https://pt.wikisource.org/wiki/MediaWiki:Common.js
+ gadgets default enabled to all users:
https://pt.wikisource.org/wiki/MediaWiki:Gadget-Extra_toolbar.js
https://pt.wikisource.org/wiki/MediaWiki:Gadget-Edittools.js
https://pt.wikisource.org/wiki/MediaWiki:Gadget-Modernizacao.js
https://pt.wikisource.org/wiki/MediaWiki:Gadget-LanguageConverter.css
https://pt.wikisource.org/wiki/MediaWiki:Gadget-Correlatos.js
https://pt.wikisource.org/wiki/MediaWiki:Gadget-Internet_Explorer.js
+ we on pt.wikisource have also FlaggedRevs enabled on some namespaces,
including the Página one (ns:106)

https://ca.wikisource.org/wiki/MediaWiki:Common.js
- they don't have neither gadgets enabled to all users neither FlaggedRevs
extension

I hope that helps =)

Many thanks,
Luiz


On Mon, Dec 16, 2013 at 8:42 AM,  wrote:

> > > 2013/12/14 Luiz Augusto 
> > > Header and footer sections aren't being displayed on pt.wikisource.
>
> Isn't it the Safari 4.0/5.1 and IE < 8 trouble we got also on fr.wp ?
>
> --
> Phe
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Issues with ProofreadPage

[Luiz Augusto]

I've just found the same scenery on ca.wikisource:

https://ca.wikisource.org/w/index.php?title=Pàgina:L%27auca_del_senyor_Esteve_(1912).djvu/145&action=edit<https://ca.wikisource.org/w/index.php?title=P%C3%A0gina:L%27auca_del_senyor_Esteve_(1912).djvu/145&action=edit>


On Sat, Dec 14, 2013 at 8:59 PM, Alex Brollo  wrote:

> Strange I entered and I saw them, both logged and unlogged; I only
> found a default setting to hide them, but both using preferences or
> Proofreading tools (Instrumentos de revisão) header and footer can be seen.
>
> Alex
>
>
> 2013/12/14 Luiz Augusto 
>
>> Header and footer sections aren't being displayed on pt.wikisource.
>>
>> Maybe it's due to local scripts?
>>
>> Example:
>> https://pt.wikisource.org/w/index.php?title=P%C3%A1gina:Phar%C3%B3es.pdf/45&action=edit
>>
>>
>> On Wed, Dec 11, 2013 at 12:52 AM, billinghurst wrote:
>>
>>> Gday Tpt,
>>>
>>> I would like to thank you for all the work that you have been doing to
>>> firstly convert the ProofreaPage extension away from the javascript
>>> methodology, into the new schema.  Then all the time that you have spent
>>> bug fixing this past week. It probably sounds as though we are
>>> complaining
>>> at times with raising issues, but to let you know personally that I think
>>> that the work that you have been doing for the editing community, and
>>> then
>>> for the reading community, is magnificent.
>>>
>>> So that big thank you to you, and to those who have helped problem solve
>>> this past week. Really appreciated.
>>>
>>> Regards Billinghurst
>>>
>>> On Tue, 10 Dec 2013 21:34:09 +0100, Thomas Tanon 
>>> wrote:
>>> > Hi!
>>> >
>>> > Some improvements and bug corrections have been deployed some minutes
>>> ago
>>> > as part of MediaWiki 1.23wmf6:
>>> >
>>> > Here is a list of fixed issues:
>>> > * A JavaScript fatal error in Page: pages editing interface is solved
>>> for
>>> > Internet Explorer 8 or less and old Safari versions.
>>> > * Mediawiki:proofreadpage_default_header and
>>> > Mediawiki:proofreadpage_default_footer and text layer extraction now
>>> works
>>> > for Page: pages without index.
>>> > * It is possible again to zoom in on mouse scroll.
>>> > * The level change summary tag is now added when you click on the level
>>> > selector (it’s what was done before the new Page: pages editing
>>> interface
>>> > deployment)
>>> >
>>> > Here is the remaining known issues (thanks to report ones that haven’t
>>> > been listed here):
>>> > * Fatal error on submit for a very few pages (a correction is on
>>> review)
>>> > * the issue with gadget that Aubrey have reported here (I think that
>>> the
>>> > solution is more on the gadget side that on the extension one)
>>> > * It isn't possible to edit only the body of a page throw the API
>>> > * The body content editing area doesn’t fit the scan height in vertical
>>> > editing mode. I’m looking for a clean way to fix this problem.
>>> > * The tab order in Page: pages editing interface is strange. A
>>> correction
>>> > for it is ready and will be deployed soon.
>>> >
>>> > Thomas
>>> >
>>> > Le 6 déc. 2013 à 23:53, Alex Brollo  a écrit :
>>> >
>>> >> Thanks Thomas but I can't write php, just a little of python and
>>> >> javascript.
>>> >> But more or less I can read it (if statements are simple) , thanks for
>>> >> link.
>>> >>
>>> >> Alex
>>> >>
>>> >>
>>> >> 2013/12/6 Thomas Tanon 
>>> >> The trim final routine is done automatically by the Wikitext content
>>> >> representation. So, it have been very easy to implement. If you are
>>> >> interested, here is the internal representation of a Page: page:
>>> >>
>>>
>>> https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FProofreadPage.git/8435e3855decbebc809280edffc9013b38b1f349/includes%2Fpage%2FProofreadPageContent.php
>>> >> About automatic addition of the references tag, it’s a good idea. Feel
>>> >> free to hack the extension (you are really invited to do so :-)) or to
>>> >> fill a bug on bugzilla.
>>> >> Thomas
&g

Re: [Wikisource-l] Issues with ProofreadPage

[Luiz Augusto]

Header and footer sections aren't being displayed on pt.wikisource.

Maybe it's due to local scripts?

Example:
https://pt.wikisource.org/w/index.php?title=P%C3%A1gina:Phar%C3%B3es.pdf/45&action=edit


On Wed, Dec 11, 2013 at 12:52 AM, billinghurst wrote:

> Gday Tpt,
>
> I would like to thank you for all the work that you have been doing to
> firstly convert the ProofreaPage extension away from the javascript
> methodology, into the new schema.  Then all the time that you have spent
> bug fixing this past week. It probably sounds as though we are complaining
> at times with raising issues, but to let you know personally that I think
> that the work that you have been doing for the editing community, and then
> for the reading community, is magnificent.
>
> So that big thank you to you, and to those who have helped problem solve
> this past week. Really appreciated.
>
> Regards Billinghurst
>
> On Tue, 10 Dec 2013 21:34:09 +0100, Thomas Tanon 
> wrote:
> > Hi!
> >
> > Some improvements and bug corrections have been deployed some minutes
> ago
> > as part of MediaWiki 1.23wmf6:
> >
> > Here is a list of fixed issues:
> > * A JavaScript fatal error in Page: pages editing interface is solved
> for
> > Internet Explorer 8 or less and old Safari versions.
> > * Mediawiki:proofreadpage_default_header and
> > Mediawiki:proofreadpage_default_footer and text layer extraction now
> works
> > for Page: pages without index.
> > * It is possible again to zoom in on mouse scroll.
> > * The level change summary tag is now added when you click on the level
> > selector (it’s what was done before the new Page: pages editing
> interface
> > deployment)
> >
> > Here is the remaining known issues (thanks to report ones that haven’t
> > been listed here):
> > * Fatal error on submit for a very few pages (a correction is on review)
> > * the issue with gadget that Aubrey have reported here (I think that the
> > solution is more on the gadget side that on the extension one)
> > * It isn't possible to edit only the body of a page throw the API
> > * The body content editing area doesn’t fit the scan height in vertical
> > editing mode. I’m looking for a clean way to fix this problem.
> > * The tab order in Page: pages editing interface is strange. A
> correction
> > for it is ready and will be deployed soon.
> >
> > Thomas
> >
> > Le 6 déc. 2013 à 23:53, Alex Brollo  a écrit :
> >
> >> Thanks Thomas but I can't write php, just a little of python and
> >> javascript.
> >> But more or less I can read it (if statements are simple) , thanks for
> >> link.
> >>
> >> Alex
> >>
> >>
> >> 2013/12/6 Thomas Tanon 
> >> The trim final routine is done automatically by the Wikitext content
> >> representation. So, it have been very easy to implement. If you are
> >> interested, here is the internal representation of a Page: page:
> >>
>
> https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FProofreadPage.git/8435e3855decbebc809280edffc9013b38b1f349/includes%2Fpage%2FProofreadPageContent.php
> >> About automatic addition of the references tag, it’s a good idea. Feel
> >> free to hack the extension (you are really invited to do so :-)) or to
> >> fill a bug on bugzilla.
> >> Thomas
> >>
> >> Le 6 déc. 2013 à 14:28, Alex Brollo  a écrit :
> >>
>  Hi!
>  No, there isn’t any doc about it. The Proofread Page doc is very
> messy
>  and work on documentation is something really needed (it’s something
>  that any advanced editor of Wikisource can do).
>  # yes the bottom of nsPage body is trimmed (it’s normal normalisation
>  of wikitext content). If it breaks pages we can disable this
>  normalisation.
>  # you can add a default footer content in Mediawiki:proofread
>  page_default_footer (it doesn’t works currently because of a bug but
> it
>  should be fixed soon (in the worst case at next Tuesday deployment)).
>
>  If you want to customize this value for a specific index, just add a
>  new field called 'Footer’ (the ID is important) in
>  MediaWiki:Proofreadpage_index_data_config with header:true.
>  en.wikisource use this feature.
>  # basically yes
>  # yes you have to if you use the action=edit API. I’m working on an
>  other API action that will allow to edit only the body and/or the
>  proofreading level (and that will be used also by the VisualEditor
> when
>  it’ll be integrated)
> >>>
> >>>by Thomas
> >>>
> >>> Thanks for details; usually we are learning by "try and learn" and
> >>> explicit details like those you give save hours of tries!
> >>>
> >>> # trimming bottom of the page: IMHO it's an excellent idea. The simple
> >>> trick to add (manually or by a script launched at onSubmit event) a
> >>> tl|nop at the bottom of the page when needed to force the closure of a
> >>> paragraph at the bottom of the page and saves many transclusion
> issues.
> >>> # in the meantime, since we have to activate such a "final cleanup
> >>> routine", it would be eas

Re: [Wikisource-l] [Wikidata-l] DNB 11M bibliographic records as CC0

[Luiz Augusto]

On Mon, Dec 9, 2013 at 12:18 PM, Tom Morris  wrote:


> I'm not sure I agree.  There's a lot of good data in OpenLibrary, but
> there's also a lot of junk.  Freebase imported a bunch of OpenLibrary data,
> after winnowing it to what they thought was the good stuff, and still ended
> up deleting a bunch of the supposedly "good" stuff later because they found
> their goodness criteria hadn't been strict enough.
>
> One of the reasons OpenLibrary is such a mess is because *they*
> arbitrarily imported junky data (e.g. Amazon scraped records).  The last
> thing the world needs is more duplicate copies of random junk.  We've
> already got the DPLA for that. :-)
>
> Another issue with the OpenLibrary metadata is that there's no clear
> license associated with it.  IA's position is that they got it from
> wherever they got it from and you're own your own if you want to reuse it,
> which isn't very helpful.  The provenance for major chunks of it is
> traceable and new stuff by users is nominally being contributed under CC0,
> so they could probably be sorted out with enough effort (although the same
> thing is true of the data quality issues too).
>
>
>
Gosh, I withdraw my support for fully reusage of Open Library data.

That was probably the best efforts they can do in past years, before the
mass disponibilization of data dumps directly from well known libraries
catalogs, but now we are in a very different scenario.

Even a simple mass import from the already mentioned datahub [1] in the
openlibrary engine (open source software) without further editing will
generate best quality data.

[1] - http://datahub.io/group/bibliographic
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Wikidata-l] DNB 11M bibliographic records as CC0

[Luiz Augusto]

Due to weird reasons my message was sent only to wikidata-l. Re-sending to
wikisource-l. Sorry for any inconvenience


On Sun, Dec 8, 2013 at 2:04 AM, Luiz Augusto  wrote:

>
> On Sat, Dec 7, 2013 at 12:47 PM, Thomas Douillard <
> thomas.douill...@gmail.com> wrote:
>>
>>
>> That's why I think we must do a lot more with such datas than just
>> importing them from openlibrary, as they are really important to Mediawiki
>> in general, and that the community as a whole is a powerful drinving force
>> for Bibliographical datas. I'm not against cooperating with openlibrary,
>> but we should seek deep cooperation and integration with them so both
>> projects can benefits from each others community.
>>
>
> +1 on this
>
> openlibrary.org have a limited set of fields.
>
> Moreover, simply importing data at some random time of some random records
> will not benefit neither openlibrary neither Wikimedia.
>
> You will first need to search if Wikidata don't have the needed
> information, search again for it in openlibrary, create the content in
> openlibrary, import the content into Wikidata, make the desired local
> changes and send back to openlibrary any local relevant changes.
>
> But I had an idea: a MediaWiki User Interface to openlibrary data
>
> openlibrary.org offers access to records in 3 ways:
>
> * read/write of individual records through API;
> * read of individual records through RDF and JSON;
> * bulk download of the entire dataset
>
> So i'ts possible to:
>
> 1) Import the bulk data;
> 2) Catch all changes from openlibrary.org in real time;
> 3) Allows that the synced data can be browsable and editable at any time
> on MediaWiki/Wikidata instances;
> 4) Sends back to openlibrary the changes, storing locally the data from
> custom fields in the MediaWiki instance (allowing further import at
> openlibrary instance if they creates the corresponding fields in their DB);
> 5) Sends back to openlibrary all new book records created on MediaWiki
> instances.
>
>
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Wikidata-l] DNB 11M bibliographic records as CC0

[Luiz Augusto]

There are reasons for editing and there are also reasons for not editing.

One big reason *for* editing is if at any time data from new sources are
being imported.

We in Librarianship/Information Sciences makes decisions on how the data
will be available to our users/customers. Eg an author name. There are many
ways to write the same name from the same individual. The same individual
can adopt in his life dozens of nicknames, change their last name if gets
married and so on. The rule choosen in a particular library can be the same
in more libraries, or even an entire different one (based on how the local
community of users from a library will search/wants the data), or even no
rule is choosen and the data is recorded "as is" it is registered in the
publication. Some libraries have additional records specially devoted to
the synonymies for the same name, some not.

Google Book Search simply imported data from many libraries without making
any attempt to standardize then, resulting in the large amount of
duplicates and bullshits founds in some searches (specially those whose the
imprints didn't standardizet themselves the data).

Some special kinds of data from the same work can also be stored in
differents sets of "fields" and "subfields" of MARC21 records across
different libraries, again because the user/client need of informations
about the works can vary from place to place (ie you get data duplication
in the same record if you simple merge records from libraries).

MARC21 specification have also an entire design that IMHO is impossible to
reflect in the current MediaWiki schema, even with Semanctic MediaWiki.

And sometimes some libraries tells that their data is stored on MARC21
fields, but are on USMARC ones (yep, there are many flavours of MARC as
there are many flavors of Ubuntu). Or it is *based* on MARC21 fields, with
dozens of local adaptions.

I've just finished an internship in a library with 45k of records that was
migrating data from REPIDISCA *based* fields (let's call it as a FreeBSD
flavour) to MARC21 *based* fields (in this comparision, an Ubuntu flavour;
and yep, *based*, with local adaptions, we needs those changes). The data
is migrated in an automated fashion, but still needs to be validated record
by record if the library wants those records in the MARC21 fields as it's.

What I'm saying is:

1) You can't simply import data from many sources without validations
expecting a good quality end product. You will get a "search engine"
quality data (tons of random informations that will make sense only with a
continuously developed set of algorithms maybe more time+resources
consuming than standartizing the data);

2) Data standardize is an epic work dozens of times more epic than writing
an comprehensive encyclopedia about all subjects on all languages.
Institutional support will be needed, and in more compreensive ways
embracing more than just releasing their data to play around it (ie, with
additional hands for standardization).

[[Paul Otlet]] (1868-1944) tried it in efforts that some argues he's the
concept designer of Internet and hypertext. With no success, what is very
unfortunate. Will the wikimedians gets any level of success on it?

[[:m:User:555]]

On Fri, Dec 6, 2013 at 9:59 PM, Denny Vrandečić  wrote:

> Thanks for reviving this thread, Luiz. I also wanted to ask whether we
> should be updating parts of DNB and similar data. Maybe not create new
> entries, but for those that we already have, add some of the available data
> and point to the DNB dataset?
>
>
> On Fri, Dec 6, 2013 at 3:24 PM, Luiz Augusto  wrote:
>
>> Just found this thread while browsing my email archives (I'm/was inactive
>> on Wikimedia for at least 2 years)
>>
>> IMHO will be very helpfull if a central place hosting metadata from
>> digitized works will be created.
>>
>> In my past experience, I've found lots of PD-old books from languages
>> like french, spanish and english in repositories from Brazil and Portugal,
>> with UI mostly in portuguese (ie, with very low probabilities to get found
>> by volunteers from subdomains from those languages), for example.
>>
>> I particularly loves validating metadata more than proofreading books.
>> Perhaps a tool/place like this makes new ways to contribute to Wikisource
>> and helps on user retention (based on some wikipedians that gets fun making
>> good articles but loves also sometimes to simply make trivial changes on
>> their spare time)?
>>
>> I know that the thread was focused on general metadata from all kinds and
>> ages of books, but I had this idea while reading this
>>
>> [[:m:User:555]]
>>
>>
>> On Mon, Aug 26, 2013 at 10:42 AM, Thomas Douillard <
>> thomas.douill...@gmail.com> wrote:
>

Re: [Wikisource-l] [Wikidata-l] DNB 11M bibliographic records as CC0

[Luiz Augusto]

Just found this thread while browsing my email archives (I'm/was inactive
on Wikimedia for at least 2 years)

IMHO will be very helpfull if a central place hosting metadata from
digitized works will be created.

In my past experience, I've found lots of PD-old books from languages like
french, spanish and english in repositories from Brazil and Portugal, with
UI mostly in portuguese (ie, with very low probabilities to get found by
volunteers from subdomains from those languages), for example.

I particularly loves validating metadata more than proofreading books.
Perhaps a tool/place like this makes new ways to contribute to Wikisource
and helps on user retention (based on some wikipedians that gets fun making
good articles but loves also sometimes to simply make trivial changes on
their spare time)?

I know that the thread was focused on general metadata from all kinds and
ages of books, but I had this idea while reading this

[[:m:User:555]]


On Mon, Aug 26, 2013 at 10:42 AM, Thomas Douillard <
thomas.douill...@gmail.com> wrote:

> I know, I started a discussion about porting the bot to WIkidata in
> scientific Journal Wikiproject. One answer I got : the bot owner had other
> things to do in his life than running the bot and was not around very often
> any more. Having everiyhing in Wikidata already will be a lot more reliable
> and lazier, no tool that works one day but not the other one, no effort to
> tell the newbies that they should go to another website, no significant
> problem.
>
> Maybe one opposition would be that the data would be vandalised easily,
> but maybe we should find a way to deal with imported sourced datas which
> have no real reason to be modified, just marked deprecated or updated by
> another import from the same source.
>
>
> 2013/8/26 David Cuenca 
>
>> If the problem is to automate bibliographic data importing, a solution is
>> what you propose, to import everything. Another one is to have an import
>> tool to automatically import the data for the item that needs it. In WP
>> they do that, there is a tool to import book/journal info by ISBN/doi. The
>> same can be done in WD.
>>
>> Micru
>>
>>
>> On Mon, Aug 26, 2013 at 9:23 AM, Thomas Douillard <
>> thomas.douill...@gmail.com> wrote:
>>
>>> If Wikidata has an ambition to be a really reliable database, we should
>>> do eveything we can to make it easy for users to use any source they want.
>>> In this perspective, if we got datas with guaranted high quality, it make
>>> it easy for Wikidatian to find and use these references for users. Entering
>>> a reference in the database seems to me a highly fastidious, boring, and
>>> easily automated task.
>>>
>>> With that in mind, any reference that the user will not have to enter by
>>> hand is something good, and import high quality sources datas should pass
>>> every Wikidata community barriers easily. If there is no problem for the
>>> software to handle that many information, I say we really have no reason
>>> not to do the imports.
>>>
>>> Tom
>>>
>>>
>>> ___
>>> Wikidata-l mailing list
>>> wikidat...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>
>>>
>>
>>
>> --
>> Etiamsi omnes, ego non
>>
>> ___
>> Wikidata-l mailing list
>> wikidat...@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>
>>
>
> ___
> Wikidata-l mailing list
> wikidat...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Advocacy Advisors] Joining a letter on copyright term in the TPP?

[Luiz Augusto]

-- Mensagem encaminhada --
De: "Stephen LaPorte" 
Data: 05/12/2013 20:57
Assunto: [Advocacy Advisors] Joining a letter on copyright term in the TPP?
Para: "Advocacy Advisory Group for WMF LCA" <
advocacy_advis...@lists.wikimedia.org>

Hello advocacy advisers,

Current drafts of the Trans Pacific Partnership[0], a new trade treaty
currently being negotiated, contains language that would require countries
that sign the treaty to extend the length of the minimum copyright term to
life of the author plus 70 years. Global treaties currently require only
life + 50 years, so the TPP would represent a widespread extension of
copyright terms by 20 years, and make it hard to roll back the copyright
term in countries that already have life + 70.

The letter below[1], addressed to the TPP negotiators, directly addresses
this issue. We’re considering signing, because the letter is specifically
targeted at an issue (copyright term) that is core to our encyclopedic
mission, and affects (at present) 14 different countries.

Does the advisory group have any thoughts about joining the letter? We
would like to let KEI know if we will join the letter before December 7,
2013.

[0] https://en.wikipedia.org/wiki/Trans-Pacific_Partnership ;
http://tppinfo.org/

(We briefly mentioned TPP in the Wikilegal fact sheet on ACTA in January
2012. If anyone is interested in updating that document, feel free to get
in touch! See:  https://meta.wikimedia.org/wiki/Wikilegal/ACTA)

[1] http://keionline.org/nolifeplus70intpp

--

The letter was prepared by Knowledge Ecology International, and will be
joined by like-minded organizations including the Open Knowledge
Foundation, Electronic Frontier Foundation, and Free Software Foundation.

Full copy of the letter:

*Dear TPP negotiators,*

*In a December 7-10 meeting in Singapore you will be asked to endorse a
binding obligation to grant copyright protection for 70 years after the
death of an author. We urge you to reject the life+ 70 year term for
copyright.*

*There is no benefit to society of extending copyright beyond the 50 years
mandated by the WTO. While some TPP countries, like the USA, Mexico, Peru,
Chile or Australia, already have life+ 70 (or longer) copyright terms,
there is growing recognition that such terms were a mistake, and should be
shortened, or modified by requiring formalities for the extended periods.*

*The primary harm from the life+ 70 copyright term is the loss of access to
countless books, newspapers, pamphlets, photographs, films, sound
recordings and other works that are “owned” but largely not commercialized,
forgotten, and lost. The extended terms are also costly to consumers and
performers, while benefiting persons and corporate owners that had nothing
to do with the creation of the work.*

*Life+70 is a mistake, and it will be an embarrassment to enshrine this
mistake into the largest regional trade agreement ever negotiated.*

-- 
Stephen LaPorte
Legal Counsel
Wikimedia Foundation

*This message might have confidential or legally privileged information in
it. If you have received this message by accident, please delete it and let
us know about the mistake. For legal reasons, I may only serve as an
attorney for the Wikimedia Foundation. This means I may not give legal
advice to or serve as a lawyer for community members, volunteers, or staff
members in their personal capacity.*

___
Advocacy_Advisors mailing list
advocacy_advis...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/advocacy_advisors
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikimedia-l] Creating Wikikultur

[Luiz Augusto]

FYI, proposal for a new Wikimedia project or Wikibooks/Wikisource inclusion
criteria
-- Mensagem encaminhada --
De: "Mathieu Stumpf" 
Data: 27/11/2012 14:37
Assunto: [Wikimedia-l] Creating Wikikultur
Para: 

Hello, I just added this proposition : http://meta.wikimedia.org/**
wiki/Wikikultur 

Here is the summary :
Currently there are still some digital works which can not be published on
a wikimedia projects, because none of them have the right editorial
guideline to host them. Things like original poetry, songs, essays, theses,
novels, etc., wether they were already previously published or not.

It would be great to see wikimedia launch a project to host this kind of
works.

The no original research for wikipedia is understable and very important of
course. Now what's relevant for an encyclopedia may not fit others projects
which need different editorial guidelines. In existing projects Wikibooks
is too pedagogic works oriented, and wikisource won't accept works which
were not previously published elsewhere.

Moreover, one may argue that it would be a good way to softly evacuate
originals works from wikipedia, with a message like "your contribution
contains original claims, wikipedia is not the place to publish this kind
of content, but you could share your original work on wikikultur". Then
eventualy, the wikipedia article could use wikikultur arcticles as
references. This would give access to authoring information (eventually
anonymous/IP claims), and all avantages of a free/libre work on a wiki. For
example, we may have statistics on articles, so we can check if it's not
used as a reference of an over represented point of view in an wikipedia
article.

On artistics topics, I think it would really help to boost the free-libre
culture movement to have a place where every artists can directly
experiment what it means to share and build together, with an audience
intertwinned with other mediawiki projects.



It looks like other proposed projects would be included in such a project,
like Wikiessay (I just discovered and I'm gonna read others projects
description, sorry), but others aspect don't seem - at first glance - to be
covered, like artistics topics.

Kind regards,
mathieu

-- 
Association Culture-Libre
http://www.culture-libre.org/

__**_
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.**org 
Unsubscribe: 
https://lists.wikimedia.org/**mailman/listinfo/wikimedia-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [GLAM] Library e-books on demand

[Luiz Augusto]

-- Mensagem encaminhada --
De: "Ole Palnatoke Andersen" 
Data: 01/11/2012 06:35
Assunto: [GLAM] Library e-books on demand
Para: "Wikimedia & GLAM collaboration [Public]" 

Hi!

The Royal Library in Copenhagen has started making free e-books on demand
from Danish 1701-1900 books in their collections.

By doing this, they get more usage but less wear and tear and more space in
the reading room :-)

More on http://www.kb.dk/en/nb/samling/dod/index.html


Regards,
Ole


-- 
http://palnatoke.org * @palnatoke * +4522934588

___
GLAM mailing list
g...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/glam
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] "A Collaborative Environment For Music Transcription And Publishing"

[Luiz Augusto]

FYI, the following Open Acces paper describes an implementation of DokuWiki
and ABC to make a collaborative environment for music scores.

May be interesting for those that watches the inactivity on
[[bugzilla:189]] (opened on 2004).

http://www.booksonline.iospress.nl/Content/View.aspx?piid=30623

DOI:10.3233/978-1-61499-065-9-82

Best,
[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Still wikipediocentric

[Luiz Augusto]

Dear all,

I was the [[:m:User:555]], mainly active on the last years of my volunteers
actions on Wikimedia Commons and Wikisource. I've left the Wikimedia
projects mainly because the lack of energy from my side to keep trying to
get free time to work in projects fully neglected by the Wikimedia staff,
developers team and some volunteers in the core of the Foundaction acts.

A friend told me about the http://labs.wikimedia.beta.wmflabs.org/ . I've
checked http://labs.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrixand...
surprise! no Wikisource wikis with blue color links! I asked myself
random things about the [[bug:21653]] lasted for 26 months until gets
PARTIALLY fixed and decided to check some 'Recent changes' pages and found
this:

http://pt.wikisource.org/w/index.php?diff=prev&oldid=233269

Come on guys! What is the point to run a bot spamming on all wikis if the
tests are only to the Wikipedias? Attempt of a 'politically correct' action
to these worse guys from others projects get's 'socially included'? Like in
the real life, those worse guys aren't in need of assistencialism [1]
actions...

Well, I don't expect any change on the Wikipediocentric actions in short,
medium or long time (in fact the Foundation and some local chapters are
trying to make things for the Wikimedia Commons project, but only because
that project is the central media source for Wikipedias), this was only a
mutter.

Despite my apparently hatred on this message, I really hope that the 3-4
extensions only enabled on Wikisources wikis don't get's any aditional bugs
than the current ones in the new version of MediaWiki in the same intensity
that your guys hopes that focusing in a project that only describes the
knowledge in an encyclopedic way fully meets the
http://wikimediafoundation.org/wiki/Mission_statement

[1] - wow, a concept from social sciences yet not defined neither on
en.wikpedia or en.wiktionary? O_O

As on all of my previous messages, sorry for my limited English skills.
Best regards,

[[:m:User:555|Lugusto]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Foundation-l] Announcement: Selected Books from Malayalam Wikisource on CD released

[Luiz Augusto]

Congratulations!

Specially because it is a non-Wikipedia CD project released after of a
Wikipedia CD project [1].

Maybe the entire Wikimedia community learn from your experience what they
can do if someone remembers that Wikimedia is more than Wikipedia.

--[[:m:User:555|Lugusto]]

[1] - http://www.mlwiki.in/ : Malayalam Wikisource on CD *2011* release and
Malayalam Wikipedia on CD *2010* release

On Sat, Jun 11, 2011 at 4:12 PM, emijrp  wrote:

> Creating an offline version of a wiki project is a hard work. Keep up the
> good work! Congratulations! : )
>
> P.D.: downloading...
>
> 2011/6/11 Jyothis E 
>
> > Dear fellow Wikimedians,
> >
> > With great pleasure, Malayalam Wikimedia Community announced its 2011 CD
> > project "Selected Books from Malayalam Wikisource on CD - 1.0" at the 4th
> > annual Wiki Meetup in Kannur, Kerala. This is by far the biggest digital
> > collection of free books in Malayalam language available on CD for
> offline
> > use. This is an important milestone, as majority of the households in
> > Kerala
> > does not have internet or does not have an always on connection and this
> > will enable them to access these books as an offline content.
> >
> > Contents:
> >
> > Selected Poems by
> >  * Kumaranasan
> >  * Cherusseri
> >  * Changampuzha Krishna Pillai
> >  * Kalakkaththu Kunchan Nambiar
> >  * Irayimman Thampi
> >  * Ramapurathu Warrier
> >
> > Malayalam Grammer
> >  * Kerala Panineeyam by AR Rajaraja Varma
> >
> > Legends/Folklore
> >  * Aithihyamala
> >
> > Novels
> >  * Indulekha
> >
> > Religious
> >  * Bhagavad Gita
> >  * Adhyatma Ramayanam Kilippaatu
> >  * Harinama Keerthanam
> >  * Geetha Govindam
> >  * Sathya Veda Pusthakam (Malayalam Bible)
> >  * Quran
> >  * Works of Sree Narayana Guru
> >  * Devotional songs for Christian, Hindu and Islamic religions
> >
> >  Native Art Form
> >  * Parichamuttukali pattukal
> >
> >  Philosophy (Political)
> >  * Communist Manifesto
> >  * Principles of Communism (Friedrich Engels)
> >
> > The CD also contains the commons collections of images on food, plants,
> > birds, maps and  celebrations from Kerala. The CD is made available for
> > download in iso format as well as browsing at our community website -
> > http://www.mlwiki.in. For those who are interested in the technical
> > challenges and aspects of the background work may read Santhosh's blog
> > post<
> >
> http://thottingal.in/blog/2011/06/11/malayalam-wikisource-offline-version/
> > >about
> > it.
> >
> > We thank every one who participated in the effort. Comments and questions
> > are welcome.
> >
> > Thanks and Regards,
> > Malayalam Wikimedia Community.
> > ___
> > foundation-l mailing list
> > foundatio...@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
> >
> ___
> foundation-l mailing list
> foundatio...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] "MediaWiki and Wikimedia Foundation development to non-Wikipedia projects"

[Luiz Augusto]

I've just made a question to the Board candidates at

http://meta.wikimedia.org/wiki/Board_elections/2011/Candidates/Questions/2#MediaWiki_and_Wikimedia_Foundation_development_to_non-Wikipedia_projects

IMO interesting to be tracked by all of us that spent some of their free
time at non-Wikipedia projects.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Changing the Main Page

[Luiz Augusto]

On Tue, Mar 3, 2009 at 10:09 AM, ThomasV  wrote:

> Luiz Augusto a écrit :
> >
> > If anyone is interested, I can start in the next weekend a draft for a
> > vote on main page changes.
> that would be great.
> I will be glad to help you
>
>
I've created the page
http://wikisource.org/wiki/Wikisource:Changing_the_main_page , that intends
to be a starting point for those with no time or patience to read the entire
discussion on wiki and here at the mailing list. This may be helpful
specially for those that will be known this issue only when spamming their
local Village pump, for example. My intention is to make a detailed page
like the http://meta.wikimedia.org/wiki/Top_Ten_Wikipedias

You and everyone on this list is invited to improve that page with more
details about the "worries" mentioned in the current page version, with pros
and cons to the specified options or adding new options to change the main
page.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Changing the Main Page

[Luiz Augusto]

On Mon, Mar 2, 2009 at 2:12 PM, Ray Saintonge  wrote:

> Occasional anomalies such as what you mentioned about pt:wikisource
> should not be driving the agenda of what happens on the Main Page.  Even
> if some kind of massive gaming or mischief was intended such anomalies
> tend to be overwhelmed by more steady and consistent behaviour.
>
> Ec
>
>
Thankyou for your nice words about adding valid and referenced public domain
content in a language spoken by 191 milion of peoples.

I strongly agree with this message:
http://wikisource.org/w/index.php?title=Talk:Main_Page&diff=247906&oldid=247810

If anyone is interested, I can start in the next weekend a draft for a vote
on main page changes.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Extension:Collection enabled on all Wikisources!

[Luiz Augusto]

.odt, not .ogg

On Tue, Feb 24, 2009 at 9:20 PM, Luiz Augusto  wrote:

> Now is possible to generate .pdf and .ogg files and to buy a printed copy
> of Wikisource pages
>
>
> http://wikitech.wikimedia.org/index.php?title=Server_admin_log&diff=18869&oldid=18868
>
> http://www.mediawiki.org/wiki/Extension:Collection
>
> http://meta.wikimedia.org/wiki/Book_tool
>
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Extension:Collection enabled on all Wikisources!

[Luiz Augusto]

Now is possible to generate .pdf and .ogg files and to buy a printed copy of
Wikisource pages

http://wikitech.wikimedia.org/index.php?title=Server_admin_log&diff=18869&oldid=18868

http://www.mediawiki.org/wiki/Extension:Collection

http://meta.wikimedia.org/wiki/Book_tool
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Wikistats seens to be inaccurate for Wikisources

[Luiz Augusto]

Hi Erik, I'm crossposting this message to the wikisource-l, if anyone is
interested to give some inputs.

The http://stats.wikimedia.org/wikisource/EN/TablesDatabaseWords.htm seens
to be inaccurate. Apparently your tool compute only words in the main
namespace. It may works for projects like Wikipedia and theirs very long
talk pages at the namespace Project: on some subjects (such as deletion
requests). But it doens't work for Wikisource for two main reasons:

1) Some subdomains have custom namespaces for short biographies and list of
works by author (en, it, pt and others), some have it on the main namespace
(fr, de, es and others). This is a minor issue, since the amount of words on
those pages is small

2) Some Wikisources (de, fr and en, according to
http://wikisource.org/wiki/Wikisource:ProofreadPage_Statistics ) have large
amount of contents in a custom namespace devoted to the ProofreadPage
Extension ( http://www.mediawiki.org/wiki/Extension:Proofread_Page ). This
content is displayed on main namespace within page transclusion (see
http://en.wikisource.org/w/index.php?title=35_Sonnets&action=edit for an
example).

Is possible to include the custom namespaces for all Wikisources on your
automated calculation tool?

[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Changing the Wikisource main page

[Luiz Augusto]

Any progress on this?

I'm asking it because I am going to destroy two statistics in the next weeks

1) Destroying the "article" count: Portuguese Wikisource will be bumped from
7th to 2th in article count when I finish the import of A to N articles from
a public domain dictionary. (See more about it at the end of this message).

2) Destroying the "all pages" from
http://wikisource.org/wiki/Wikisource:ProofreadPage_Statistics : I've found
on Internet Archive the 24 volumes of the "Décadas da Ásia" by
http://en.wikipedia.org/wiki/Jo%C3%A3o_de_Barros and I will be uploading
those djvu files on Commons and the text extracted text on Portuguese
Wikisource in a few hours

(I've talked with some users about mass upload of OCR-ed texts and no one
have made objections until now; this is like as the bot creation of stub
articles on Wikipedias for them. I hope that you all agrees with this
opinion and no one start a "radical cleanup" propose like the one on the
Volapuk Wikipedia in December 2007 ;-) . Please note that the ProofreadPage
Statistics page have more stats and graphs higher than the "all pages" one)

---
More about the dictionary and the import

The portuguese speakers at Distributed Proofreaders @ Project Gutenberg are
proofreading a dictionary and making it public avaiable as the work is done
at http://dicionario-aberto.net . The "source-code" (the words database) is
also shared http://dicionario-aberto.net/sources.html. Since it is in public
domain both on United States and in Portugal (the country of origin), I'm
going to import it to the Portuguese Wikisource. I've proposed it on
http://pt.wikisource.org/wiki/Wikisource:Esplanada/Candido_de_Figueiredo_1913days
ago and no one have made any objections to it until now.

>From A to N that dictionary have more than 85k entries and no one on
Portuguese Wikisource is opposing to import one entry per article. I've
offered to import the dictionary on the Portuguese Wiktionary (
http://pt.wiktionary.org/wiki/Wikcion%C3%A1rio:Esplanada#Candido_de_Figueiredo_1913.2C_v.C3.A3o_querer.3F)
but only one user have manifest suppor for it and two have opposed;
one of
the opposers suggested to change the "no articles were found" on
pt.wiktionary a bit, pointing to search for words on that dictionary in
pt.wikisource.

The import will be started in few weeks. I'm only waiting for more opinions
on pt.wikisource and pt.wiktionary and to the FlaggedRevs getting enabled on
pt.wikisource (since bot created articles are automatically flagged as
approved and I don't have plans to spend ten years flagging those pages by
hand :-)

On Tue, Sep 16, 2008 at 9:43 PM, Syagrius  wrote:

> > De: "John Vandenberg" 
> > A: "discussion list for Wikisource,  the free library" <
> wikisource-l@lists.wikimedia.org>
> > Objet: Re: [Wikisource-l] Changing the Wikisource main page
> > Date: Sun, 14 Sep 2008 06:03:36 +1000
>
> > A Chinese "word" has more meaning than a Spanish "word".  I dont have
> > the numbers, but the word "word" is not the same in all languages.
> > This makes words a very complex statistic.
> >
> > --
> > John
> >
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
> I may have found a very simple solution : if we agree that a chinese sign
> is a word as we understand "word", than we have to found how many sign there
> are. I made a test, and found that a chinese sign is 3 octets. The very same
> statistics tells us that the average number of octets of an article on the
> chinese wikisource is 1957. So, there are 1957/3 = 652.3 words. The
> statistics counts (on may 31, 2008) 29084 articles for the chinese
> wikisource, and 652.3*29084 gives 18.9M words for total.
>
> The only question remaining is : why the statistics page presents 29.3M as
> the number of words for the chinese wikisource ? Is that the number of
> "groups of letters" ?
>
> Anyway, if we accept the figures, we would have : 1. English : 211M words -
> 2. French : 125M - 3. Spanish : 41.8M - 4. Russian : 22.2M - 5. Chinese :
> 18.9M - 6. Polish : 18.2M - 7. Portuguese : 15.5M - 8. Deutsch : 14.4M - 9.
> Italian : 12.0M - 10. Arabic : 10.6M.
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikitech-l] FlaggedRevs setups restarting

[Luiz Augusto]

Now pt.wikisource too: https://bugzilla.wikimedia.org/show_bug.cgi?id=16365:-)

P.S.: in a near future I will send a detailed message about the
pt.wikisource plans regarding sources of works and stabilization: I'm since
July doing some tests based on the it.wikisource policy plus some
innovations ( {{textinfo}}/{{ficha}} in a custom namespace instead of
talkpage, {{edition}}/{{edição}} with some {{#ifexist}}, inputbox and
javascript tricks on all pages within {{header}}/{{navegar}}  etc)

On Sun, Nov 16, 2008 at 11:18 PM, John Vandenberg <[EMAIL PROTECTED]> wrote:

> The subdomain coordination page[1] says that FlaggedRevs has been
> requested for Hebrew[2] and Russian[3] Wikisource.  Are there any
> other projects that want to try it?  The email below suggests that
> they should be set up soon.
>
> 1. http://wikisource.org/wiki/Wikisource:Subdomain_coordination
> 2. https://bugzilla.wikimedia.org/show_bug.cgi?id=14648
> 3. https://bugzilla.wikimedia.org/show_bug.cgi?id=15006
>
> -- Forwarded message --
> From: Brion Vibber <[EMAIL PROTECTED]>
> Date: Mon, Nov 17, 2008 at 11:56 AM
> Subject: Re: [Wikitech-l] FlaggedRevs setups restarting
> To: Wikimedia developers <[EMAIL PROTECTED]>
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Daniel ~ Leinad wrote:
> >> Ok, Rob's starting to clear out some of the FlaggedRevs setup requests,
> >> now that we've cleaned up some of the configuration files.
> >>
> >> For today we've set up en.wikibooks.org as requested:
> >> https://bugzilla.wikimedia.org/show_bug.cgi?id=14618
> >>
> >> If everything's going smoothly, we'll start chugging through the rest
> >> over the coming days.
> >
> > When you continue enable FalggedRevs on remaining projects?
>
> Monday. :)
>
> - -- brion
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkkgwTIACgkQwRnhpk1wk473CQCgvkfEETfaiI6QWvrbgCKsUIkB
> kXgAoJuaGzIDaJsD5mTXy3gL/+fOiVRJ
> =6340
> -END PGP SIGNATURE-
>
> ___
> Wikitech-l mailing list
> [EMAIL PROTECTED]
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikitech-l] new extension for embedded music scores

[Luiz Augusto]

-- Forwarded message --
From: River Tarnell <[EMAIL PROTECTED]>
Date: Tue, Oct 28, 2008 at 9:18 AM
Subject: [Wikitech-l] new extension for embedded music scores
To: [EMAIL PROTECTED]


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

hello,

i have written a new extension to embed music scores in MediaWiki pages:
 https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:ABC

unlike the Lilypond extension, this uses a simple input language (ABC) that
is
much easier to validate for security.  ABC is mostly used to transcribe
Irish
trad and other simple tunes, but it recently gained support for more
advanced
features, e.g. multiple staves and lyrics.  this is supported in the
extension
using the 'abcm2ps' tool.

unlike the existing ABC extension (AbcMusic), it doesn't support opening
arbitrary files as ABC input (which is a potential security issue), and has
several additional features:

- - The original ABC can be downloaded easily
- - The score can be downloaded as PDF, PostScript, MIDI or Ogg Vorbis
- - A media player can be embedded in the page to play the media file

i believe the ABC format is suitable for transcribing the majority of scores
currently on Wikimedia projects.  although it can't handle all of them, it
is
better than the current situation.  plus, as ABC is simple, and existing ABC
scores are easily available, it's easier for novice users to contribute.

i would be interested to hear peoples' thoughts on enabling this extension
on
Wikimedia.

   - river.
-BEGIN PGP SIGNATURE-

iD8DBQFJBwL+IXd7fCuc5vIRAqG6AJ9RxKTGjJ7ywdZoesrTJWrMPtBYrACgjgDX
lIY552ilDFaVG1mLzqW1F/Y=
=7Tda
-END PGP SIGNATURE-

___
Wikitech-l mailing list
[EMAIL PROTECTED]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Extension:Collection

[Luiz Augusto]

FYI: Since the http://www.mediawiki.org/wiki/Extension:Collection is enabled
on all Wikibooks projects, I've changed the bug 15970 requesting it getting
enabled also on all Wikisource projects:
https://bugzilla.wikimedia.org/show_bug.cgi?id=15970#c2
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Green papers

[Luiz Augusto]

Anyone knows if a [[w:green paper]] from the European Union is under
copyright? I'm asking it because IMHO the following green paper can be a
great addition to Wikisource:
http://ec.europa.eu/internal_market/copyright/copyright-infso/copyright-infso_en.htm
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Inside Google Book Search] U.S. copyright renewal records available for down...

[Luiz Augusto]

-- Forwarded message --
From: Inside Google Book Search <[EMAIL PROTECTED]>
Date: Mon, Jun 23, 2008 at 2:54 PM
Subject: [Inside Google Book Search] U.S. copyright renewal records
available for down...
To: [EMAIL PROTECTED]


Posted by Jon Orwant, Engineering Manager, Google Book Search

If I handed you a book and asked whether it was in copyright or in the
public domain, you'd probably turn to the copyright page first.
Unfortunately, a copyright page can't answer that question definitively --
at best, it could tell you when the book in your hands was published, and
who owned the rights to it at that time. Ownership can change, though:
rights revert back to authors, and after enough time has passed, the book
enters into the public domain, letting people copy and adapt it as they
wish.

So how much time is "enough"? It
varies,
often depending on the country, on when the book was published, and whether
the author is living. For U.S. books published between 1923 and 1963, the
rights holder needed to submit a form to the U.S. Copyright Office renewing
the copyright 28 years after publication. In most
cases,
books that were never renewed are now in the public domain. Estimates of how
many books were renewed vary, but everyone agrees that most books weren't
renewed. If true, that means that the majority of U.S. books published
between 1923 and 1963 are freely usable.

How do you find out whether a book was renewed? You have to check the U.S.
Copyright Office records. Records from 1978 onward are online (see
http://www.copyright.gov/records) but not downloadable in bulk. The
Copyright Office hasn't digitized their earlier records, but Carnegie Mellon
scanned them as part of their Universal Library Project, and the tireless
folks at Project Gutenberg  and the Distributed
Proofreaderspainstakingly typed in every word.

Thanks to the efforts of Google software engineer Jarkko Hietaniemi, we've
gathered the records from both sources, massaged them a bit for easier
parsing, and combined them into a single XML file available for download
here
.

There are undoubtedly errors in these records, but we believe this is the
best and most comprehensive set of renewal records available today. These
records are free and in the public domain, and we hope you're able to use
them to determine the copyright status of books that interest you.

At Google, we're committed to making as many books available online to users
as possible while respecting copyright, and this is one example of that
commitment. Watch this space for more to come.

--
Posted By Inside Google Book Search to Inside Google Book
Searchat
6/23/2008 09:45:00 A
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Inside Google Book Search" group.
To unsubscribe from this group, send an email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/inside-google-book-search
-~--~~~~--~~--~--~---
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] On linking Wikisource with page images

[Luiz Augusto]

On Jan 21, 2008 2:39 PM, Gregory Maxwell <[EMAIL PROTECTED]> wrote:

> Greetings.
>
> Off and on for many months been working on a project to import a large
> collection of public domain historic scientific documents into
> Wikimedia's collection.
>
> My standing plan has been to pre-organize and catalog the collection,
> then upload the document images as DJVU files (which are utterly tiny
> compared to tiffs or pdfs) to commons including a OCRed Text layer
> (for search and copy and paste).
>
> I would then begin importing documents into Wikisource, starting with
> the OCR but eventually having a full marked up output.  From there the
> documents could be extensively linked and referenced from the other
> Wikimedia projects.

(...)

wow, nice!

Just for curiosity: these works are on what languages?
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] LabeledSectionTransclusion seens to work with FlaggedRevs

[Luiz Augusto]

Hi,

I've done a quick play on http://test.wikipedia.org with LST and FlaggedRevs
extensions. See
http://www.mediawiki.org/wiki/Extension_talk:FlaggedRevs#FlaggedRevs_.2B_LabeledSectionTransclusion_reportfor
the results.

If anyone is interested to play with FlaggedRevs + LST:

* Login/Create an account on http://test.wikipedia.org
* Go to http://test.wikipedia.org/wiki/Special:MakeReviewer . Any user is
able to grant to himself editor + reviewer privileges
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Foundation-l] Implications of IMSLP case

[Luiz Augusto]

-- Forwarded message --
From: Klaus Graf <[EMAIL PROTECTED]>
Date: Oct 21, 2007 2:06 PM
Subject: [Foundation-l] Implications of IMSLP case
To: [EMAIL PROTECTED]

Franz Liszt writes in his Myspace weblog:

"A great blow has been dealt against the world of music and of our
common cultural heritage.

The International Music Score Library Project (IMSLP) was a wonderful
site for sharing public domain music scores. They had an encyclopaedic
collection of scores which anyone could download as a .pdf file. The
site was entirely free and run by people dedicated to the art of
music.

Unfortunately the music publishers Universal Edition has threatened
the site's creator with legal action if he does not "cease and desist"
the site's activities. This has now happened. UE's threats appear to
be based on rather spurious copyright grounds. The intention is not to
protect artists' rights, but to stop people from accessing public
domain materials.

Most artists have struggled terribly in life and die broke and young.
Having ignored the artists during their lifetimes, publishers are then
able to exploit their genius posthumously. Take poor old Franz
Schubert, for instance.

UE's legal threat is a direct attack on our common musical heritage as
well as on culture in general. I believe that these public domain
works should be freely available to the public. For the most part,
IMSLP made available sores by all the greats (including my humble
self), most of whom have been long dead and are out of copyright.

There is a current trend for all our common cultural heritage to be
"privatized" and exploited by private corporations for the sole
purpose of making money. The idea that the works of Shakespeare,
Beethoven and Leonardo da Vinci (et al) should "belong" to anyone
except the people of this planet (and beyond) is outrageous.

Sadly, this trend is not restricted only to great works of art.
Ancient buildings, national parks, libraries, museums, images of works
art, and many aspects of our cultural heritage are all being devoured
by private corporations in order to fuel the interests of a small
minority of greedy individuals.

Be that as it may, I do urge you to go to the IMSLP forum, register.
learn the facts and offer support (if only by adding your voice). This
is important because this is about freedom, our common cutural
heritage - and about music! [...]

The address is http://imslpforums.org "

Source:
http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=113684180&blogID=320723275

The cease and desist letter mentions EU-protected composers but also
composers like Gustav Mahler who is dead since 1911.

There are two questions:

First: Can WMF help to re-activate IMSLP by hosting e.g. Wikiscore (or so)?

It is already possible to uload PD scores on Wikimedia Commons. See
http://commons.wikimedia.org/wiki/Category:Sheet_music

Second: Are there implications for WMF copyright policies?

The CaD-letter mentions the fact that "that under Canadian law a
judgement rendered in Europe is enforceable in Canada". If a Canadian
user uploads works on Commons from an US server like Internet Archive
(pre-1923-rule) which are PD in Canada (50 y pma) then this is allowed
by the (inappropriate) rule of Commons.

I have to quote the rule:
http://commons.wikimedia.org/wiki/Commons:Licensing#Interaction_of_United_States_copyright_law_and_foreign_copyright_law

"If material that has been saved from a third-party website is
uploaded to Commons, the copyright laws of the US, the country of
residence of the uploader, and the country of location of the
webservers of the website apply."

It clearly lacks the COUNTRY OF ORIGIN in this (inappropriate) rule.
If this country is a EU country the 70 year pma rule is in effect.

Take a Bela Bartok score published before 1923 (or 1909). Bartok died
in 1945, his works are protected in all EU countries until December
31, 2015. The score is PD in the US and Canada but the Canadian
uploader can be sued by a Canadian lawyer because the work is not free
in Europe.

WMF cannot be sued for an US court in this case because the work is PD
in the US.

But should'nt we protect the uploader when he is uploading according our
rules?

Klaus Graf

___
foundation-l mailing list
[EMAIL PROTECTED]
Unsubscribe: http://lists.wikimedia.org/mailman/listinfo/foundation-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Feedback and beta-testing from non-Wikipedia projects

[Luiz Augusto]

/me slaps "send"

On 10/17/07, Luiz Augusto <[EMAIL PROTECTED]> wrote:
>
> This thread have received some followup at wikiquality-l that aren't
> delivered to here (wikisource-l), including a proposal to host a unofficial
> test-wiki for Wikisource [1] and a reply to ThomasV [2]
>
> On regards to [1], this is IMHO a great option and I think that the
> default configuration for MediaWiki and FlaggedRevs is sufficient (list of
> configuration options for FlaggedRevs: [3]),


since my worry is related to transclusion issues from the
LabeledSectionTransclusion extension and interactions between ProofreadPage
javascript and FlaggedRevs javascript

[1] -
> http://lists.wikimedia.org/pipermail/wikiquality-l/2007-October/000359.html
> [2] -
> http://lists.wikimedia.org/pipermail/wikiquality-l/2007-October/000363.html
> [3] - http://www.mediawiki.org/wiki/Extension:FlaggedRevs#Configuration
>
> On 10/15/07, Birgitte SB <[EMAIL PROTECTED]> wrote:
> >
> > I disagree.  I think this extension will be even more
> > useful for Wikisource than Wikipedia. Text stability
> > is a more important goal at Wikisource.  This is what
> > flaggedrevs offers: stability.   I certainly hope it
> > it will work on Wikisource projects.
> >
> >
> > BirgitteSB
> >
> > --- [EMAIL PROTECTED] wrote:
> >
> > > Flaggedrevs had been designed with Wikipedia in
> > > mind.
> > > Writing an encyclopedy article is about confronting
> > > multiple
> > > points of view. During this process, the quality of
> > > an article might not always improve; the purpose of
> > > Flaggedrevs is to flag some revisions as "non
> > > draft",
> > > while still allowing users to modify the article.
> > >
> > > I do not think that this would be useful for
> > > Wikisource.
> > > A decrease of quality on a wikisource article can be
> > >
> > > agreed upon in a much more objective way.
> > > Introducing
> > > flaggedrevs will likely result on confusion and
> > > useless
> > > complexity.
> > >
> > > (I am not even sure if Flaggedrevs will solve the
> > > problems
> > > faced by wikipedia; once the community know what it
> > > really
> > > is about, they might realize technology does not
> > > replace
> > > expertise...)
> > >
> > >
> > >
> > >
> > >  Original-Nachricht 
> > > > Datum: Fri, 12 Oct 2007 22:39:04 -0300
> > > > Von: "Luiz Augusto" <[EMAIL PROTECTED]>
> > > > An: [EMAIL PROTECTED]
> > > > CC: wikisource-l@lists.wikimedia.org
> > > > Betreff: [Wikisource-l] Feedback and beta-testing
> > > from non-Wikipedia projects
> > >
> > > > (sorry for my English and for the crossposting)
> > > >
> > > > I known that the FlaggedRevs extension is under a
> > > review stage and their
> > > > development is devoted basically to the needs from
> > > the most known
> > > > Wikimedia
> > > > project. This is ok to me, no worries on it. But
> > > since more Wikimedia
> > > > projects have users watching the development of
> > > this feature, I think that
> > > > only two future official wikis for the public beta
> > > testing is
> > > > insufficient.
> > > >
> > > > Wikisource, for example, have
> > > LabeledSectionTransclusion and ProofreadPage
> > > > enabled on all of yours wikis. These extensions
> > > may have issues to work
> > > > appropriately with FlaggedRevs. Enabling these two
> > > extensions at the same
> > > > wiki devoted to the English Wikipedia beta-testing
> > > may generate some
> > > > troubles with the en.wp users that don't known how
> > > and why Wikisource have
> > > > these extensions, to exemplify with only one of
> > > the possible reactions.
> > > > Not
> > > > enabling these two extensions + FlaggedRevs at
> > > someplace may create false
> > > > hopes. And I think that knowing that issues and
> > > waiting for someone with
> > > > the
> > > > required skills to fix them when get time to work
> > > on it is more proper
> > > > instead of a community (a Wikisource wiki) gaining
> > > consensus to request
> > > > FlaggedRevs getting enabled and finding that a new
> > > nice feature brokes
> > > > another
> > > > one.
> > > >
> > > > [[:m:User:555]]
> > >
> >
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Feedback and beta-testing from non-Wikipedia projects

[Luiz Augusto]

This thread have received some followup at wikiquality-l that aren't
delivered to here (wikisource-l), including a proposal to host a unofficial
test-wiki for Wikisource [1] and a reply to ThomasV's [2]

On regards to [1], this is IMHO a great option and I think that the default
configuration for MediaWiki and FlaggedRevs is sufficient (list of
configuration options for FlaggedRevs: [3]).

[1] -
http://lists.wikimedia.org/pipermail/wikiquality-l/2007-October/000359.html
[2] -
http://lists.wikimedia.org/pipermail/wikiquality-l/2007-October/000363.html
[3] - http://www.mediawiki.org/wiki/Extension:FlaggedRevs#Configuration

On 10/15/07, Birgitte SB <[EMAIL PROTECTED]> wrote:
>
> I disagree.  I think this extension will be even more
> useful for Wikisource than Wikipedia. Text stability
> is a more important goal at Wikisource.  This is what
> flaggedrevs offers: stability.   I certainly hope it
> it will work on Wikisource projects.
>
>
> BirgitteSB
>
> --- [EMAIL PROTECTED] wrote:
>
> > Flaggedrevs had been designed with Wikipedia in
> > mind.
> > Writing an encyclopedy article is about confronting
> > multiple
> > points of view. During this process, the quality of
> > an article might not always improve; the purpose of
> > Flaggedrevs is to flag some revisions as "non
> > draft",
> > while still allowing users to modify the article.
> >
> > I do not think that this would be useful for
> > Wikisource.
> > A decrease of quality on a wikisource article can be
> >
> > agreed upon in a much more objective way.
> > Introducing
> > flaggedrevs will likely result on confusion and
> > useless
> > complexity.
> >
> > (I am not even sure if Flaggedrevs will solve the
> > problems
> > faced by wikipedia; once the community know what it
> > really
> > is about, they might realize technology does not
> > replace
> > expertise...)
> >
> >
> >
> >
> >  Original-Nachricht 
> > > Datum: Fri, 12 Oct 2007 22:39:04 -0300
> > > Von: "Luiz Augusto" <[EMAIL PROTECTED]>
> > > An: [EMAIL PROTECTED]
> > > CC: wikisource-l@lists.wikimedia.org
> > > Betreff: [Wikisource-l] Feedback and beta-testing
> > from non-Wikipedia projects
> >
> > > (sorry for my English and for the crossposting)
> > >
> > > I known that the FlaggedRevs extension is under a
> > review stage and their
> > > development is devoted basically to the needs from
> > the most known
> > > Wikimedia
> > > project. This is ok to me, no worries on it. But
> > since more Wikimedia
> > > projects have users watching the development of
> > this feature, I think that
> > > only two future official wikis for the public beta
> > testing is
> > > insufficient.
> > >
> > > Wikisource, for example, have
> > LabeledSectionTransclusion and ProofreadPage
> > > enabled on all of yours wikis. These extensions
> > may have issues to work
> > > appropriately with FlaggedRevs. Enabling these two
> > extensions at the same
> > > wiki devoted to the English Wikipedia beta-testing
> > may generate some
> > > troubles with the en.wp users that don't known how
> > and why Wikisource have
> > > these extensions, to exemplify with only one of
> > the possible reactions.
> > > Not
> > > enabling these two extensions + FlaggedRevs at
> > someplace may create false
> > > hopes. And I think that knowing that issues and
> > waiting for someone with
> > > the
> > > required skills to fix them when get time to work
> > on it is more proper
> > > instead of a community (a Wikisource wiki) gaining
> > consensus to request
> > > FlaggedRevs getting enabled and finding that a new
> > nice feature brokes
> > > another
> > > one.
> > >
> > > [[:m:User:555]]
> >
> > --
> > GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10
> > Free SMS.
> > Alle Infos und kostenlose Anmeldung:
> > http://www.gmx.net/de/go/freemail
> >
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> >
> http://lists.wikimedia.org/mailman/listinfo/wikisource-l
> >
>
>
>
>
>
> 
> Moody friends. Drama queens. Your life? Nope! - their life, your story.
> Play Sims Stories at Yahoo! Games.
> http://sims.yahoo.com/
>
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Feedback and beta-testing from non-Wikipedia projects

[Luiz Augusto]

(sorry for my English and for the crossposting)

I known that the FlaggedRevs extension is under a review stage and their
development is devoted basically to the needs from the most known Wikimedia
project. This is ok to me, no worries on it. But since more Wikimedia
projects have users watching the development of this feature, I think that
only two future official wikis for the public beta testing is insufficient.

Wikisource, for example, have LabeledSectionTransclusion and ProofreadPage
enabled on all of yours wikis. These extensions may have issues to work
appropriately with FlaggedRevs. Enabling these two extensions at the same
wiki devoted to the English Wikipedia beta-testing may generate some
troubles with the en.wp users that don't known how and why Wikisource have
these extensions, to exemplify with only one of the possible reactions. Not
enabling these two extensions + FlaggedRevs at someplace may create false
hopes. And I think that knowing that issues and waiting for someone with the
required skills to fix them when get time to work on it is more proper
instead of a community (a Wikisource wiki) gaining consensus to request
FlaggedRevs getting enabled and finding that a new nice feature brokes another
one.

[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Commons-l] On Perpetual Copyright (NYT)

[Luiz Augusto]

-- Forwarded message --
From: cohesion <[EMAIL PROTECTED]>
Date: May 20, 2007 5:21 PM
Subject: [Commons-l] On Perpetual Copyright (NYT)
To: English Wikipedia <[EMAIL PROTECTED]>, Wikimedia Commons
Discussion List <[EMAIL PROTECTED]>

Lawrence Lessig is asking people to form a response to this
(ridiculous) article in the NYT in support of perpetual copyright.

http://www.nytimes.com/2007/05/20/opinion/20helprin.html?ex=1337313600&en=3571064d77055f41&ei=5124&partner=permalink&exprod=permalink
http://www.lessig.org/blog/archives/003781.shtml

He wants people to do this collaboratively on his wiki, so I thought
it might be of some interest to people on this list. Here is the wiki
link:

http://wiki.lessig.org/index.php/Against_perpetual_copyright

Judson
[[:en:User:Cohesion]]

___
Commons-l mailing list
[EMAIL PROTECTED]
http://lists.wikimedia.org/mailman/listinfo/commons-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] future of the Wikisource

[Luiz Augusto]

A few minutes ago I've received these two messages:

From: [EMAIL PROTECTED] <[EMAIL PROTECTED]



Date: May 6, 2007 4:12 PM
Subject: [Bug 6982] Request for setting up tamil wikisource site
To: [EMAIL PROTECTED]

http://bugzilla.wikimedia.org/show_bug.cgi?id=6982


[EMAIL PROTECTED] changed:

  What|Removed |Added

CC||[EMAIL PROTECTED]
Status|NEW |RESOLVED
Resolution||WONTFIX




--- Additional Comments From [EMAIL PROTECTED]  2007-05-06 19:12 UTC
---
Tamil wikisource is undergoing discussion at langcom, .
please
re-open this bug when a decision is reached to create it.



From: [EMAIL PROTECTED] <[EMAIL PROTECTED]



Date: May 6, 2007 4:01 PM
Subject: [Bug 7855] Creation of nds wikisource
To: [EMAIL PROTECTED]

http://bugzilla.wikimedia.org/show_bug.cgi?id=7855


[EMAIL PROTECTED] changed:

  What|Removed |Added

CC||[EMAIL PROTECTED]
Status|NEW |RESOLVED
Resolution||WONTFIX


On 5/4/07, jkbwiki <[EMAIL PROTECTED]> wrote:


 Just some remarks to the art of discussion and decision here.

In March/April there were some mail concernig the wikisource, the future
of wikiosurce (multilingual, wikisource.org) and new subdomains.

Although I work in wikisource.org since 2004 and although I am an admin
there since 2005, I saw and I read some points the first time in my wiki
life. There was no word of announcement or discussion of this matter on the
pages of the multilingual wikisource, never, although it concerns this
domain.

So, the proposals, that everything what has to do with new subdomains
should be put in the hands of somebody else, but not the wikisource.

Nice. The multilingual wikisource did in the past manage the creation of
new subdomains, after we had a contact to the users there. Now, there is a
not nearly specified proposal, some incubation domain will do. Fine. Fine,
if it works.

But doesn't seem to work. The discussion ended, nobody concerns, nobody
tries to do something. And the Tamil wikisource request and another one are
still waiting for a solution. Since months, since nearly one year. Do you
think that the users are so strong and so good prepared fot the shit here,
that they will wait another half a year and then start to work again??? I am
sure, we lost not only some users, but we lost two subdomains in the last
four weeks.

I tried to keep the domain of wikisource.org running in the past, but now
I must resignate. Some people announce some new fine ideas, they take the
competences away, without saying who will do it in the future. I am not like
to act there as a idiot, I am not one.

You will have to recognize, that such acting leads to a loss of users and
subdomains. You will have to recognize that the wikisource subdomains have
to learn something else than the wikipedia or wictionary subdomains.
Obviously, yaou have to recognize this in the future.

It is not a good feeling to me to write these sentences after three years
of wotking here, but the development of the WS did hurt  me.

Thanks.

-jkb-




___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Foundation-l] A successful request not yet fulfilled

[Luiz Augusto]

Hi

On 4/3/07, Birgitte SB <[EMAIL PROTECTED]> wrote:


Luiz

Perhaps it is the language barrier, but I am not sure
about what you are saying entirely.

I think you are saying that there is a continued need
for [[:oldwikisource:]] outside of staring new
wikisources.  Of course I agree with you in that.  But
as I said, not everyone agrees with this.  I cannot be
certain of everyone I talked to about this (it was not
recently), but timichal is one person who talked of
merging content into incubator and the conversation
ended with us agreeing to disagree about the issue.  I
do not believe he was talking about the year 2859.  I
am not entirely against the idea of merging the test
wiki process, but I am against handing off that
process without some seperate conditions for
Wikisources.  First that related languages should be
required to attempt to work together to conserve
resources (i.e. in the line of de.WS hosting Low Saxon
and en.WS hosting Middle English) before being given a
test wiki.  Secondly that test wikis which do not
"pass" should be imported into [[:oldwikisource:]].



Don't worry, I'm en-1 to read and en-0,5 to write. I understood what you
believe. The "With long term you is trying to say "starting at the 2859
year"?" isn't directed to you, but to the people that have said it to you.
The "you" is only because *you* that have wrote it on the message :) And the
"2859 year" is only a irony.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Foundation-l] A successful request not yet fulfilled

[Luiz Augusto]

On 4/2/07, Birgitte SB <[EMAIL PROTECTED]> wrote:


Due to past conversations I have had with people
involved with incubator, I read the comment about
"merging processes" differently than you did.  Perhaps
I am mistaken, and that is not what was meant in this
case.

However there are people who have been clear with me
that they think  [[:oldwikisource:]] should be
completely merged into [[:incubator:]] in the long
term.



With long term you is trying to say "starting at the 2859 year"? If yes, it
is fine to me. The world have more than 5,000 languages and the Wikimedia
Foundation at this time have 63 Wikipedias, the most google-friendly
project, with less than 100 articles [1]. I think that the [[:incubator:]]
is a temporary hosting, not a hosting for someone trying to found more
people speaking on a specific language that have Internet access, knows
something related to free culture, historical texts, OCRing and wiki culture
like [[:oldwikisource:]] is for some languages.

Personally I don't like to see the process of

starting new Wikisources taken over, because outside
people simply fail to appreciate the reality of
wikiSOURCE, where the content already exists in
tangible form (with corresponding dialects and
orthographies already pre-determined for each edition
of a text).  Processing requests at meta has led to
people being encouraged to start a new wikisource for
a variation of a language without ever trying to work
in the existing wiki (or even talking to them). [1]
The people I have spoken to from incubator also seem
unable to see the intrinsic differences between a
wikisource and a wikipedia.  From what I can see they
are planning a one-size fits all process, with no
differences in handling based on projects.  Despite
the fact that there are strong arguments for having
one Wikisource where there are several Wikipedias with
related languages.  If plans have changed, or I am
simply mistaken, please correct me.

[1]

http://meta.wikimedia.org/w/index.php?title=Requests_for_new_languages/Ancient&diff=prev&oldid=360204

The full page seems to have been lost on meta, so I
linked one of my contributioins there



My propose is a attempt of a {{merge}} between the current Wikisource
Multilingual policy + langcom policy + proposed policies to the Wikisource
Multilingual [2].

The problem is the pun "Wikimedia" naming the foundation. The press
generally ignores the others projects due to it. Google and Yahoo! sometimes
aren't friendly with theirs search results for non-Wikipedia projects,
specially for non-English languages. The Wikimedia Foundation tries to do
attention to all projects, but sometimes Wikipedia suck all of their energy
due to the media coverage to Wikipedia and the lack of media coverage for
non-Wikipedia projets. The result: users with only basic knowledge thinks
that Wiktionary is a mini-Wikipedia with the same rules and needs, Wikibooks
is a Wikipedia for big articles and the Wikisource is the big trashcan for
texts that newbies adds to the Wikipedia articles.

Moving the requests to the Meta-Wiki is IMHO the best solution because:

* You don't need to someone remeber the existence of a wiki that may have
requests for new languages placed on then, neither to prays to someone check
that page/wiki regularly during the small amout of seconds per month that
Wikipedia isn't sucking all attention
* You can simply vote as against on meta if no one is placing text-units on
the correct place (specially if something on [2] may give a chance to move
from proposal to policy)
* You stop the behaviour "let's go to the [[:oldwikisource:]] only to vote
for new languages and to delete old stuff" specially because you can vote as
against if no one is adding texts neither in the right place neither in the
wrong place, again specially if something on [2] forcing to that wiki
having someone rather than Volapuk and India national languages speakers
adding periodically new texts.


[1] - http://s23.org/wikistats/wikipedias_html.php

[2] -
http://lists.wikimedia.org/pipermail/wikisource-l/2007-April/000224.html
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Foundation-l] A successful request not yet fulfilled (was Language Prevention Committee created)

[Luiz Augusto]

Hi, thanks for your reply. Now the discussion continues on
http://wikisource.org/wiki/Wikisource:Scriptorium#Wikisource:Language_domain_requests_versus_m:Meta:Language_proposal_policy


On 4/1/07, Jesse Martin (Pathoschild) <[EMAIL PROTECTED]> wrote:


Hello,

The developers usually want approval by the subcommittee or the board
before creating a new language subdomain. The language subcommittee
has developed the language proposal policy
 to provide a clear
step-by-step policy on getting approval, but the Wikisource creation
policy is not equivalent.

Unfortunately, this means that most or all requests on the
multilingual Wikisource do not fit the requirements and will need to
be re-opened under the language proposal policy, in particular
regarding the use of arguments rather than simple votes.

Fortunately, the existence of an active test project (whether on the
incubator or the multilingual Wikisource) will mean that the request
can be fast-tracked if there are insufficient arguments against in the
new request. Requests for more projects in a language already
established in another project can be fast-tracked even further.

I apologize for the delay and inconvenience; once the new process is
fully settled in there should be much less hassle.

Yours cordially,
Jesse Martin (Pathoschild)

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Foundation-l] A successful request not yet fulfilled (was Language Prevention Committee created)

[Luiz Augusto]

Thanks for the answers, Pathoschild and GerardM. I know that the process to
*request* to create a new Wikisource (and to request the creation of a new
Wikinews or a new Wikiversity) have theirs particularities. But unfortunately
I'm unable to found any documentation/policy page that explains if the
langcom need to do a final word on these requests or not. Now I have five
answers to this:

* The http://langcom.wikimedia.org/wiki/Main_Page saying "a clear
step-by-step policy (based on quantitative indicators) for evaluating the
feasibility of new language wikis, with an automated procedure for project
development;" (with no distinctions between projects)
* The http://meta.wikimedia.org/wiki/Meta:Language_proposal_policy saying
"The proposal is to open a new language edition of an existing Wikimedia
project that does not already exist (see the complete list of Wikimedia
projects)" (with no distinctions between projects)
* GerardM ignoring my specific question and doing a [[Ad nauseam]], followed
by some [[Ad nauseam]] answers criticizing theirs statments (my Gmail trash
is unfortunately queasy with a large amount of [[Ad nauseam]]s)
* A (nice) on-topic reply made by Pathoschild with their POV pointing
to a paragraph
originally writen by me [1] based on the Wikisource Multilingual wiki policy

* The Wikisource creation policy itself.

Please langcom members, discuss internaly and release to the public if their
committee need to do a final word on requestions for creation for new
Wikisource/Wikinews/Wikiversity wikis or if theirs policy requirements to
prevent a new wiki going to be created with 0 active users and 0 pages is
sufficient to make a bugzilla request. And please someone write a few lines
to be cuted-and-pasted at wikisource.org/wiki/ explaing about the possibles
reasons for the delays on the creation for new Wikisources wikis.

And please, related to the Tamil Wikisource specific situation: why this
don't have yet a wiki? Technical problems? Just no one with free time to set
this wiki up? Just others than me with the same questions related to the
"final word"? No sufficient pages at [[:oldwikisource:]] "incubator"? (if
the problem is the last one, the most recent Wikisource, mk.wikisource, has
been created with only the "Main page" at the "incubator" and now have 308
"articles" apart the last edit on that wiki is from 27 February from this
year).

Please keep on topic on replies. Please. Please.

[1] 
http://meta.wikimedia.org/w/index.php?title=Requests_for_new_languages&diff=prev&oldid=527531
, based on a previous
http://meta.wikimedia.org/w/index.php?title=User_talk:Pathoschild&diff=next&oldid=481667


On 4/1/07, Jesse Martin (Pathoschild) <[EMAIL PROTECTED]> wrote:


Hello,

The process on the multilingual Wikisource domain is not covered by
the language subcommittee yet; you'll notice that there is a redundant
process at < http://meta.wikimedia.org/wiki/RFL#Wikisource>. The
secondary processes will eventually be merged into the Meta process
(probably a combination of both, not simply removing one), but we want
to make sure that the latter is working at a reasonable efficiency
first. As your sarcasm indicates you already know, we've had some
difficulty starting up.

I would suggest continuing to follow the Wikisource process, since the
request is there. This process is the same as it was on Meta until the
reform: file a bug request following community approval, and it might
be done eventually. I'm sorry that we can't do anything more at the
moment, but we're busy catching up on requests (for many projects,
*not* only Wikipedias) that were filed through the subcommittee
process in the transitional period.

Yours cordially,
Jesse Martin (Pathoschild)

(This message is not an official statement of the language subcommittee.)


> From: "Luiz Augusto" <[EMAIL PROTECTED]>
> Hi
>
> There is a successful and old request for opening a new wiki not yet
> fulfilled. Language prevention/creation committee/subcommittee or
> whatever/anything else, please forgive the MessagexXX.php paranoia and
see
> requests for non-Wikipedias wikis a while.
>
> # [[:oldwikisource:]] have a [[Wikisource:Language domain requests]]
page.
> # This page have at least one successful request for a new Wikisource
wiki:
> Tamil Wikisource (ta.wikisource)
> ## This have a large community support:
>
http://wikisource.org/w/index.php?title=Wikisource:Language_domain_requests&oldid=215092#Domain_requests_.28ta.wikisource.org.29
> ## This have "incubator" pages:
http://wikisource.org/wiki/Category:Tamil
> ## This have a bugzilla request:
> http://bugzilla.wikimedia.org/show_bug.cgi?id=6982
> ## The MessagesTa.php is avaiable at MediaWiki SVN repository
> ## There is someone interested on editing in this non-existi

[Wikisource-l] A successful request not yet fulfilled (was Language Prevention Committee created)

[Luiz Augusto]

Hi

There is a successful and old request for opening a new wiki not yet
fulfilled. Language prevention/creation committee/subcommittee or
whatever/anything else, please forgive the MessagexXX.php paranoia and see
requests for non-Wikipedias wikis a while.

# [[:oldwikisource:]] have a [[Wikisource:Language domain requests]] page.
# This page have at least one successful request for a new Wikisource wiki:
Tamil Wikisource (ta.wikisource)
## This have a large community support:
http://wikisource.org/w/index.php?title=Wikisource:Language_domain_requests&oldid=215092#Domain_requests_.28ta.wikisource.org.29
## This have "incubator" pages: http://wikisource.org/wiki/Category:Tamil
## This have a bugzilla request:
http://bugzilla.wikimedia.org/show_bug.cgi?id=6982
## The MessagesTa.php is avaiable at MediaWiki SVN repository
## There is someone interested on editing in this non-existing exactly now:
http://wikisource.org/w/index.php?title=User_talk%3A-jkb-&diff=215093&oldid=214978
## I've asked about it on the langcom wiki yesterday but no one
apparentlyhave read it.

And, if the language prevention/creation committee/subcommittee or
whatever/anything else isn't happy to increase the current amount of
Wikimedia wikis, I found a good solution: open the ta.wikisource and close
the ang.wikisource. No, no one have deleted the MessagesAng.php from
subversion, this apparently has never created, but you can find a vote to
close that wiki with large community support at:
http://meta.wikimedia.org/wiki/Proposals_for_closing_projects/Closure_of_Old_English_Wikisource

Best regards
[[:m:User:555]]
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Wikisource] How many books (was: 200k)

[Luiz Augusto]

On 3/23/07, Lars Aronsson <[EMAIL PROTECTED]> wrote:


Luiz Augusto wrote:

> Wikisources are going to reach 200 000 articles (now all 52
> Wikisources have 190 865 articles)

Wikisource is in bad need to be restructured.  You cannot digitize
books and talk about 200,000 articles.  What does that tell
anybody about the size?  The number of articles is a size
measurement for an encyclopedia or dictionary, but not for a
collection of digitized books.  How many books do we have?



The number of articles doesn't help to determine the number of books, this
is true. But Wikisource isn't only books. Wikisource have also a large
amount of texts that never constitute a book.

 How

many printed pages?  How can I download one book?  Some people
want to download the entire French Wikipedia but very few can be
interested in downloading the whole of Wikisource.  The book
should be the unit, not the library.



Portuguese and Spanish Wikisources have the "Print Version" project [1],
based on the Print Version from the English Wikibooks [2] (English Wikibooks
releases .pdf files containing a full book but Portuguese and Spanish
Wikisource have rejected to duplicate the current avaiable material on
another file type). This may help to download a entire book for works that
are books. But MediaWiki have some limitations for general printing [3] and
a external tool to export pages from a category and convert then in a
downloadable file may be more helpfull.

This isn't the main problem for me. I really rate the Protection policy used
in the most majority of Wikisources to protect the integrity of a text.
Wikisource is powered by the MediaWiki, a *wiki* content managing system. A
fully proofread text is a fully proofread text, not a dead page that never
more receive a new category schema [4] or a interwiki for translation or a
annotation or a link pointing to some Wikipedia/Wiktionary article for some
specific word or a free image found in some edition that helps to understand
the text or (...). I'm anxious to see new developments in the "stable
version".

Anyway, the number of "articles" is a valid number of general development.
These numbers are something like the total pages from a book that a publishing
house have released to the general public. You know the total number of
"paper" used at Wikisources but you don't know yet the total number of books
and others publications that these publishing house have released.

(sorry for my poor English in a long message)

[1] <
http://pt.wikisource.org/wiki/Wikisource:Vers%C3%A3o_para_impress%C3%A3o>
and <http://es.wikisource.org/wiki/Wikisource:Versi%C3%B3n_para_imprimir>

[2] <http://en.wikibooks.org/wiki/Wikibooks:Print_versions>

[3] Some of these listed by a en.ws user at <
http://en.wikisource.org/wiki/User:Newmanbe/Printing_works>

[4] <
http://lists.wikimedia.org/pipermail/wikisource-l/2007-February/000163.html>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] [Wikisource] 200k

[Luiz Augusto]

Wikisources are going to reach 200 000 articles (now all 52 Wikisources have
190 865 articles) [1]. Are in plans of anyone to write a Press release? The
"war" for the second position between French and Spanish wikis and for the
fourth position between Portuguese and Chinese wikis is promising :)

[1] http://s23.org/wikistats/wikisources_html.php
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Commons-l] recent legal issues in France

[Luiz Augusto]

-- Forwarded message --
From: David Monniaux <[EMAIL PROTECTED]>
Date: Feb 28, 2007 8:04 PM
Subject: [Commons-l] recent legal issues in France
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], Wikimedia Commons Discussion List <
[EMAIL PROTECTED]>

Two legal changes in France, one working for us, one against us:

1) Wartime copyright extensions

Before 1995, the normal duration of copyright in France was 50 years
after the death of the author, or after publication in the case of
collective or anonymous works. However, there were special extensions
meant to compensate the world wars. Due to European "harmonization" of
laws, the normal duration was extended to 70 years (following Germany, I
think). The lingering question was whether the war extensions still
applied. The French Court of Cassation
 said they didn't (at
least in the case where extensions didn't start to elapse before 1995,
but those who did will be over in 2009 or so). A yet unsolved question
is the case of the 30 year extensions for authors killed in action (the
only major author that comes to mind is Antoine de Saint Exupéry
, of /Little
Prince/ fame).

Wikimedia France is having its counsel investigate the exact
implications of this evolution. In any case, it seems that the situation
is better for us.

For the curious, the relevant articles are in the Code of intellectual
property, L123-1, -8, -9 and -10, and in rulings 280 and 281 of the
Court of Cassation, first civil chamber, for 2007.

2) Repression of 'happy slapping'

The French parliament has just passed a law aimed at preventing
delinquence. Among a gazillion of measures on diverse issues more or
less related to delinquence, the Senate passed an amendment aimed at
repressing 'happy slapping'. 'Happy slapping' is basically youngsters
beating up people, filming the scene with cell phones, and broadcasting
the movie in order to humiliate the victim.

Unfortunately, the wording of the amendment was broad, and basically
criminalized against filming or broadcasting the film of certain kinds
of violences, unless one does so for gathering evidence for legal
proceedings, or as part of the normal work of a *profession* whose goal
is to inform the public.

In short, they have outlawed normal citizens (not professional
journalists) video reporting on certain kinds of violences. This could
prove a problem for Wikipedia, Commons and Wikinews contributors; for
instance, if reporting on police violence.

Wikimedia France contacted officials, who claimed that this was not the
intent; the only target was happy slapping, and that if we had called
them earlier they would have the amendment altered.

Now, several good things can still happen :
* The opposition has had the law sent for constitutional review. It is
possible that this article will get constitutional "reservations of
interpretation" that will clarify the situation of non professionals.
* The government will perhaps clarify the issue; that is, make it clear
that the intent of this article is not to punish non professionals
reporting on events with a goal to inform the public.
* Even if the law is accepted as is, prosecutors may get orders not to
enforce it against non professionals who merely meant to inform.
* Judges may also decide the same, if they feel there is a superior need
of freedom of speech.

Finally, do not forget that there are legislative elections 3 months
away or so, and this law may go 'pschitt' if the current opposition wins.

In any case, I don't expect actual prosecution of "citizen journalists",
though I envision as a credible possibility that overzealous police may
want to get rid of undesirable reporters using this law. Even if you are
prosecuted or sentenced in the end,  being taken into police custody is
intimidating enough.

Wikimedia France tries to get informed on that issue.


___
Commons-l mailing list
[EMAIL PROTECTED]
http://lists.wikimedia.org/mailman/listinfo/commons-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] WAP Wikisource/ Live mirroring

[Luiz Augusto]

On 2/1/07, Birgitte SB <[EMAIL PROTECTED]> wrote:


What is the problem?  I'm not sure what WAP is (is it
something for phones?) so I don't understand why there
is a problem.

BirgitteSB



If this don't overload the servers, no problem :)
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] WAP Wikisource/ Live mirroring

[Luiz Augusto]

Hi

Acessing es.wikisource I found a link to a WAP version at their Main Page. I
tested some URLs and... WAP version is avaiable also for others languages!
This is new only to me?

http://es.wikisource.7val.com/
http://pt.wikisource.7val.com/
http://en.wikisource.7val.com/
http://fr.wikisource.7val.com/
http://de.wikisource.7val.com/

... and this may work for more languages

But there is a problem: apparently this is just another live mirroring from
Wikimedia projects
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikisource-l