--On February 5, 2006 3:01:13 PM -0500 Josh Sled
<[EMAIL PROTECTED]> wrote:
On Sun, 2006-02-05 at 14:37 -0500, Mike Alexander wrote:
When I added these (and a catalog to map the URI to the DTD), Epic
found the DTD, but it complained about a number of errors in it. I
haven't tracked them down
Christian Stimming wrote:
You are referring to the 1.8.x translations, where we had a (say) 1.8.5
release out there, and the next 1.8.6 release needed a little bit translation
work. The fundamental problem was that the translators of course couldn't
wait for the official 1.8.6 release (becau
Am Sonntag, 5. Februar 2006 19:59 schrieb Nigel Titley:
> (...) but in the past Christian has occassionaly forgotten to send
> the .pot file to the translation project until the last minute. In this
> particular instance, with so many new strings to translate I felt that
> as much time as possible
Am Sonntag, 5. Februar 2006 15:51 schrieb Neil Williams:
> > > Are we having a string freeze before 1.9.0?
Yes, we will need a formal "string freeze" period, and we (read: me) will have
a clear definition for what this means. But not in 1.9.0. In one of the later
1.9.x releases.
> > http://wik
On Sun, 2006-02-05 at 14:37 -0500, Mike Alexander wrote:
> When I added these (and a catalog to map the URI to the DTD), Epic
> found the DTD, but it complained about a number of errors in it. I
> haven't tracked them down yet.
Which DTD? If it's one(s) from the gnucash source tree, it's like
--On February 4, 2006 11:34:46 PM -0500 Chris Shoemaker
<[EMAIL PROTECTED]> wrote:
On Sat, Feb 04, 2006 at 06:56:57PM -0500, Joshua Sled wrote:
FYI,
nXML shows the following for my datafile:
"Unknown element"
"Element not allowed in this context"
"Unknown element"
hbci
Quoting Nigel Titley <[EMAIL PROTECTED]>:
Neil Williams wrote:
(When I did some work on the en_GB translation, I was asked if it
was possible to allow a *lot* more time for other translations than
gnucash may have done historically.)
This request came from me. I'm not concerned so much fo
Neil Williams wrote:
Personally, as a gnucash user in the UK, I'd much rather *not* have zero
padding on data entry or data display of UK date formats.
There is no UK consensus on whether 04/02/06 is preferable to 4/2/6 or 4/2/06.
It's a "problem" of the 21st century where single digit years
On Sunday 05 February 2006 6:59 pm, Neil Williams wrote:
> On Sunday 05 February 2006 6:36 pm, Derek Atkins wrote:
> > A good question. If it works with 2.4.13 then we can change the
> > configure script. If it doesn't work with 2.4.13, well, I'm happy
> > telling people they need an updated FC3.
Neil Williams wrote:
(When I did some work on the en_GB translation, I was asked if it was possible
to allow a *lot* more time for other translations than gnucash may have done
historically.)
This request came from me. I'm not concerned so much for the en_GB
translation, as between Neil a
On Sunday 05 February 2006 6:36 pm, Derek Atkins wrote:
> A good question. If it works with 2.4.13 then we can change the configure
> script. If it doesn't work with 2.4.13, well, I'm happy telling people
> they need an updated FC3. :)
OK, I got passed with gtk+-2.0 == 2.4.13 by tweaking configu
A good question. If it works with 2.4.13 then we can change the configure
script. If it doesn't work with 2.4.13, well, I'm happy telling people they
need an updated FC3. :)
-derek
Quoting Neil Williams <[EMAIL PROTECTED]>:
When we say we are targetting FC3 as target platform, does that mean
When we say we are targetting FC3 as target platform, does that mean a
completely default FC3 or a regularly updated FC3?
I can't build gnucash on my vanilla FC3, gtk+-2.0 is being reported as
(slightly) too old. I have 2.4.13 and ./configure is complaining about not
having 2.4.14. It then ment
On Sunday 05 February 2006 2:27 pm, you wrote:
> On Sun, 2006-02-05 at 11:59 +, Neil Williams wrote:
> > Are we having a string freeze before 1.9.0? If not (and there probably
> > isn't time) can we _use_ 1.9.0 as a platform to get the other translators
> > started on the work for gnucash 2.0.0
On Sun, 2006-02-05 at 11:59 +, Neil Williams wrote:
> Are we having a string freeze before 1.9.0? If not (and there probably isn't
> time) can we _use_ 1.9.0 as a platform to get the other translators started
> on the work for gnucash 2.0.0 ?
Have you read http://wiki.gnucash.org/wiki/Releas
В Суб, 04/02/2006 в 09:25 +0100, Didier Vidal пишет:
> Have you tried to add (manually) the encoding of your files in the
> header of the XML gnucash 1.8 files ?
> Instead of starting the file with
>
>
>
> start with
>
>
Please read:
http://bugzilla.gnome.org/show_bug.cgi?id=329202
--
П
Are we having a string freeze before 1.9.0? If not (and there probably isn't
time) can we _use_ 1.9.0 as a platform to get the other translators started
on the work for gnucash 2.0.0 ?
There are a huge number of modified translatable strings going from 1.8 to
1.9.0 and even if some of those in
17 matches
Mail list logo
