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
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@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@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
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_Nicolaes...
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@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@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@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
wikisource-l@lists.wikimedia.org