Hello,
I am trying to do something where I can redirect the user to different
pages on the parts of the picture they select. So is it possible to do this
on a single picture or would I need different pieces of the picture and
attach each picture as a hyperlink? If I need to do it in pieces (second
option) what would be the best way to stitch those pieces so that they
appear as a single picture to the user?
Is there any other way?
I would really appreciate any comments/suggestions/help on this matter.
Thank you,
Sincerely,
Shrenik Shah
I just discovered an extremely strange error when parsing the following:
==Advertisements==
All one will get when trying to create that section heading will be a blank heading (though any table of contents will show the proper heading.
I'm not sure what causes it, and I have verified it exists on MW 1.19, 1.20, and 1.21.
Based on all feedback gathered during the RfC about a possible
inter-project links interface [1], User:Tpt has created a content card
prototype (image: [2])
To activate it, follow these steps:
1. Go to your common.js file. For a user named "Test" in English
Wikipedia, it would be: https://en.wikipedia.org/wiki/User:Test/common.js
2. Modify it and paste this line: mw.loader.load('//
www.wikidata.org/w/index.php?title=User:Tpt/interproject.js&action=raw&ctyp…'
);
3. Save and go to any Wikipedia page
4. You should see an icon next to the article title, if you don't,
refresh your browser cache. *Instructions*: Internet Explorer: hold down
the Ctrl key and click the Refresh or Reload button. Firefox: hold down the
Shift key while clicking Reload (or press Ctrl-Shift-R). Google Chrome and
Safari users can just click the Reload button.
What it does:
- It displays an icon next to the article title
- When you hover your mouse over the icon it shows a *content card*.
- The content card displays information from Wikidata: label, image,
link to Commons gallery, and link to edit Wikidata.
What it is supposed to do in the future when Wikidata supports sister
projects:
- It will display contents or links to sister projects
Please leave your feedback on the Request for comments, thanks!
http://meta.wikimedia.org/wiki/Requests_for_comment/Interproject_links_inte…
Cheers,
Micru
[1]
http://meta.wikimedia.org/wiki/Requests_for_comment/Interproject_links_inte…
[2] http://commons.wikimedia.org/wiki/File:Content-card-prototype.png
Hi Jane, hi Alex,
Yes, I agree with you that a centralized Wikisource would be quite
meaningful, specially now that projects like Wikidata have shown that it is
possible to have both localization and centralization living in harmony.
I know that Doug (cc'ed) did some experiments with this goal in mind, but I
have no idea how far he is now.
Apart from the technical challenge, it also worries me the social aspect.
Wikisourcerors from each Wikisource and have lived in isolation from each
other for a long time. How would be a reunification perceived by the
different communities? Would it be something wanted?
Andrea and me have the pending task of contacting the communities, so this
is something that we should bring up among other important topics (like the
creation of a Wikisource User Group:
http://meta.wikimedia.org/wiki/Wikimedia_User_Groups)
The OPW is a grant program for students similar to Google Summer of Code
focused on helping bring more female contributors to open source projects.
https://www.mediawiki.org/wiki/Outreach_Program_for_Women
So yes, it is a gendergap project, but we can offer wikisource-related
projects as we did with GsoC.
David --Micru
PS: Some of those plates are quite scary... I love them :)
On Sat, Jun 1, 2013 at 4:12 AM, Jane Darnell <jane023(a)gmail.com> wrote:
> Hi David and Alex,
> I am also starting to think that one project would be a whole lot
> simpler, especially given the lack of cross-referencing between
> projects, which would be nice to have in the wikisource of many
> popular wikipedia languages - especially for translated texts.
>
> Years ago, while researching an urban legend, I took some photographs
> of the engravings and the table of contents of a Latin book and its
> Dutch translation a century later. At the time I was toying with the
> idea of cross referencing the stories but realized quickly there was
> no way to do this on Wikisource. I put my scans here:
>
> http://commons.wikimedia.org/wiki/Category:Observationes_Medicae_by_Nicolae…
>
> Wouldn't it be easier to have just one Wikisource and have all
> language-related information reside in interface layers and for the
> language of texts, the category structure? This would make the Lua
> interface easier to achieve and work on.
>
> David, do you mean by "Outreach Program for Women" to refer to a
> specific wikisource project other than the general ones we have for
> the gendergap project?
>
> Jane
>
> 2013/5/31, Alex Brollo <alex.brollo(a)gmail.com>:
> > I agree fully Micru.
> > Obviously, my dream is something much simpler and clear-cut: a unique
> > wikisource for all languages, since an unique project for any textual
> media
> > is needed IMHO just as a common project for any non-textual media is
> > running: Commons; and a common project for data now exists: Wikidata.
> >
> > And now, let's go to explore Lua a little bit more.... I presume, that
> > mw.loaderData() can read a table of Lua functions too, if I understand
> Lua
> > table features. So, shared modules could perhaps be hosted into one data
> > module only. Let's try ....
> >
> > Alex
> >
> >
> >
> >
> > 2013/5/31 David Cuenca <dacuetu(a)gmail.com>
> >
> >> Hi all,
> >>
> >> After a talk with Brad Jorsch during the Hackathon (thanks again Brad
> for
> >> your patience), it became clear to me that Lua modules can be localized
> >> either by using system messages or by getting the project language code
> >> (mw.getContentLanguage().getCode()) and then switching the message. This
> >> second option is less integrated with the translation system, but can
> >> serve
> >> as intermediate step to get things running.
> >>
> >> For Wikisource it would be nice to have a central repository (sitting on
> >> wikisource.org) of localized Lua modules and associated templates. The
> >> documentation could be translated using Extension:Translate. These
> >> modules,
> >> templates and associated documentation would be then synchronized with
> >> all
> >> the language wikisources that subscribe to an opt-in list. Users would
> be
> >> then advised to modify the central module, thus all language versions
> >> would
> >> benefit of the improvements. This could be the first experiment of
> having
> >> a
> >> centralized repository of modules.
> >>
> >> What do you think of this? Would be anyone available to mentor an
> >> Outreach
> >> Program for Women project?
> >>
> >> Thanks,
> >> David Cuenca --Micru
> >>
> >> _______________________________________________
> >> Wikisource-l mailing list
> >> Wikisource-l(a)lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> >>
> >>
> >
>
> _______________________________________________
> Wikisource-l mailing list
> Wikisource-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>
--
Etiamsi omnes, ego non