How are CVS Revision numbers used today? The best feature of po is
that translation text is marked as 'fuzzy' when the main text is
changed. If we could do the same with our docbook translation files
whenever the en file is committed then we have the same benefits
imo. I'm wondering if CV
> Our main problem is with translations because CVS Revision numbers are
> required today and used with translations to track/sync with EN. I was
> hoping the gettext/po effort would have gone smoother by now but it hasn't.
> So, I ask that people think about solutions for how we handle this, and
On Jul 8, 2009, at 9:34 AM, Anthony Bedford wrote:
On 8 Jul 2009, at 03:56, Philip Olson wrote:
Soon the entire PHP project will throw itself into the fire and
migrate from CVS to SVN. This will break many activities here but
the task of editing EN DocBook files likely won't change much,
On 8 Jul 2009, at 03:56, Philip Olson wrote:
Soon the entire PHP project will throw itself into the fire and
migrate from CVS to SVN. This will break many activities here but
the task of editing EN DocBook files likely won't change much,
except for the commands to checkout/commit.
Will o
On Jul 8, 2009, at 12:38 AM, Hannes Magnusson wrote:
On Wed, Jul 8, 2009 at 04:56, Philip Olson wrote:
Our main problem is with translations because CVS Revision numbers
are
required today and used with translations to track/sync with EN. I
was
hoping the gettext/po effort would have gone s
On Wed, Jul 8, 2009 at 04:56, Philip Olson wrote:
> Our main problem is with translations because CVS Revision numbers are
> required today and used with translations to track/sync with EN. I was
> hoping the gettext/po effort would have gone smoother by now but it hasn't.
> So, I ask that people
