The Slovak translation should be in an importable state now. I have been testing it successfully on my system for several weeks. Some statistics: Character set: UTF-8 Translated messages: 1248 Untranslated messages: 125 Link: http://www.matuska.org/martin/mailman/ Patch for Mailman ver 2.1.9, including updated German and Czech translations for the word "Slovak": http://www.matuska.org/martin/mailman/sk-2.1.9-0.1.patch.gz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 27, 2007, at 9:06 AM, Martin Matuska wrote:
The Slovak translation should be in an importable state now. I have been testing it successfully on my system for several weeks.
Some statistics: Character set: UTF-8 Translated messages: 1248 Untranslated messages: 125
Link: http://www.matuska.org/martin/mailman/
Patch for Mailman ver 2.1.9, including updated German and Czech translations for the word "Slovak": http://www.matuska.org/martin/mailman/sk-2.1.9-0.1.patch.gz
Martin, thanks for your contribution. I'm hoping Mark can import your language for 2.1.10. I'm also wondering whether we can get the Hebrew translation into 2.1.10. Here's something I've been thinking about, and I'd like to know what you folks think about this. Short of using a translation service such as Rosetta or Pootle, how can we make translations easier to add and update? What if all translators were to use Bazaar branches of the 2.1 tree to update and add new translations to? Then all we (i.e. core developers) would need to do would be to merge your branch to test the changes. It would make it easier for you because your translation branch could be easily kept up-to-date with the official 2.1 branch, and it would be easier for us to merge in your changes. Is this a crazy idea or a good one? It should be fairly easy to implement both for you all and for us. If anybody has any questions about Bazaar, of course, we're here to help. If you like this idea, I'd be happy to create a Launchpad team that you could join and publish branches to, although it would /not/ be required to use this. In other words, you could use any Bazaar branch hosting service to publish your i18n branches, even one you hosted yourself. The only thing I'd request is that we update the wiki page http://wiki.list.org/display/DEV/Languages to include the location of the branch. The really cool thing is that we could write a script to automatically scrape that page and pull your updates whenever we're about to cut a new release. Martin, how would you like to be the test subject on this one? :) Thoughts? - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRqqNuXEjvBPtnXfVAQLA9AP+OMtU1t1pZ+6hpYzLqLqhW7pFrdiBvbzD GUKx6UV8Y0k2zhibelmlUgqFIjYKDhGTjH4WUjjxjpDupCyhWI/o8EonHIWSZYXq e8ajsTJEM3aHcj4Aq5LHQxmGa87Vp8IBwCwEirv6zSavEW3rPVk24txXFy8iE/+i gqiSmlc3/O4= =t9oS -----END PGP SIGNATURE-----
On 28/07/2007, at 9:58 AM, Barry Warsaw wrote:
Here's something I've been thinking about, and I'd like to know what you folks think about this.
Short of using a translation service such as Rosetta or Pootle,
Pootle would definitely make things easier, and gain you more translator participation.
how can we make translations easier to add and update? What if all translators were to use Bazaar branches of the 2.1 tree to update and add new translations to? Then all we (i.e. core developers) would need to do would be to merge your branch to test the changes. It would make it easier for you because your translation branch could be easily kept up-to-date with the official 2.1 branch, and it would be easier for us to merge in your changes.
Is this a crazy idea or a good one? It should be fairly easy to implement both for you all and for us. If anybody has any questions about Bazaar, of course, we're here to help.
If you like this idea, I'd be happy to create a Launchpad team that you could join and publish branches to, although it would /not/ be required to use this. In other words, you could use any Bazaar branch hosting service to publish your i18n branches, even one you hosted yourself. The only thing I'd request is that we update the wiki page
http://wiki.list.org/display/DEV/Languages
to include the location of the branch. The really cool thing is that we could write a script to automatically scrape that page and pull your updates whenever we're about to cut a new release.
Martin, how would you like to be the test subject on this one? :)
Thoughts?
This is my first encounter with bzr. I installed it last night (via MacPorts), and according to the wiki page for bzr, it seems similar enough to svn from the user POV. As long as committing a translation via bzr is as straightforward as committing via svn, it shouldn't be a problem for people accustomed to using source control. (We're still losing the vast majority of linguists, who are not technically minded, so Pootle is still my recommendation.) For source control, I still prefer svn. ;) For one thing, it's embedded into my favourite tools: my translation editor, my text editor and my file manager — bzr is not. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 28, 2007, at 1:51 AM, Clytie Siddall wrote:
On 28/07/2007, at 9:58 AM, Barry Warsaw wrote:
Here's something I've been thinking about, and I'd like to know what you folks think about this.
Short of using a translation service such as Rosetta or Pootle,
Pootle would definitely make things easier, and gain you more translator participation.
I think Rosetta probably would too, although I don't have a good sense of which community is more robust, where mind-share is heading, or what the major advantages and disadvantages of both systems are. That's a good part of the reason why I don't want to think about switching to either yet, although we should start another thread at some point to talk about it. The right time for that is probably when we want to get 2.2 and/or 3.0 translated.
This is my first encounter with bzr. I installed it last night (via MacPorts), and according to the wiki page for bzr, it seems similar enough to svn from the user POV. As long as committing a translation via bzr is as straightforward as committing via svn, it shouldn't be a problem for people accustomed to using source control. (We're still losing the vast majority of linguists, who are not technically minded, so Pootle is still my recommendation.)
bzr should feel pretty natural for svn users, but please let me know if anybody hits roadblocks!
For source control, I still prefer svn. ;) For one thing, it's embedded into my favourite tools: my translation editor, my text editor and my file manager ― bzr is not.
I know! Hopefully over time, that stuff will come. (I recently scratched my own itch in writing a bzr plugin for setuptools ;). - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq5+1HEjvBPtnXfVAQJgtQQAmWW0XJ7opa2OrQJZ6yXK3FFP5ZQ56Kaj 3Q8C+38v4ESGJVK0OPN3agDeT5HYQdkw+KultND3ZnBhskSP8THG/ls/VEDYwkPE MPpYfswG56O/xrwJCHShVqxkl4sKuAgBDhVzcNpFGXHudlwMl8IYwXTGO3+qynNI kX9TLUuslW0= =LI9o -----END PGP SIGNATURE-----
Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 27, 2007, at 9:06 AM, Martin Matuska wrote:
The Slovak translation should be in an importable state now. I have been testing it successfully on my system for several weeks.
Some statistics: Character set: UTF-8 Translated messages: 1248 Untranslated messages: 125
Link: http://www.matuska.org/martin/mailman/
Patch for Mailman ver 2.1.9, including updated German and Czech translations for the word "Slovak": http://www.matuska.org/martin/mailman/sk-2.1.9-0.1.patch.gz
Martin, thanks for your contribution. I'm hoping Mark can import your language for 2.1.10. I'm also wondering whether we can get the Hebrew translation into 2.1.10.
Anything I can do to help...
Here's something I've been thinking about, and I'd like to know what you folks think about this.
Short of using a translation service such as Rosetta or Pootle, how can we make translations easier to add and update? What if all translators were to use Bazaar branches of the 2.1 tree to update and add new translations to? Then all we (i.e. core developers) would need to do would be to merge your branch to test the changes. It would make it easier for you because your translation branch could be easily kept up-to-date with the official 2.1 branch, and it would be easier for us to merge in your changes.
Is this a crazy idea or a good one? It should be fairly easy to implement both for you all and for us. If anybody has any questions about Bazaar, of course, we're here to help.
It sounds good to me. It seems to me that this would simplify keeping the translation up-to-date, and still not jepordize the main branch. It will also give me a good place and method to store the translation. This is a definite improvement over the present situation!
If you like this idea, I'd be happy to create a Launchpad team that you could join and publish branches to, although it would /not/ be required to use this. In other words, you could use any Bazaar
I'd be happy to join a launchpad team.
branch hosting service to publish your i18n branches, even one you hosted yourself. The only thing I'd request is that we update the wiki page
http://wiki.list.org/display/DEV/Languages
to include the location of the branch. The really cool thing is that we could write a script to automatically scrape that page and pull your updates whenever we're about to cut a new release.
Martin, how would you like to be the test subject on this one? :)
Again, if you would like more than 1 test subject...
Thoughts? - -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRqqNuXEjvBPtnXfVAQLA9AP+OMtU1t1pZ+6hpYzLqLqhW7pFrdiBvbzD GUKx6UV8Y0k2zhibelmlUgqFIjYKDhGTjH4WUjjxjpDupCyhWI/o8EonHIWSZYXq e8ajsTJEM3aHcj4Aq5LHQxmGa87Vp8IBwCwEirv6zSavEW3rPVk24txXFy8iE/+i gqiSmlc3/O4= =t9oS -----END PGP SIGNATURE----- _______________________________________________ Mailman-i18n mailing list Posts: Mailman-i18n@python.org Unsubscribe: http://mail.python.org/mailman/options/mailman-i18n/linux%40zamirfamily.com _________________________________________________________________________ This message has been scanned by Kibbutz Beit Kama's Anti Virus software, and is believed to be clean of any viruses. _________________________________________________________________________
!DSPAM:506,46aa8ecb62391804284693!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 28, 2007, at 3:52 AM, Dov Zamir wrote:
Here's something I've been thinking about, and I'd like to know what you folks think about this. Short of using a translation service such as Rosetta or Pootle, how can we make translations easier to add and update? What if all translators were to use Bazaar branches of the 2.1 tree to update and add new translations to? Then all we (i.e. core developers) would need to do would be to merge your branch to test the changes. It would make it easier for you because your translation branch could be easily kept up-to- date with the official 2.1 branch, and it would be easier for us to merge in your changes. Is this a crazy idea or a good one? It should be fairly easy to implement both for you all and for us. If anybody has any questions about Bazaar, of course, we're here to help.
It sounds good to me. It seems to me that this would simplify keeping the translation up-to-date, and still not jepordize the main branch. It will also give me a good place and method to store the translation. This is a definite improvement over the present situation!
If you like this idea, I'd be happy to create a Launchpad team that you could join and publish branches to, although it would / not/ be required to use this. In other words, you could use any Bazaar
I'd be happy to join a launchpad team.
branch hosting service to publish your i18n branches, even one you hosted yourself. The only thing I'd request is that we update the wiki page http://wiki.list.org/display/DEV/Languages to include the location of the branch. The really cool thing is that we could write a script to automatically scrape that page and pull your updates whenever we're about to cut a new release. Martin, how would you like to be the test subject on this one? :)
Again, if you would like more than 1 test subject...
Hi Dov, If you have the time, let's see how far we can get with this idea, and see if it'll work in the short term for us (until we have a fuller discussion of moving to a better system). My recommendation would be this: * sign up for a Launchpad account * create your own bzr branch of the 2.1 official branch * integrate the Hebrew translation into your branch and test it * push your branch to your Launchpad user account * let us know what the URL is We can then try to merge your branch into the official 2.1 branch if it all looks good, we can commit the changes. You can keep your branch up to date with the official one by doing 'bzr pull' or 'bzr merge' when you see changes on the mailman-checkins list. Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq6AgXEjvBPtnXfVAQJfTQP+P3iNO2+NVWlVbjX2Ea+N53qMFUMMo317 b1VADj11s14S2aV1UnVYLF5IUfI/fTYc1L8U5nRuUx+OIHYyG2s3I/CC9G4s/g7v 4XBjhQ9X6F8+MlThGn8GxTqb4MWz0sbXUQ+sJEtTvVf0nW8Cuvr22K1C3dS1FZ2R yqX3F4uSykU= =py4+ -----END PGP SIGNATURE-----
participants (4)
-
Barry Warsaw -
Clytie Siddall -
Dov Zamir -
Martin Matuska