Last modified: 2014-09-12 09:43:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48522, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46522 - Multilingual SemanticMediaWiki
Multilingual SemanticMediaWiki
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 47736
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-25 01:17 UTC by Quim Gil
Modified: 2014-09-12 09:43 UTC (History)
13 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Quim Gil 2013-03-25 01:17:41 UTC
Siebrand proposes:

Semantic MediaWiki is cool, but it would be even cooler if it was multilingual-capable out of the box. Integrate it with Translate extension.

http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Multilingual_SemanticMediaWiki

I haven't found any enhancement request, so here goes one. Does this proposal make sense? 

Also would it fit as a Google Summer of Code Project, keeping a student busy during 12 weeks? If all this makes sense this proposal would still need at least one mentor.
Comment 1 Jeroen De Dauw 2013-03-25 01:24:27 UTC
Any more details on how one would make SMW multilingual? Or how integration with Translate would work?
Comment 2 Quim Gil 2013-03-25 01:44:48 UTC
Not yet, the same entry at the wiki page reads:

"Disclaimer: This a long list proposal. The team will assess this long list on 2013-03-28 and update it with more specific information, or retract it."

I asked Siebrand please please to post a list of potential GSOC 2013 projects. He said he only had time to list ideas that would be reviewed next Thursday at the WMF Language team meeting. I'm grateful he did (our GSOC deadline is Friday), and I'm trying to help getting more feedback from other sources. In this case it made sense to ask the SMW maintainers here.

Thank you for your understanding.
Comment 3 Quim Gil 2013-03-28 23:16:49 UTC
There are more details now at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Multilingual_SemanticMediaWiki

Some of the steps could be:

* Fix the issues that prevent full localisation of semantic forms.

* Enhance Special:CreateForm and friends to create forms that are already i18ned with placeholders and message group for Translate extension.
    
* Make it possible to define translation for properties and create a message group for Translate extension
    * There are lot of places where properties are displayed: many special pages, queries, property pages. Some thinking is required to find out a sensible way to handle translations on all these places.

-------

Question: are there existing bug reports about this issues? If so please let's make them blockers of this one in order to provide more information to potential volunteers.

This is a proposal coming from the WMG Language team but it needs the buy-in and help from the SMW maintainers before I can move it to the Featured section, where it will be explicitly promoted to potential GSOC & OPW candidates.
Comment 4 Jeroen De Dauw 2013-03-28 23:23:45 UTC
> Question: are there existing bug reports about this issues?

Not AFAIK.

The two first points seem to be SF specific. The other two indeed need more thought, and need further specification. I suspect they will not be easy to implement.
Comment 5 MWJames 2013-03-28 23:41:20 UTC
> * Make it possible to define translation for properties and create a message
> group for Translate extension
>     * There are lot of places where properties are displayed: many special
> pages, queries, property pages. Some thinking is required to find out a
> sensible way to handle translations on all these places.

My 3 cents, since SMW needs to function with or without a Translate extension in mind, the translated text should probably go into a separate blob table with a property tracking id, language key, and its translation. Some setter/getters to catch the representation based on the language key returning a Message object.

Also some enlightenment about how and what the Translate extension actually does and how it would interact might be helpful (can't really picture the Translate extension).

How does the ULS would come into play with this?
Comment 6 Quim Gil 2013-03-28 23:51:21 UTC
You can see the Translate extension in action at 

https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example

https://www.mediawiki.org/wiki/How_to_contribute

and many other pages at http://mediawiki.org

Look at the Edit views to see the tags inserted. Then there is a backend for admins and translators to notify new translatable versions of a page, see % of completion per language and so on.
Comment 7 MWJames 2013-03-29 00:15:47 UTC
(In reply to comment #6)
> You can see the Translate extension in action at 
> 
> https://www.mediawiki.org/wiki/Help:Extension:Translate/
> Page_translation_example

Fair enough.

<< Example
Fréttinga is a small municipality in MungoLand, located on the [[Located at::BaMungo island]].
It hosts a population of about 400 people. It has some agriculture and fishing.
Tourists like to visit it in the summer time.
...
>>

Within the text you have some annotations (such as [[Located at::BaMungo island]]), what would the Translate extension do now? Provide an event to catch the translation? Should SMW look in the parserOutput for something that says "I have a translation, please handle me differently?"!

Should SMW look for <translate></translate> and somehow find out about the original and the translated copy.

Should free-text annotations (as above) be considered at all or should the focus be on SpecialProperties [1] only?

This is what I meant by "can't really picture the Translate extension" mainly about how the Translate extension and SMW should work together and what is the expected outcome.

[1] http://www.semantic-mediawiki.org/wiki/Special_properties
Comment 8 Niklas Laxström 2013-04-01 18:48:17 UTC
Translate extension would provide the translation interface. SMW would register a message group(s) to Translate. One of these groups would contain all the *name* of the properties known to exist in the wiki.

The above part is easy. The harder part is to use those translations in various places. Most cases are probably easy to change, but there can be a lot of them and some of them might be difficult because of caching or other issues.

I would leave inline syntax out of scope. There is enough to do with templates and forms.

To give you some idea: Something like this but automated and integrated to Translate (I've spent considerable time doing these by hand):
Forms: http://tieteentermipankki.fi/mediawiki/index.php?title=Lomake:K%C3%A4site&action=edit
Templates: http://tieteentermipankki.fi/mediawiki/index.php?title=Malline:K%C3%A4site&action=edit (only partially i18ned)
Comment 9 Jodi Schneider 2013-04-19 20:52:08 UTC
> Some of the steps could be:
> 
> * Fix the issues that prevent full localisation of semantic forms.

Is there a list of known issues? Or how would I go about tracking these down?
Comment 10 Quim Gil 2013-04-22 16:36:06 UTC
Background: Jodi is interested in this project in the context of Google Summer of Code. However, so far there is no unanimous opinion between Semantic MediaWiki maintainers.

Either we get a fast agreement or Jodi should go for another project proposal, since GSoC deadlines are close.
Comment 11 Yaron Koren 2013-04-22 17:17:08 UTC
I don't think the issue here is unaminity - just lack of communication. I have the greatest respect for the Translatewiki/Translate extension developers, and I think this project makes a lot of sense in theory, but I don't think they've explained enough yet about how this project would work, either here or on the SMW mailing list(s), for it to happen for this GSoC, given the upcoming deadline. I do hope we can have a full discussion about it soon, ideally on the semediawiki-devel list.
Comment 12 Niklas Laxström 2013-04-24 07:29:58 UTC
Thanks Yaron. Can you help me by pointing what questions I should answer wrt to the integration. Can you also start the discussion on smw-devel or should I or Jodi do that?
Comment 13 Yaron Koren 2013-04-24 11:55:00 UTC
Hi Niklas - ideally you can do that, by sending an email fully describing this idea: what the Translate extension does, how it could be used by SMW and SF, what prevents that usage from happening now, and maybe how long you think it would take to fix.
Comment 14 vladjohn2013 2013-12-01 15:47:22 UTC
Hi, this project is still listed at  https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Multilingual_SemanticMediaWiki 

Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the "Featured projects" section if it has community support and mentors.
Comment 15 Rishi Mittal 2014-03-18 17:18:11 UTC
Hi everyone , 

The project is not clear , can someone tell me is it part of GSOC-2014 or not.

thanks
Rishi Mittal
Comment 16 Andre Klapper 2014-03-18 18:25:28 UTC
See comment 11 (I guess).
Comment 17 Nemo 2014-03-19 11:09:20 UTC
(In reply to Rishi Mittal from comment #15)
> The project is not clear , can someone tell me is it part of GSOC-2014 or
> not.

Yes, it is; we also clarified the description recently. Please ask questions on the project in public, for instance on this bug; or on the talk page of your proposal as soon as you create it (which should be immediately, even if it's incomplete and you have to work on it).
Comment 19 Quim Gil 2014-09-12 09:43:01 UTC
FOSS OPW round 9 is about to start. Do you still want to feature this project at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Multilingual_Semantic_MediaWiki and are there mentors available?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links