Hi, I see that we are approaching beta4 release (because Barry already checked in the comment lines in the NEWS file) and I was thinking that it would be useful to have a fresh mailman.pot in CVS about 1 week before the release. This way we translators will have a chance to resync our catalogs and ship them in the official beta4 tar.gz. I think this should be the correct procedure at least for 2.1 final. Barry, what do you think? -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo
"SP" == Simone Piunno <pioppo@ferrara.linux.it> writes:
SP> I see that we are approaching beta4 release (because Barry SP> already checked in the comment lines in the NEWS file) and I SP> was thinking that it would be useful to have a fresh SP> mailman.pot in CVS about 1 week before the release. This way SP> we translators will have a chance to resync our catalogs and SP> ship them in the official beta4 tar.gz. I think this should SP> be the correct procedure at least for 2.1 final. SP> Barry, what do you think? That works for me. I figure it will take me about a week to polish off b4, if the release of Python 2.2.2 and other Zope work goes smoothly enough. I could generate the new .pot file tonight or tomorrow. Is CVS sufficient or do you want me to upload it to SF also? -Barry
That works for me. I figure it will take me about a week to polish off b4, if the release of Python 2.2.2 and other Zope work goes smoothly enough.
good
I could generate the new .pot file tonight or tomorrow. Is CVS sufficient or do you want me to upload it to SF also?
CVS is enough for me, thanks. -- This signature intentionally left blank
Hi, I like the idea and welcome the decision Barry made. Just FYI, anyone can generate a fresh mailman.pot by typing $ make mailman.pot at $mailmansrc/messages directory. You may have to remove mailman.pot and *.files for really fresh generation. BTW, I always have to edit Makefile s/>|/>/g to do this job. Is it standard to use '>|' instead of just '>' for redirection ? Simone Piunno wrote:
Hi,
I see that we are approaching beta4 release (because Barry already checked in the comment lines in the NEWS file) and I was thinking that it would be useful to have a fresh mailman.pot in CVS about 1 week before the release. This way we translators will have a chance to resync our catalogs and ship them in the official beta4 tar.gz. I think this should be the correct procedure at least for 2.1 final.
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
Tokio Kikuchi <tkikuchi@is.kochi-u.ac.jp> writes:
Just FYI, anyone can generate a fresh mailman.pot by typing $ make mailman.pot at $mailmansrc/messages directory. You may have to remove mailman.pot and *.files for really fresh generation.
On a procedural note: While this is the case, I would recommend that translators stick to "official" templates generated by the project maintainer (i.e. Barry). That way, it is easier to identify catalogs later on, as the POT-Creation-Date will refer to one of a few official templates. Regards, Martin
"TK" == Tokio Kikuchi <tkikuchi@is.kochi-u.ac.jp> writes:
TK> BTW, I always have to edit Makefile s/>|/>/g to do this job. TK> Is it standard to use '>|' instead of just '>' for redirection TK> ? AFAIK, >| is the bash-ism for "stick the output in this file, overwriting it if it exists", and since I use bash... :) BTW, mailman.pot update has been checked in. -Barry
participants (4)
-
barry＠python.org -
loewis＠informatik.hu-berlin.de -
Simone Piunno -
Tokio Kikuchi