On Thu, 2010-02-04 at 22:50 +0200, F Wolff wrote:
> Op Wo, 2010-02-03 om 16:59 + skryf Bruce Cowan:
> > I proposed a string strike force last August[0]. I think it was a
> > reasonably well received, but I think the idea lost steam due to it
> > being the wrong time of
Op Wo, 2010-02-03 om 16:59 + skryf Bruce Cowan:
> I proposed a string strike force last August[0]. I think it was a
> reasonably well received, but I think the idea lost steam due to it
> being the wrong time of year. Now that string freeze is nearly upon us,
> I thought I'
On Wed, 2010-02-03 at 16:59 +, Bruce Cowan wrote:
> I proposed a string strike force last August[0]. I think it was a
> reasonably well received, but I think the idea lost steam due to it
> being the wrong time of year. Now that string freeze is nearly upon us,
> I thought I'
On Wed, 2010-02-03 at 21:10 +0100, Claude Paroz wrote:
> Le mercredi 03 février 2010 à 16:59 +, Bruce Cowan a écrit :
> > I proposed a string strike force last August[0]. I think it was a
> > reasonably well received, but I think the idea lost steam due to it
> > being t
Le mercredi 03 février 2010 à 16:59 +, Bruce Cowan a écrit :
> I proposed a string strike force last August[0]. I think it was a
> reasonably well received, but I think the idea lost steam due to it
> being the wrong time of year. Now that string freeze is nearly upon us,
> I thoug
I proposed a string strike force last August[0]. I think it was a
reasonably well received, but I think the idea lost steam due to it
being the wrong time of year. Now that string freeze is nearly upon us,
I thought I'd start the ball rolling again.
I think that the best way to go would
Sorry about the late reply, but I've been very busy with things.
On Wed, 2009-09-30 at 11:56 +0200, Chusslove Illich wrote:
> (A KDE translator here.)
>
> > [: Philip Withnall :]
> > [...] My suggestion would be to translate strings to review them, and
> > discuss them (or explain any fixes) in t
can't be changed (easily). Of course, I could have started earlier, but
> I didn't for some reason.
>
> Anyway, I thought that a sort of "string strike force" may be a good
> idea. Essentially it would audit strings while they can still be fixed.
>
> The en_GB
Op Vr, 2009-08-28 om 10:20 -0500 skryf Shaun McCance:
> On Thu, 2009-08-27 at 08:59 +0200, Claude Paroz wrote:
> > Le mercredi 26 août 2009 à 17:13 -0500, Shaun McCance a écrit :
> > > On Wed, 2009-08-26 at 23:02 +0100, Bruce Cowan wrote:
...
> The problem is that we might not be able to finish t
2009/8/28 Shaun McCance :
> I was thinking of using PO files for string reviews. We'd
> have some faux language code (x-string-review.po), and some
> defined syntax that allows people to check off strings.
>
> I could add a plugin to Pulse that would read these and
> report which strings have had
f course, I could have started earlier, but
> > > > I didn't for some reason.
> > > >
> > > > Anyway, I thought that a sort of "string strike force" may be a good
> > > > idea. Essentially it would audit strings while they can still be fix
the grammar and spelling of the original strings. However, most of the
> > > work of the team seems to be done after string freeze, when the strings
> > > can't be changed (easily). Of course, I could have started earlier, but
> > > I didn't for some reason.
> &g
On Thu, 2009-08-27 at 17:36 +0100, Bruce Cowan wrote:
> On Thu, 2009-08-27 at 09:44 +0200, F Wolff wrote:
> > > The difficulty might lie in the timeframe devoted to this review
> > > process. If it's too soon, it might lead to time waste, because strings
> > > can still change. What about some "str
On Thu, 2009-08-27 at 09:44 +0200, F Wolff wrote:
> > The difficulty might lie in the timeframe devoted to this review
> > process. If it's too soon, it might lead to time waste, because strings
> > can still change. What about some "string sprint" the week-end just
> > before string freeze?
> >
>
El jue, 27-08-2009 a las 15:01 +0200, Petr Kovar escribió:
> What comes to my mind first is checking for ngettext use where appropriate.
> As I can see, pofilter warns user when it encounters singular and
> plural appended to a word in the original string. Fragments like "file(s)"
> represent a lo
eam seems to be done after string freeze, when the strings
> > can't be changed (easily). Of course, I could have started earlier, but
> > I didn't for some reason.
> >
> > Anyway, I thought that a sort of "string strike force" may be a good
>
eam seems to be done after string freeze, when the strings
> > can't be changed (easily). Of course, I could have started earlier, but
> > I didn't for some reason.
> >
> > Anyway, I thought that a sort of "string strike force" may be a good
>
7;t be changed (easily). Of course, I could have started earlier, but
> I didn't for some reason.
>
> Anyway, I thought that a sort of "string strike force" may be a good
> idea. Essentially it would audit strings while they can still be fixed.
>
> The en_GB
the grammar and spelling of the original strings. However, most of the
> > > work of the team seems to be done after string freeze, when the strings
> > > can't be changed (easily). Of course, I could have started earlier, but
> > > I didn't for some reason.
> &g
gt; work of the team seems to be done after string freeze, when the strings
> > can't be changed (easily). Of course, I could have started earlier, but
> > I didn't for some reason.
> >
> > Anyway, I thought that a sort of "string strike force" may be a goo
2009/8/27 Shaun McCance :
>
> The documentation team has discussed doing this before.
> We'd like to look for more than just spelling and grammar
> problems. Notably:
>
> 1) Making sure terminology matches our style guide
> 2) Fixing awkward and confusing sentences
> 3) Checking for things that ca
On Wed, 2009-08-26 at 17:13 -0500, Shaun McCance wrote:
> The documentation team has discussed doing this before.
> We'd like to look for more than just spelling and grammar
> problems. Notably:
>
> 1) Making sure terminology matches our style guide
> 2) Fixing awkward and confusing sentences
>
can't be changed (easily). Of course, I could have started earlier, but
> I didn't for some reason.
>
> Anyway, I thought that a sort of "string strike force" may be a good
> idea. Essentially it would audit strings while they can still be fixed.
>
> The en_GB
didn't for some reason.
Anyway, I thought that a sort of "string strike force" may be a good
idea. Essentially it would audit strings while they can still be fixed.
The en_GB team could take this on itself, but it's probably a bit
24 matches
Mail list logo
