Hi All,
The grants team & I are trying to build workflow tools to make it easier for people to create grant and interact with it, endorsing it, joining it etc.
The first tool we are building is a popup where anyone can endorse a grant and add his/her comment in the popup.
Eg: https://meta.wikimedia.org/wiki/Grants:IEG/Heather%27s_test You'll need to add importScript('User:Jeph_paul/endorse.js'); to your common.js on meta.
We want users to be able to create grants in the own language too. We were assuming we could edit the translated pages using the API but that does not seem the case. It isn't possible to manually edit the translated page either. We are actually not looking for translation per se, we want users to be able to create pages in different languages in the Grants namespace.
Eg: The user should be able to create IEG'shttps://meta.wikimedia.org/wiki/Grants:IEGin his/her language. There will be a template which will need translations (The skeleton for a grant), but from then on we wont be needing the ability to translate. The user should be able to go ahead & add content in his language.
What would be the best way to achieve this in meta? Looking forward to your comments.
Thanks Jeph
Jeph Alapat, 03/05/2014 12:38:
What would be the best way to achieve this in meta? Looking forward to your comments.
It's a well known enhancement request that you can follow/vote on bugzilla: https://bugzilla.wikimedia.org/show_bug.cgi?id=35489 If you want it to be solved, you need to ask resources to be assigned (presumably in WMF Platform/Core team) to fixing the core bug https://bugzilla.wikimedia.org/show_bug.cgi?id=9360 .
Nemo
Hi,
03.05.2014 12:38:00 (CEST), Jeph Alapat kirjoitti:
We want users to be able to create grants in the own language too. We were assuming we could edit the translated pages using the API but that does not seem the case. It isn't possible to manually edit the translated page either.
No, the Translate extension is thought to keep alignment between languages, hence it is forbidden to change translated pages. Since your script cannot add endorsement on translated pages, I suggest adding the endorsements on a common page (e.g. "IEG name/Endorsements") and it will also avoid changing a translatable page (translation admins will not like continuously marking pages to be translated and I’m not sure it is needed to translate the endorsements). On a common page, perhaps the multilingual aspects can even be shown by adding endorsements: * {{#language:fr}}: {{lang|fr|Fantastique IEG !}} ~~~~
Note: for the page language, there is mw.config.get('wgPageContentLanguage')
We are actually not looking for translation per se, we want users to be able to create pages in different languages in the Grants namespace.
Eg: The user should be able to create IEG'shttps://meta.wikimedia.org/wiki/Grants:IEGin his/her language. There will be a template which will need translations (The skeleton for a grant), but from then on we wont be needing the ability to translate. The user should be able to go ahead & add content in his language.
What would be the best way to achieve this in meta? Looking forward to your comments.
Apart from the bug pointed by Nemo is quickly resolved (I have some doubts), perhaps you can add the new submissions on a temporary page (e.g. "IEG name/Original proposal") and ask translators to translate from language-to-English without the Translate extension.
If you don’t know the InputBox extension, you can be interested in it (or its functionalities), particularly the preload and editintro parameters if you want to preload a skeleton page to be filled, possibly even with templates and/or in a specific language.
~ Seb35
Hi
We've decided to keep it really simple. We'll pick the interface language from the user's language setting & disable the endorsements on translated pages. We are assuming the primary grant language as english, till such time that the mediawiki bug is fixed or we decide to tag the page with a language marker inside the wikitext ourselves (It'll be local to our gadget though).
Jeph
On Mon, May 5, 2014 at 2:15 PM, Seb35 seb35wikipedia@gmail.com wrote:
Hi,
03.05.2014 12:38:00 (CEST), Jeph Alapat kirjoitti:
We want users to be able to create grants in the own language too. We were
assuming we could edit the translated pages using the API but that does not seem the case. It isn't possible to manually edit the translated page either.
No, the Translate extension is thought to keep alignment between languages, hence it is forbidden to change translated pages. Since your script cannot add endorsement on translated pages, I suggest adding the endorsements on a common page (e.g. "IEG name/Endorsements") and it will also avoid changing a translatable page (translation admins will not like continuously marking pages to be translated and I’m not sure it is needed to translate the endorsements). On a common page, perhaps the multilingual aspects can even be shown by adding endorsements:
- {{#language:fr}}: {{lang|fr|Fantastique IEG !}} ~~~~
Note: for the page language, there is mw.config.get(' wgPageContentLanguage')
We are actually not looking for translation per se, we want users to be
able to create pages in different languages in the Grants namespace.
Eg: The user should be able to create IEG'shttps://meta.wikimedia.org/wiki/Grants:IEGin his/her language.
There will be a template which will need translations (The skeleton for a grant), but from then on we wont be needing the ability to translate. The user should be able to go ahead & add content in his language.
What would be the best way to achieve this in meta? Looking forward to your comments.
Apart from the bug pointed by Nemo is quickly resolved (I have some doubts), perhaps you can add the new submissions on a temporary page (e.g. "IEG name/Original proposal") and ask translators to translate from language-to-English without the Translate extension.
If you don’t know the InputBox extension, you can be interested in it (or its functionalities), particularly the preload and editintro parameters if you want to preload a skeleton page to be filled, possibly even with templates and/or in a specific language.
~ Seb35
10.05.2014 11:53:54 (CEST), Jeph Alapat kirjoitti:
We've decided to keep it really simple. We'll pick the interface language from the user's language setting & disable the endorsements on translated pages. We are assuming the primary grant language as english, till such time that the mediawiki bug is fixed or we decide to tag the page with a language marker inside the wikitext ourselves (It'll be local to our gadget though).
Ok, it’s easier for now. Anyway could you use a subpage "/Endorsements" to avoid changing the main page? Else there will be always a message on the top "mark this page for the translation" and the endorsements on the translated pages will hardly stay synchronised with the main page. Such a subpage can be transcluded on main page and translations with "{{:Grants:IEG/Heather's test/Endorsements}}".
~ Seb35
Jeph
On Mon, May 5, 2014 at 2:15 PM, Seb35 seb35wikipedia@gmail.com wrote:
Hi,
03.05.2014 12:38:00 (CEST), Jeph Alapat kirjoitti:
We want users to be able to create grants in the own language too. We were
assuming we could edit the translated pages using the API but that does not seem the case. It isn't possible to manually edit the translated page either.
No, the Translate extension is thought to keep alignment between languages, hence it is forbidden to change translated pages. Since your script cannot add endorsement on translated pages, I suggest adding the endorsements on a common page (e.g. "IEG name/Endorsements") and it will also avoid changing a translatable page (translation admins will not like continuously marking pages to be translated and I’m not sure it is needed to translate the endorsements). On a common page, perhaps the multilingual aspects can even be shown by adding endorsements:
- {{#language:fr}}: {{lang|fr|Fantastique IEG !}} ~~~~
Note: for the page language, there is mw.config.get(' wgPageContentLanguage')
We are actually not looking for translation per se, we want users to be
able to create pages in different languages in the Grants namespace.
Eg: The user should be able to create IEG'shttps://meta.wikimedia.org/wiki/Grants:IEGin his/her language.
There will be a template which will need translations (The skeleton for a grant), but from then on we wont be needing the ability to translate. The user should be able to go ahead & add content in his language.
What would be the best way to achieve this in meta? Looking forward to your comments.
Apart from the bug pointed by Nemo is quickly resolved (I have some doubts), perhaps you can add the new submissions on a temporary page (e.g. "IEG name/Original proposal") and ask translators to translate from language-to-English without the Translate extension.
If you don’t know the InputBox extension, you can be interested in it (or its functionalities), particularly the preload and editintro parameters if you want to preload a skeleton page to be filled, possibly even with templates and/or in a specific language.
~ Seb35
Seb35, 13/05/2014 17:18:
Ok, it’s easier for now. Anyway could you use a subpage "/Endorsements" to avoid changing the main page? Else there will be always a message on the top "mark this page for the translation" and the endorsements on the translated pages will hardly stay synchronised with the main page. Such a subpage can be transcluded on main page and translations with "{{:Grants:IEG/Heather's test/Endorsements}}".
+1.
Nemo
mediawiki-i18n@lists.wikimedia.org