Hi folks,
please help me understand how to do this stuff.
First, I have to use the i18n.twtranslate() function. That's OK. Second: there must be a file in /i18n subdirectory with the same name that contains translations. As I see here: https://www.mediawiki.org/wiki/Special:Code/pywikipedia/9882Follow-up translations are directly written in this file and committed? But what is the role of translatewiki then? I miss a manual for that.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I had the same problem once... ;)
DON'T PANIC!
http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02255.html
and thus
http://lists.wikimedia.org/pipermail/pywikipedia-l/2011-January/006632.html
Hoping this helps... ;)
Greetings DrTrigon
On 11.02.2012 17:03, Bináris wrote:
Hi folks,
please help me understand how to do this stuff.
First, I have to use the i18n.twtranslate() function. That's OK. Second: there must be a file in /i18n subdirectory with the same name that contains translations. As I see here: https://www.mediawiki.org/wiki/Special:Code/pywikipedia/9882Follow-up
translations are directly written in this file and committed? But what
is the role of translatewiki then? I miss a manual for that.
-- Bináris
_______________________________________________ Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
2012/2/11 Dr. Trigon dr.trigon@surfeu.ch
http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02255.html
and thus
http://lists.wikimedia.org/pipermail/pywikipedia-l/2011-January/006632.html
Hoping this helps... ;)
Thank you, but I still don't really understand. This is about creating translations in rewrite/i18n. OK. How do they get to TW? How do they get back? This letter tells more about this: http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02269.htmlS... some manual work is done, but who does it, and what is the algorithm? Which is the main field of translating, those "shadow" scripts in /i18n subdirectory, or translatewiki? May translations be done in any of these? Or is the TW just for those who have no access to Pywiki SVN, and committers should translate in scripts?
One more: xqt says: "i18n dicts are placed in the rewrite branch. In trunk release i18n directory is defined as svn:external which copies its content from rewrite." What happens if I write a script to trunk that is still not implemented in rewrite? Should its "shadow" script also be placed in rewrite/i18n?
Thanks, Bináris
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As far as I remeber - basically - you write it into i18n directory and commit it to svn, then you have to notify someone (I think siebrand, but not sure...) to import those new ones to TW. Then later the entries at TW get frequently exported to svn again and you can enjoy them.
Greetings
On 11.02.2012 23:00, Bináris wrote:
2012/2/11 Dr. Trigon <dr.trigon@surfeu.ch mailto:dr.trigon@surfeu.ch>
http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02255.html
and thus
http://lists.wikimedia.org/pipermail/pywikipedia-l/2011-January/006632.html
Hoping this helps... ;)
Thank you, but I still don't really understand. This is about creating translations in rewrite/i18n. OK. How do they get to TW? How do they get back? This letter tells more about this: http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02269.html
So some manual work is done, but who does it, and what is the algorithm?
Which is the main field of translating, those "shadow" scripts in /i18n subdirectory, or translatewiki? May translations be done in any of these? Or is the TW just for those who have no access to Pywiki SVN, and committers should translate in scripts?
One more: xqt says: "i18n dicts are placed in the rewrite branch. In trunk release i18n directory is defined as svn:external which copies its content from rewrite." What happens if I write a script to trunk that is still not implemented in rewrite? Should its "shadow" script also be placed in rewrite/i18n?
Thanks, Bináris
_______________________________________________ Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
On 11/02/2012 22:43, Dr. Trigon wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As far as I remeber - basically - you write it into i18n directory and commit it to svn, then you have to notify someone (I think siebrand, but not sure...) to import those new ones to TW. Then later the entries at TW get frequently exported to svn again and you can enjoy them.
Greetings
Thats basicly it, yes... and Siebrand seems to be the person in charge of pywikipedia translations at twn, (I really should know who is, considering I'm twn staff as well...)
-- Lewis Cawte
On 11.02.2012 23:00, Bináris wrote:
2012/2/11 Dr. Trigon<dr.trigon@surfeu.ch mailto:dr.trigon@surfeu.ch>
http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02255.html
and thus
http://lists.wikimedia.org/pipermail/pywikipedia-l/2011-January/006632.html
Hoping this helps... ;)
Thank you, but I still don't really understand. This is about creating translations in rewrite/i18n. OK. How do they get to TW? How do they get back? This letter tells more about this: http://www.mail-archive.com/pywikipedia-l@lists.wikimedia.org/msg02269.html
So some manual work is done, but who does it, and what is the algorithm?
Which is the main field of translating, those "shadow" scripts in /i18n subdirectory, or translatewiki? May translations be done in any of these? Or is the TW just for those who have no access to Pywiki SVN, and committers should translate in scripts?
One more: xqt says: "i18n dicts are placed in the rewrite branch. In trunk release i18n directory is defined as svn:external which copies its content from rewrite." What happens if I write a script to trunk that is still not implemented in rewrite? Should its "shadow" script also be placed in rewrite/i18n?
Thanks, Bináris
_______________________________________________ Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk827x8ACgkQAXWvBxzBrDCmMwCggv8qVc3F0SMSynoSgjDDKTmh MLkAoMctvMu7egi0EE8ViCGjO3yDUC0R =Eskk -----END PGP SIGNATURE-----
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l