From: Markus K. <ma...@se...> - 2012-10-18 08:06:46
|
Dear SMW users & developers, we enjoy an awesome internationalisation support from translatewiki.net, which ceaselessly translates MW extensions (and more) into a huge number of languages. To work smoothly, this also needs some help from the user/developer community, since translators are sometimes not sure about how a message is used (e.g. the word "view" could mean many things, and needs to be translated differently in each case). If there is a problem, "Open Requests" are created [1] (supported by SMW :-). Currently, there are 5 open requests related to SMW, Validator, SRF, and Semantic Expressivity [2] which could use some looking into. More generally, the translatewiki.net community could always use the help of users who are familiar with the software and can clarify the intended meaning of a message. Various projects are lacking message documentation (language code "qqq"), e.g. SRF [3]. This is something where users who are familiar with the software could help by writing short documentations. This can be done directly on translatewiki.net, without any developer access to the code. If you would like to help out, please have a look at translatewiki.net. They have a lot of documentation on how everything works (it is usually quite easy). Part of the task is to chase the right people, so don't hesitate to email the developer if something is unclear. I am sure that some of you are already working with translatewiki anyway. Yet, the folks at translatewiki are often not sure whom to ask about certain issues -- if you think you could manage this a bit (i.e., become the main contact for translating S* extensions) then you are most welcome to let us know. Cheers, Markus [1] https://translatewiki.net/wiki/Support/Open_requests [2] <https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Semex-shortquery-hover-loading-failed/en> <https://translatewiki.net/wiki/Thread:Suppor/About_MediaWiki:Validator-listerrors-errors/en> <https://translatewiki.net/wiki/Thread:Suppor/About_MediaWiki:Validator-type-title/en> <https://translatewiki.net/wiki/Thread:Support/MediaWiki:Srf_paramdesc_views> <https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Smw-ask-otheroptions-info/en> [3] https://bugzilla.wikimedia.org/show_bug.cgi?id=36607 |
From: Markus K. <ma...@se...> - 2012-10-19 06:07:25
|
Hi Karsten, On 18/10/12 11:58, [[kgh]] wrote: > Heiya Markus, heiya to all of you, > > when it comes to missing message documentation (/qqq) I offer to be the person for first level support on > bugzilla as well as on tw.n. As a matter of fact I have helped in this context in the past already for SWM > [1]. Thus bugs concerning missing /qqq may be assingned to me directly. I just was not aware of this one > (36607) and partially fixed it without knowing about it. The same applies to tw.n support requests. You may > use me as the main support contact for semantic extensions there, too. Great, thanks a lot. I hope Nemo (Federico; CC) has seen this too. > > My recommendation to coders is to incluce message documentation right away. In fact this already done in the > meantime in most cases. Yes, this is also important for other developers who may need to decide if a message is appropriate for new code or not. Cheers, Markus > > Cheers Karsten > > PS @Markus Please forward this message to the dev-list. Thank you. The dev list was already in your CC, or do your messages get filtered? Anyway, this reply will reach both lists now. > > [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=36608 > > > Am 18.10.2012 10:06, schrieb Markus Krötzsch: >> Dear SMW users & developers, >> >> we enjoy an awesome internationalisation support from translatewiki.net, >> which ceaselessly translates MW extensions (and more) into a huge number >> of languages. >> >> To work smoothly, this also needs some help from the user/developer >> community, since translators are sometimes not sure about how a message >> is used (e.g. the word "view" could mean many things, and needs to be >> translated differently in each case). If there is a problem, "Open >> Requests" are created [1] (supported by SMW :-). Currently, there are 5 >> open requests related to SMW, Validator, SRF, and Semantic Expressivity >> [2] which could use some looking into. >> >> More generally, the translatewiki.net community could always use the >> help of users who are familiar with the software and can clarify the >> intended meaning of a message. Various projects are lacking message >> documentation (language code "qqq"), e.g. SRF [3]. This is something >> where users who are familiar with the software could help by writing >> short documentations. This can be done directly on translatewiki.net, >> without any developer access to the code. >> >> If you would like to help out, please have a look at translatewiki.net. >> They have a lot of documentation on how everything works (it is usually >> quite easy). Part of the task is to chase the right people, so don't >> hesitate to email the developer if something is unclear. I am sure that >> some of you are already working with translatewiki anyway. Yet, the >> folks at translatewiki are often not sure whom to ask about certain >> issues -- if you think you could manage this a bit (i.e., become the >> main contact for translating S* extensions) then you are most welcome to >> let us know. >> >> Cheers, >> >> Markus >> >> >> [1] https://translatewiki.net/wiki/Support/Open_requests >> [2] >> <https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Semex-shortquery-hover-loading-failed/en> >> <https://translatewiki.net/wiki/Thread:Suppor/About_MediaWiki:Validator-listerrors-errors/en> >> <https://translatewiki.net/wiki/Thread:Suppor/About_MediaWiki:Validator-type-title/en> >> <https://translatewiki.net/wiki/Thread:Support/MediaWiki:Srf_paramdesc_views> >> <https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Smw-ask-otheroptions-info/en> >> >> [3] https://bugzilla.wikimedia.org/show_bug.cgi?id=36607 >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Markus K. <ma...@se...> - 2012-10-22 09:03:24
|
On 21/10/12 11:13, Federico Leva wrote: > Hello, > > Markus Krötzsch, 19/10/2012 08:07: >> Great, thanks a lot. I hope Nemo (Federico; CC) has seen this too. > > Yes, I've seen it and I've just started assigning requests to Karsten. > Note, however, that in general they are not only about documentation, > and I don't know if Karsten is also willing to commit patches for > gender, grammar, plural support and so on when needed. Requests that need changes to the code should be submitted to bugzilla as usual. Anybody can take any bug from there and submit a patch (in the best case directly through gerrit). Translation-related bugs do not require a special handling here. In general, we can always use help in monitoring/processing input from bugzilla. This does not even require patches -- assessing, verifying, and classifying bugs would already help. Even filtering out the invalid/worksforme bugs would make a big contribution. But I18N requests are not special here. Markus >>> >>> My recommendation to coders is to incluce message documentation right >>> away. In fact this already done in the >>> meantime in most cases. >> >> Yes, this is also important for other developers who may need to decide >> if a message is appropriate for new code or not. > |