Hi guys,
The Commons messages are now a big mess. Everything gets imported from other bots, duplication etc etc. I was thinking about just making a lib (commons_lib.py?) to store the messages and moving the translations to the i18n later on. Good plan? Or should it be in the family file?
Comments please :-)
Affected files: nowcommons.py imagecopy.py imagecopy_self.py imagetransfer.py tag_nowcommons.py (maybe more)
Maarten
On 06/07/11 21:20, Maarten Dammers wrote:
Hi guys,
The Commons messages are now a big mess. Everything gets imported from other bots, duplication etc etc. I was thinking about just making a lib (commons_lib.py?) to store the messages and moving the translations to the i18n later on. Good plan? Or should it be in the family file?
Comments please :-)
Affected files: nowcommons.py imagecopy.py imagecopy_self.py imagetransfer.py tag_nowcommons.py (maybe more)
Maarten
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
I'd go with the i18n route, because its used for a lot of scripts, and it would benefit...
Hi Maarten,
On 06/07/11 21:20, Maarten Dammers wrote:
other bots, duplication etc etc. I was thinking about just making a lib (commons_lib.py?) to store the messages and moving the translations to the i18n later on. Good plan? Or should it be in the family file?
I think it would be best just to use the i18n infrastructure - this essentially already is a library the way you suggest. Just name the messages commons-blah-die-blah, put then in i18n/commons.py and you've got the best of both worlds: central commons messages /and/ free translations.
Best, Merlijn
Hi Merlijn,
Op 9-7-2011 14:03, Merlijn van Deen schreef:
Hi Maarten,
On 06/07/11 21:20, Maarten Dammers wrote: > other bots, duplication etc etc. I was thinking about just making a lib > (commons_lib.py?) to store the messages and moving the translations to > the i18n later on. Good plan? Or should it be in the family file?I think it would be best just to use the i18n infrastructure - this essentially already is a library the way you suggest. Just name the messages commons-blah-die-blah, put then in i18n/commons.py and you've got the best of both worlds: central commons messages /and/ free translations.
I did this for some messages, so these can be translated at translatewiki. I'll probably move the more configuration like messages to a shared library.
Maarten
pywikipedia-l@lists.wikimedia.org