From paul.kholer at gmail.com Tue Jul 3 21:50:14 2007 From: paul.kholer at gmail.com (paul.kholer paul.kholer) Date: Tue, 3 Jul 2007 22:50:14 +0300 Subject: [Mailman-i18n] Sierra Club-NYC Report Calls for New York City Energy Shortage Contingency Plan - Energy Automation Systems Message-ID: <19de303e0707031250u2da5cd27nb498208b3d894802@mail.gmail.com> Energy Automation Systems Sierra Club NYC Group releases a report detailing why and how the City needs to prevent rapid price spikes by planning and acting today. The group says Mayor Bloomberg's PlaNYC 2030 moves the City in the right direction in planning for long term sustainability, but encourages City leaders to include rapid energy conservation plans to respond to potential energy price shocks. Its report, "Moving NYC Toward Sustainable Energy Independence," authored by Dan Miner, the Group's energy committee chair, requests Council to reconsider Intro. 374, previously submitted in 2004. Both San Francisco and Portland, Oregon have passed similar bills. Short and long-term recommendations on transportation, buildings, electric generation and renewable power, addressing both global warming and energy security are offered in the report. Some recommendations were included in PlaNYC and in Governor Spitzer's plan to reduce state electricity use 15% by 2015, others will enhance these proposals, while stepping up the City's climate change response. Organizations that have signed on to the report so far include: American Littoral Society NE Chapter, Asthma Free School Zone, Carbon Tax Center, Galapagos Art Center, Hudson River Sloop Clearwater, Energy & Environment Program at Interfaith Center on Corporate Responsibility, New York Public Interest Research Group, Nos Quedamos, NY Divinity School, the Pace Energy Project, Sane Aviation for Everyone, Solar One, Sustainable South Bronx, The Cathedral Church of St. John the Divine, and The Gaia Institute. New York City Must Prepare Now for Energy Security Dan Miner, Sierra Club NYC Group energy committee chair Many of us are worried about the long-term consequences of climate change, and there's growing support for the warnings of climate scientists that we need to cut carbon emissions by 80% by 2050 to avoid climate catastrophe. On the other hand, most Americans are not cutting their energy use significantly. Defenders of business as usual claim that energy frugality will harm our economy, while failing to consider that inaction now guarantees wrecking the economy later with heat waves and flooding. Part of the problem is the perception that the climate impacts of our oil addiction lie far in the future, preventing a public consensus of urgency. Without that, the bold political action we need today is impossible. Our dependence on imported fossil fuels poses serious short-term risks as well. Conservative pundits and military analysts tell us that even slight disruptions to our oil imports will cause prices to spike to $100 a barrel or more. The economic consequences will impact most Americans personally and directly. Unlike climate change impacts, we could be faced with the national security threat of price shocks at any time. For example, an attack on Iran is likely to result in a blockade of the Straits of Hormuz, through which over a third of the world's oil is shipped. Hopefully that won't happen, but we're still at risk from disruptions caused by Gulf Coast hurricanes or terrorist attacks on oil shipping and refining infrastructure. Even without a crisis, a recent GAO report documents that depleting world oil supplies, when combined with rising demand, will make energy markets increasingly volatile - and supply disruptions inevitable. Rising awareness of climate change is accelerating the transition away from fossil fuels, and we need to step it up further. Short-term municipal plans to conserve energy quickly during fuel price shocks are a critical starting point. Putting them into place will make cities more resilient, and public education about them will motivate rapid implementation of efficiency, conservation and renewable energy projects. Both the Administration and the Council have been doing a fine job on environmental issues, and with PlaNYC 2030, New York City is on the path toward long-term sustainability. However, our vulnerability to energy shocks requires attention now. How would $100 a barrel oil affect trucks bringing groceries to supermarkets, winter heating bills, commuters, and the restaurants and theaters dependent on tourists? These are prudent questions to consider well before problems arise. The newly released Sierra Club report, "Moving New York City toward Sustainable Energy Independence" asks the PlaNYC initiative to address this issue, and urges the City Council to resurrect the bill, drafted in 2004 by its own Environmental Committee, which would create a City energy shortage contingency plan. San Francisco and Portland, Oregon have already passed similar bills, and are already developing their plans. The report recommends creating such a plan in the short term, and over the long term, rapid deployment of decentralized, renewable power, and other measures that will enhance PlaNYC 2030 implementation. By cutting energy costs, creating jobs, and slowing global warming while buffering the impact of energy shocks, the approach is a win-win solution. New York's example could lead the U.S. toward energy independence. We don't have to wait for future disasters, let's start moving beyond oil today. http://www.energyautomation.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070703/ddf404cc/attachment.htm From paul.kholer at gmail.com Tue Jul 3 19:24:33 2007 From: paul.kholer at gmail.com (paul.kholer paul.kholer) Date: Tue, 3 Jul 2007 20:24:33 +0300 Subject: [Mailman-i18n] Energy Sports Drink To Warm Up Your Body - Joe Merlo Message-ID: <19de303e0707031024v7860efadt3c51d15b6d2f5935@mail.gmail.com> Joe Merlo An energy sports drink can be very helpful especially for the athletes and enthusiasts who want to try out sports. Most athletes have relied upon energy sports drink to give them extra stamina so that they can practice all day. People who treat sports as their profession surely force themselves to take energy sports drink so that they can increase their performance and work. Some of these sports player are basketball players who are exposed to lots of warm ups and trainings. They even spend a whole day and continued practice just to put their body in good condition and master their shooting skills. The runners are also some of the athletes who take energy sports drink. They need speed and endurance and they should not tire off easily because they will lose it. Running is not a joke because you give off all your strength and rest for a little while and hit the tracks again. However helpful, it has been said that energy sports drink do not give a good effect to the human body. Some people know it but they know that they don?t have a choice but to drink it to give them the power and strength they need. If you are quite concerned enough, you can try to look at the ingredients and contents of the energy drink. If you are still young, you should not drink energy sports drink because it might not bring a good effect to your body and to your health as well. Most of these athletes can also experience side effects in their body. Some may not feel it at once but as time goes on and with continued use, probably they will feel it when they grow older. It may even shorten a person?s life or cause sudden death if taken more than the usual. But that is only a probability because there are no proofs that it had brought dangers to a person. If you are into sports, it is true that you need the energy sports drink. But as long as you can handle the pressure, you can try to bring out the very best in you. If not, choose an energy sports drink which has low caffeine because it is known to men that said ingredient may bring side effects to your body. Also, as much as possible, do not drink it excessively. Drink it only when you need it to save your body from too much caffeine contamination. If you drink energy sports drink at the desired dosage, it may be helpful to a person?s build up. The only hazard is when a person drinks too much. Energy sports drink have been known and proven to increase activity of the body, brain activity, performance and endurance. This will make a person finish a long day?s activity without wearing easily. If you have kids, make sure that they don?t drink energy sports drink like you do because it will damage their health the most. These drinks will surely increase your energy but make sure that you know how to handle your body properly to keep you healthy and in shape. Want to start the day and end the day right? Get an energy sports drink and warm your body up. http://www.energyautomation.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070703/fc07d31c/attachment.html From paul.kholer at gmail.com Wed Jul 4 22:40:06 2007 From: paul.kholer at gmail.com (paul.kholer paul.kholer) Date: Wed, 4 Jul 2007 23:40:06 +0300 Subject: [Mailman-i18n] Tackling Key Home Improvement Projects - Direct Buy Message-ID: <19de303e0707041340x5ed2c19ex83863678a168c989@mail.gmail.com> Direct Buy Summer time means barbeques, baseball, camping, and yes, Home Improvement Projects! As the weather gets nice and the days get longer so do lists of home improvement projects. Here are a few projects which are best done in the summer maximizing the long days and the good weather! *Gardening/Landscaping:* Depending on which part of the country you live in it may be too late to plant a garden from seed, but you most likely still have time to get your garden going using starters. Plant now, be sure to properly weed and water and you will enjoy your vegetables all fall. Many landscaping projects can be done throughout the year but it can be easier and more enjoyable during the summer. Build a rockwall, plant some perennials, or put down a fresh layer of mulch. Working in the summer ensures the soil will be easy to work with and completing these projects now allows you to enjoy them for the remainder of the summer and fall. *Exterior Painting:* In many parts of the country 80% of exterior painting gets done between the end of June and middle of September. The reason is the weather is more predictable and warmer; you don't have to worry as much about getting rained on in the middle of applying the second coat of paint. The summer months are also a popular time for staining decks. Not only do most people spend a lot of time on their decks during the summer and thus want them to look nice, but the long days are ideal for completing a re-staining job in a weekend. *Roof replacement:* Summer is the perfect time to replace your roof because there is no chance of getting snow and the weather is more predictable so you can plan the best time to tear the roof off. There is nothing worse than tearing off your roof right before a large rain fall! Also, in the summer you don't have to worry about losing the heat from your home as you would during the cold winter months. *Screening in your Porch:* To fully enjoy the outside without the bugs, screening in your porch is the only way to go. This project can actually be competed almost anytime during the year but will be enjoyed during the summer. *Get Air Conditioning unit tuned up:* If you haven't already done so you should get your AC tuned up. Many units use close to 50% more energy when they are not running properly. With the rising cost of energy you can't afford to keep your Air Conditioner running below its peak. The preceding is a list of projects which are best completed during the summer months. There are many other projects that are also completed during the summer but the ones above should be moved to the top of your list to maximize the weather during the summer. Good luck and don't forget to make time to go swimming too! http://www.directbuy.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070704/63b9aeb0/attachment.htm From paul.kholer at gmail.com Thu Jul 5 11:31:55 2007 From: paul.kholer at gmail.com (paul.kholer paul.kholer) Date: Thu, 5 Jul 2007 12:31:55 +0300 Subject: [Mailman-i18n] Reverse Modeling Becomes Exclusive Reseller of 3D3 Solutions' Flagship Product FlexScan3D - Harman Agency Message-ID: <19de303e0707050231p2dde945cqeea194c4bc11acbc@mail.gmail.com> Harman Agency Reverse Modeling, a premier 3D scanning solutions and service provider, has signed an agreement with 3D3 Solutions, developer of FlexScan3D, to resell their innovative reverse modeling solution to designers, artists, manufacturers and engineering professionals. Under the agreement, Reverse Modeling will offer the FlexScan3D software package nationwide. FlexScan3D Scanner is a software-based 3D scanner that lets users plug in virtually any digital SLR camera and off-the-shelf projector to create a 3D representation of an object for use in downstream applications or rapid prototyping. Offered at a fraction of the cost of most commercially available scanner solutions, FlexScan3D represents a shift in the 3D scanning market toward a more mainstream use of 3d scanners. The ability to plug in a variety of SLR cameras and projectors means that users have control over the quality and accuracy of the data, and can have multi-camera configurations at a much lower cost. "What makes FlexScan3D unique", says customer, John Thompson, "is that its flexible and affordable enough that the average modeler or designer can now capture 3D content without having to invest a lot of money on expensive or bulky hardware. I plug in my existing SLR and projector and I can capture everything I need, fast. I'm getting quality data that's better than more expensive systems." The addition of the FlexScan3D software gives Reverse Modeling clients a powerful and cost effective solution for reverse engineering and visualizing physical objects in 3D space. http://www.theharmanagency.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070705/a50b5f6f/attachment.htm From darush256 at gmail.com Sat Jul 21 13:55:30 2007 From: darush256 at gmail.com (darush aghababayeedehkordi) Date: Sat, 21 Jul 2007 04:55:30 -0700 Subject: [Mailman-i18n] my new work is balanced presentation groups Message-ID: <43a1a8cf0707210455k708b6719pc9df8da894d209e7@mail.gmail.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070721/3b642940/attachment.htm From martin at matuska.org Fri Jul 27 15:06:38 2007 From: martin at matuska.org (Martin Matuska) Date: Fri, 27 Jul 2007 15:06:38 +0200 Subject: [Mailman-i18n] Slovak translation of GNU Mailman Message-ID: <46A9EDDE.9060405@matuska.org> 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 From barry at python.org Sat Jul 28 02:28:40 2007 From: barry at python.org (Barry Warsaw) Date: Fri, 27 Jul 2007 20:28:40 -0400 Subject: [Mailman-i18n] Slovak translation of GNU Mailman In-Reply-To: <46A9EDDE.9060405@matuska.org> References: <46A9EDDE.9060405@matuska.org> Message-ID: <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> -----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----- From clytie at riverland.net.au Sat Jul 28 07:51:32 2007 From: clytie at riverland.net.au (Clytie Siddall) Date: Sat, 28 Jul 2007 15:21:32 +0930 Subject: [Mailman-i18n] Using bzr for translation commits (was: Re: Slovak translation of GNU Mailman In-Reply-To: <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> References: <46A9EDDE.9060405@matuska.org> <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> Message-ID: <76C75396-777B-480D-BC57-462DE6CFBAD4@riverland.net.au> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-i18n/attachments/20070728/5ff16529/attachment.pgp From clytie at riverland.net.au Sat Jul 28 08:49:30 2007 From: clytie at riverland.net.au (Clytie Siddall) Date: Sat, 28 Jul 2007 16:19:30 +0930 Subject: [Mailman-i18n] Updating translations Message-ID: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> HI everyone :) I'm trying to catch up with my translations (after not being able to contribute for some months), but I can't seem to find any translations needing updating in Mailman. Even the POT file in the Mailman 3.0 branch has a last-modified date of 2006-04-28. The vi.po files in each branch are complete, and haven't been changed since I last submitted them. Surely there are new strings or changed strings needing updating. But how do I find them? Thankyou for any help you can offer with this. :) 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-i18n/attachments/20070728/af6946b6/attachment.pgp From linux at zamirfamily.com Sat Jul 28 09:52:15 2007 From: linux at zamirfamily.com (Dov Zamir) Date: Sat, 28 Jul 2007 10:52:15 +0300 Subject: [Mailman-i18n] Slovak translation of GNU Mailman In-Reply-To: <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> References: <46A9EDDE.9060405@matuska.org> <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> Message-ID: <46AAF5AF.80203@zamirfamily.com> 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 at 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! > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20070728/dea0dbfa/attachment.html From msapiro at value.net Sun Jul 29 07:15:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 28 Jul 2007 22:15:39 -0700 Subject: [Mailman-i18n] Updating translations In-Reply-To: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> Message-ID: <46AC227B.5040502@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clytie Siddall wrote: > > Surely there are new strings or changed strings needing updating. But > how do I find them? After running configure, cd to the messages directory and run make potclean make potfile This will remove the existing marked.files, docstring.files and mailman.pot files and rebuild them. Note that this is done in the distribution/configure/make directory, not in the install directory. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGrCJ7VVuXXpU7hpMRAj11AKCAsBdGWQXE48hf657o90tGpdZetACgj7Qz hhKwXl88zJ/jKm+1h95Vrlw= =0r65 -----END PGP SIGNATURE----- From lists at suares.an Sun Jul 29 17:35:35 2007 From: lists at suares.an (Ace Suares) Date: Sun, 29 Jul 2007 11:35:35 -0400 Subject: [Mailman-i18n] Translating via launchpad Message-ID: <200707291135.35774.lists@suares.an> Hi, Now mailman is in bzr, and it's alos on launchpad, can translations be made against the launchpad interface ? For instance, in the mailman that is shipped with feisty, I see 228 untranslated strings... I am not sure if that aligns with the versions that we translated. Anyone can shed some light on this !? ace https://translations.launchpad.net/ubuntu/feisty/+source/mailman/+pots/mailman/nl/+translate?batch=10&show=untranslated From clytie at riverland.net.au Mon Jul 30 11:41:18 2007 From: clytie at riverland.net.au (Clytie Siddall) Date: Mon, 30 Jul 2007 19:11:18 +0930 Subject: [Mailman-i18n] Updating translations In-Reply-To: <46AC227B.5040502@value.net> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> <46AC227B.5040502@value.net> Message-ID: On 29/07/2007, at 2:45 PM, Mark Sapiro wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Clytie Siddall wrote: >> >> Surely there are new strings or changed strings needing updating. But >> how do I find them? > > > After running configure, cd to the messages directory and run > > make potclean > make potfile > > This will remove the existing marked.files, docstring.files and > mailman.pot files and rebuild them. > > Note that this is done in the distribution/configure/make > directory, not > in the install directory. > Mark, I didn't mean in my personal copy of Mailman. I mean in the repo. Shouldn't at least the POT file be automatically updated in each branch? mailman.pot in the /messages dir of the Mailman 3.0 branch shows a latest revision number of 6349 and a last-changed date of 2006-04-28. It has no new or changed strings compared with my Trunk translation of last year. I can't believe there have been no changes since then. :o 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-i18n/attachments/20070730/5401e12a/attachment.pgp From msapiro at value.net Mon Jul 30 18:06:56 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 30 Jul 2007 09:06:56 -0700 Subject: [Mailman-i18n] Updating translations In-Reply-To: References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> <46AC227B.5040502@value.net> Message-ID: <46AE0CA0.5000001@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clytie Siddall wrote: > > Mark, I didn't mean in my personal copy of Mailman. I mean in the repo. > Shouldn't at least the POT file be automatically updated in each branch? This has to be some kind of compromise. Considering the 3.0 branch (formerly the trunk), there have certainly been changes and there will be more, some of which will remove prior additions. This also happens to a lesser extent on the more stable branches. We don't want to keep making a moving target for translators, so in the past, we have set a point around a first beta release where i18n strings should be frozen for that release, and that's when we update the POT file and announce that the release is ready for translation. I am a little unclear myself on exactly how and when this is done as I have never done it although I have observed the results. Certainly we can discuss doing this more frequently. In the recent past, I have avoided making changes to the i18n strings in the 2.1 branch, because I thought the trunk would form the basis of a 2.2 release in the near future. Now that 2.2 has branched from 2.1 and not the trunk (3.0), and it looks like the near term release will be 2.1.10, I will be backporting some of my trunk changes to 2.2 and some even to 2.1. In any case, my opinion is that updating the POT any time i18n strings are added or changed is too frequent, but perhaps the current schedule (whatever it is) is not frequent enough. Of course, you can always update the POT in your working copy (or local branch in bzr) any time you want to work on changes. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGrgygVVuXXpU7hpMRAj3NAKDdCEmHXbqQM8mNUiQyj3M+g4p/YACg6AgK HV1byZoAgsc47K12j/Wf21Q= =9anj -----END PGP SIGNATURE----- From barry at python.org Mon Jul 30 19:18:08 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 30 Jul 2007 13:18:08 -0400 Subject: [Mailman-i18n] Updating translations In-Reply-To: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> Message-ID: <48582D54-ED1E-4E93-B996-E75FC92BEF00@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 28, 2007, at 2:49 AM, Clytie Siddall wrote: > Even the POT file in the Mailman 3.0 branch has a last-modified > date of 2006-04-28. The vi.po files in each branch are complete, > and haven't been changed since I last submitted them. Hi Clytie, At this point, no one should waste time trying to translate the 3.0 branch. A lot has changed and a lot /will/ change yet. For example, I'm currently working on changing the entire address registration and confirmation stuff. Strings and templates that used to talk about confirming a list subscription now talk about confirming an email address registration. The 2.1 pot file should definitely be up-to-date. If not, we need to regenerate it. The 2.2 pot file should be pretty much up-to-date, although it may change as we start to see the fruits of the new web u/ i. I still think it's a little early to start translating 2.2, but we should make sure the 2.1 branch has updated pot files, and we should concentrate on getting the translations up-to-date for 2.1.10. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq4dUXEjvBPtnXfVAQJvtwP8DxfTCZN0bCpBKGV7yJLsL1Poa9Vk99f9 MsFq7pYsJtgxFRwmkwJG0aeHLNoCddD2dmwwJcC9+AHeQzd8pWh+p/g/+tCzqYy6 KNqF5s6I5bTCDJuuuOzaLLYwGkonMauGy4bfcNT3P02ciSLzb6rYRpQ3pkkUB0sl n0mzYokq7CA= =4LW2 -----END PGP SIGNATURE----- From barry at python.org Mon Jul 30 19:22:02 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 30 Jul 2007 13:22:02 -0400 Subject: [Mailman-i18n] Updating translations In-Reply-To: <46AE0CA0.5000001@value.net> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> <46AC227B.5040502@value.net> <46AE0CA0.5000001@value.net> Message-ID: <7A94A89B-6B06-4375-B0B8-BE95F521E3FE@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 30, 2007, at 12:06 PM, Mark Sapiro wrote: > We don't want to keep making a moving target for translators, so in > the > past, we have set a point around a first beta release where i18n > strings > should be frozen for that release, and that's when we update the POT > file and announce that the release is ready for translation. > > I am a little unclear myself on exactly how and when this is done as I > have never done it although I have observed the results. Certainly we > can discuss doing this more frequently. One idea is to try to switched to timed updates for the translations. For example, we could say that on the 1st of every month (i.e. Mailman Day ), we'll update the pot files and push the changes to the official branches. Then translators will have what they need to update their translations. We can then say that on something like the 21st of each month, translators should send us their updates, or make sure their branches are updated for us to merge. > In the recent past, I have avoided making changes to the i18n > strings in > the 2.1 branch, because I thought the trunk would form the basis of a > 2.2 release in the near future. Now that 2.2 has branched from 2.1 and > not the trunk (3.0), and it looks like the near term release will be > 2.1.10, I will be backporting some of my trunk changes to 2.2 and some > even to 2.1. Excellent Mark, thanks. > In any case, my opinion is that updating the POT any time i18n strings > are added or changed is too frequent, but perhaps the current schedule > (whatever it is) is not frequent enough. > > Of course, you can always update the POT in your working copy (or > local > branch in bzr) any time you want to work on changes. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq4eOnEjvBPtnXfVAQJJ9wP6At4zRtEddCdTIfWAGARpQdyRnZkCB6NX mNmZ+T78wtCKOetQs3o7Zeklv7Am4dHCnhihM52JP76mbrykm7as3CARkkP7ck4T dRPPAyjyod9cGLfGFL2Q2/maft9vSt3A3yDxYUPBvk0bt4fj/oT9vhrAdJoPRd+x FlmKihtNuJk= =AZIp -----END PGP SIGNATURE----- From webmaster at dizain.ro Mon Jul 30 21:27:37 2007 From: webmaster at dizain.ro (Stefaniu Criste) Date: Mon, 30 Jul 2007 22:27:37 +0300 Subject: [Mailman-i18n] Updating translations In-Reply-To: <7A94A89B-6B06-4375-B0B8-BE95F521E3FE@python.org> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> <46AE0CA0.5000001@value.net> <7A94A89B-6B06-4375-B0B8-BE95F521E3FE@python.org> Message-ID: <200707302227.37953.webmaster@dizain.ro> I am trying to update Romanian translation but seems I have no permission to commit into ..../LC_MESSAGES/ro folder. - I do have my sourceforge ssh keys updated - I have tried this using KDESVN - my SF username is webdizainro Any help would be appreciated. Stefaniu Criste Romania On Monday 30 July 2007 20:22:02 Barry Warsaw wrote: > On Jul 30, 2007, at 12:06 PM, Mark Sapiro wrote: > > We don't want to keep making a moving target for translators, so in > > the > > past, we have set a point around a first beta release where i18n > > strings > > should be frozen for that release, and that's when we update the POT > > file and announce that the release is ready for translation. > > > > I am a little unclear myself on exactly how and when this is done as I > > have never done it although I have observed the results. Certainly we > > can discuss doing this more frequently. > > One idea is to try to switched to timed updates for the > translations. For example, we could say that on the 1st of every > month (i.e. Mailman Day ), we'll update the pot files and push > the changes to the official branches. Then translators will have > what they need to update their translations. We can then say that on > something like the 21st of each month, translators should send us > their updates, or make sure their branches are updated for us to merge. > > > In the recent past, I have avoided making changes to the i18n > > strings in > > the 2.1 branch, because I thought the trunk would form the basis of a > > 2.2 release in the near future. Now that 2.2 has branched from 2.1 and > > not the trunk (3.0), and it looks like the near term release will be > > 2.1.10, I will be backporting some of my trunk changes to 2.2 and some > > even to 2.1. > > Excellent Mark, thanks. > > > In any case, my opinion is that updating the POT any time i18n strings > > are added or changed is too frequent, but perhaps the current schedule > > (whatever it is) is not frequent enough. > > > > Of course, you can always update the POT in your working copy (or > > local > > branch in bzr) any time you want to work on changes. > > -Barry > > _______________________________________________ > Mailman-i18n mailing list > Posts: Mailman-i18n at python.org > Unsubscribe: > http://mail.python.org/mailman/options/mailman-i18n/webmaster%40dizain.ro From msapiro at value.net Mon Jul 30 23:38:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 30 Jul 2007 14:38:29 -0700 Subject: [Mailman-i18n] Updating translations In-Reply-To: <200707302227.37953.webmaster@dizain.ro> References: <9707FB36-8A9A-43B5-8739-E6EA84432E71@riverland.net.au> <46AE0CA0.5000001@value.net> <7A94A89B-6B06-4375-B0B8-BE95F521E3FE@python.org> <200707302227.37953.webmaster@dizain.ro> Message-ID: <46AE5A55.7020404@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefaniu Criste wrote: > I am trying to update Romanian translation but seems I have no permission to > commit into ..../LC_MESSAGES/ro folder. The Mailman SVN repository on sourceforge is now read only (see if you are having trouble reading too). Current development uses Bazaar branches hosted on Launchpad. See and for more information. Also see Barry's post at and Clytie's reply in that thread. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGrlpVVVuXXpU7hpMRAgIaAJ4hTfn7RAiBF1Dfs+tpIhkgR6TdEQCfXKZA Ja5ln1igWbh1wq/tfMPwiP0= =3KrG -----END PGP SIGNATURE----- From barry at python.org Tue Jul 31 02:14:11 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 30 Jul 2007 20:14:11 -0400 Subject: [Mailman-i18n] Using bzr for translation commits (was: Re: Slovak translation of GNU Mailman In-Reply-To: <76C75396-777B-480D-BC57-462DE6CFBAD4@riverland.net.au> References: <46A9EDDE.9060405@matuska.org> <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> <76C75396-777B-480D-BC57-462DE6CFBAD4@riverland.net.au> Message-ID: <5370B253-2E2F-4AA0-A814-C8273A04999D@python.org> -----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----- From barry at python.org Tue Jul 31 02:21:20 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 30 Jul 2007 20:21:20 -0400 Subject: [Mailman-i18n] Slovak translation of GNU Mailman In-Reply-To: <46AAF5AF.80203@zamirfamily.com> References: <46A9EDDE.9060405@matuska.org> <75EAD770-A29D-4736-8F1D-14D11BB7D2FE@python.org> <46AAF5AF.80203@zamirfamily.com> Message-ID: -----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----- From barry at python.org Tue Jul 31 02:24:50 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 30 Jul 2007 20:24:50 -0400 Subject: [Mailman-i18n] Translating via launchpad In-Reply-To: <200707291135.35774.lists@suares.an> References: <200707291135.35774.lists@suares.an> Message-ID: <679BD7FA-1189-40D0-8C8F-C185A9999404@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 29, 2007, at 11:35 AM, Ace Suares wrote: > Now mailman is in bzr, and it's alos on launchpad, can translations be > made against the launchpad interface ? For instance, in the mailman > that > is shipped with feisty, I see 228 untranslated strings... I am not > sure > if that aligns with the versions that we translated. > > Anyone can shed some light on this !? Hi Ace, We're not officially using Launchpad for translations. I know that Mailman is available on feisty, but I don't really know what is imported in Launchpad and how that differs from what we ship. At some point we'll switch to a better system, but for now, you should consider what's in our Bazaar branches to be the official translations. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq6BUnEjvBPtnXfVAQINxgP+JYwwlDhLLf5OFT0rjyRMSIArRJYgtacS XoHJYxtXqVgAW8Am+ex51lUywYBy+VQLa2Snzzq9DFm9xA8HXMrX/E9f2QcBeSYC j3kFumrmb1phP9oJ3OsjSvKdJ5hXdrh0wgS39QFzqsRSuH4SPDakzj252JqLJ9EO 2tvgKfsDcTY= =D+qQ -----END PGP SIGNATURE-----