4:21 p.m.
Hi,
I think po4a is in a releasable state.
I'm not sure about how to add the LaTeX and TeX modules (only add them in
the MANIFEST?). If somebody can do this, it would be nice.
However, it could be nice to plan a 20.1 to fix some non blocking issue:
* the with-{hyphen_to_minus,non_breaking_spaces} options (Man module)
is a bogus fix.
see thread "po4a/t 02-TransTractors.t,1.8,1.9"
* there are some martin.quinson(a)tuxfamily.org email address in the
source (I don't know if Martin wants to change them)
* there were no string freeze before this release, and there were some
string change recently.
* the LaTeX module may have nasty bugs not found during testing.
* Danilo raised an issue regarding the wrapping
It may be a little late to send this status, but if you have any comment,
please send it.
Martin wanted to release tomorrow.
--
Nekral
4:52 p.m.
Hi,
On Sun, 27 Feb 2005, Nicolas François wrote:
I'm not sure about how to add the LaTeX and TeX modules (only add
them in
the MANIFEST?). If somebody can do this, it would be nice.
I've just added them to the MANIFEST. The next step would be to edit the
chooser, to deal with the lowercase names of these modules, and to add
their descriptions (we should have at least one or two days to add their
translations)
Regards,
Jordi Vilalta
5:19 p.m.
Hi,
On Sun, Feb 27, 2005 at 11:52:44PM +0100, Jordi Vilalta wrote:
On Sun, 27 Feb 2005, Nicolas François wrote:
>I'm not sure about how to add the LaTeX and TeX modules (only add them in
>the MANIFEST?). If somebody can do this, it would be nice.
I've just added them to the MANIFEST. The next step would be to edit the
chooser, to deal with the lowercase names of these modules, and to add
their descriptions (we should have at least one or two days to add their
translations)
Thanks a lot Jordi.
I will edit the chooser.
--
Nekral
5:08 p.m.
On Sun, Feb 27, 2005 at 11:21:17PM +0100, Nicolas François wrote:
Hi,
I think po4a is in a releasable state.
I'm not sure about how to add the LaTeX and TeX modules (only add them in
the MANIFEST?). If somebody can do this, it would be nice.
However, it could be nice to plan a 20.1 to fix some non blocking issue:
* the with-{hyphen_to_minus,non_breaking_spaces} options (Man module)
is a bogus fix.
see thread "po4a/t 02-TransTractors.t,1.8,1.9"
* there are some martin.quinson(a)tuxfamily.org email address in the
source (I don't know if Martin wants to change them)
Done.
* there were no string freeze before this release, and there were
some
string change recently.
* the LaTeX module may have nasty bugs not found during testing.
* Danilo raised an issue regarding the wrapping
It may be a little late to send this status, but if you have any comment,
please send it.
We can do a dot release in a few weeks to fix those issues.
Martin wanted to release tomorrow.
;) It's not like I am in position of deciding what happens in po4a, but I
think that the changelog is long enough to release. That's why I'd like to
move slowly to a release. I don't want to rush things out either.
Thanks for your time, Mt.
5:16 p.m.
On Mon, Feb 28, 2005 at 12:08:34AM +0100, Martin Quinson wrote:
> Martin wanted to release tomorrow.
;) It's not like I am in position of deciding what happens in po4a, but I
think that the changelog is long enough to release. That's why I'd like to
move slowly to a release. I don't want to rush things out either.
It was a good excuse to push for a release ;)
--
Nekral
4:10 a.m.
On Sun, Feb 27, 2005 at 11:21:17PM +0100, Nicolas François wrote:
Hi,
I think po4a is in a releasable state.
Almost, I think.
I'm not sure about how to add the LaTeX and TeX modules (only add
them in
the MANIFEST?). If somebody can do this, it would be nice.
Jordi did that.
However, it could be nice to plan a 20.1 to fix some non blocking
issue:
* the with-{hyphen_to_minus,non_breaking_spaces} options (Man module)
is a bogus fix.
see thread "po4a/t 02-TransTractors.t,1.8,1.9"
Denis said that in his mind, this is not a blocker since removing the "\ "
from the english page fixes the issue. I agree.
* there are some martin.quinson(a)tuxfamily.org email address in the
source (I don't know if Martin wants to change them)
killed.
* there were no string freeze before this release, and there were
some
string change recently.
Jordi did just update his translations, and I think we can do a dot release
in a few to update the translations.
* the LaTeX module may have nasty bugs not found during testing.
That's why we need to release: to increase its audiance ;)
* Danilo raised an issue regarding the wrapping
He said that if the wrap would obey to the COLUMNS env variable, it would be
enough. This is still to be done, but that's not a big deal.
Jordi, are you on it or may I do it?
Martin wanted to release tomorrow.
Still true ;)
Bye, Mt.
3:42 p.m.
Hi,
On Wed, 2 Mar 2005, Martin Quinson wrote:
> * Danilo raised an issue regarding the wrapping
He said that if the wrap would obey to the COLUMNS env variable, it would be
enough. This is still to be done, but that's not a big deal.
Jordi, are you on it or may I do it?
I haven't used env variables in perl, so maybe you could get it faster ;)
Regards,
Jordi Vilalta
4:21 a.m.
New subject: [Po4a-devel]0.20 release plan
>> * Danilo raised an issue regarding the wrapping
>He said that if the wrap would obey to the COLUMNS env variable, it would
>be enough. This is still to be done, but that's not a big deal.
>Jordi, are you on it or may I do it?
I haven't used env variables in perl, so maybe you could get it faster ;)
Done (google is sooo cool).
So. People. I think we're done with 0.20. I think I'll release this WE, if
no major issue is found in the meantime. So, we have a few days to update
the translations. Here is the current status:
po/bin (pot: 16K)
ca: 115 translated messages.
es: 115 translated messages.
fr: 114 translated messages, 1 untranslated message.
it: 114 translated messages, 1 untranslated message.
af: 23 translated messages, 2 fuzzy translations, 90 untranslated messages.
cs: 11 translated messages, 7 fuzzy translations, 97 untranslated messages.
de: 42 translated messages, 6 fuzzy translations, 67 untranslated messages.
po/pod (pot: 204K)
ca: 760 translated messages, 84 fuzzy translations, 97 untranslated messages.
es: 759 translated messages, 84 fuzzy translations, 98 untranslated messages.
fr: 879 translated messages, 17 fuzzy translations, 45 untranslated messages.
it: 265 translated messages, 73 fuzzy translations, 603 untranslated messages.
I thus democratically decide that we are in feature freeze, and that we will
stay so until after 0.20 reaches the debian testing distribution. In other
words, we are in debugging and translating phase for one week or two.
If someone wants to speak against it, he's welcome :)
Mt.
9:34 a.m.
New subject: [Po4a-devel]0.20 release plan
On Thursday 03 March 2005 11:21, Martin Quinson wrote:
> >He said that if the wrap would obey to the COLUMNS env
variable, it
> > would be enough. This is still to be done, but that's not a big deal.
> > Jordi, are you on it or may I do it?
>
> I haven't used env variables in perl, so maybe you could get it faster ;)
Done (google is sooo cool).
Er... I can't make it work, neither with po4a nor with a small test script
(see the attached 'wraptest' file).
It looks like that the COLUMNS env variable isn't passed to perl (see the
attached 'columnstest' file), unless it is explicitly set from the shell
(i.e. COLUMNS=$COLUMNS perl ./columnstest).
Again, this is only a cosmetic issue. Don't worry too much about it :-)
Cheers,
Danilo
9:57 a.m.
New subject: [Po4a-devel]0.20 release plan
On Thu, Mar 03, 2005 at 04:34:56PM +0100, Danilo Piazzalunga wrote:
Er... I can't make it work, neither with po4a nor with a small
test script
(see the attached 'wraptest' file).
It looks like that the COLUMNS env variable isn't passed to perl (see the
attached 'columnstest' file), unless it is explicitly set from the shell
(i.e. COLUMNS=$COLUMNS perl ./columnstest).
That's right, COLUMNS is actually a bash variable, and is
not normally part of the environment. You can get it from
the output of resize(1) though:
#! /usr/bin/perl
$columns = (`resize` =~ /COLUMNS=(\d+)/)[0];
print $columns;
I'll let it up to who will maintain that code to write it in
a more palatable way :-)
Y.
10:31 a.m.
New subject: [Po4a-devel]0.20 release plan
On Thursday 03 March 2005 16:57, Yves Rutschle wrote:
That's right, COLUMNS is actually a bash variable, and is
not normally part of the environment. You can get it from
the output of resize(1) though:
Great idea, thank you! :-) Why didn't I think about that before? A simple
command which prints them out...
...But resize is part of X (even if it doesn't use xlibs), and we don't want
to depend on xutils for that...
...Here comes tput: simply using
$columns = (`tput cols`);
print $columns;
will solve all of our problems, and tput is part of ncurses-bin (essential
package), so no additional dependencies are introduced.
Thank you again,
Danilo
10:53 a.m.
New subject: [Po4a-devel]0.20 release plan
On Thu, Mar 03, 2005 at 05:31:37PM +0100, Danilo Piazzalunga wrote:
...But resize is part of X (even if it doesn't use xlibs), and we
don't want
to depend on xutils for that...
That's not good.
$columns = (`tput cols`);
print $columns;
That's better.
will solve all of our problems, and tput is part of ncurses-bin
(essential
package), so no additional dependencies are introduced.
I think Martin's solution with Term::ReadLine is the
cleanest really, I think those modules are standard enough
that they'd be installed anywhere.
Y.
10:04 a.m.
New subject: [Po4a-devel]0.20 release plan
On Thu, Mar 03, 2005 at 04:34:56PM +0100, Danilo Piazzalunga wrote:
On Thursday 03 March 2005 11:21, Martin Quinson wrote:
> > >He said that if the wrap would obey to the COLUMNS env variable, it
> > > would be enough. This is still to be done, but that's not a big deal.
> > > Jordi, are you on it or may I do it?
> >
> > I haven't used env variables in perl, so maybe you could get it faster ;)
>
> Done (google is sooo cool).
Er... I can't make it work, neither with po4a nor with a small test script
(see the attached 'wraptest' file).
It looks like that the COLUMNS env variable isn't passed to perl (see the
attached 'columnstest' file), unless it is explicitly set from the shell
(i.e. COLUMNS=$COLUMNS perl ./columnstest).
If it's not set explicitly from the env, you have to play the Term::ReadKey
I did.
Erm, not exactly. Give me 5mn, and I'll commit a *tested* version of that
crap. Sorry.
Again, this is only a cosmetic issue. Don't worry too much about
it :-)
If we can get it right, let's do it.
Thanks for your patience,
Mt.
7206
days inactive
7210
days old
12 comments
5 participants
participants (5)
-
Danilo Piazzalunga -
Jordi Vilalta -
Martin Quinson -
Nicolas François -
Yves Rutschle