There is no "latest build". The g2 release is still in progress.
You're welcome to pull it from CVS like everyone else.
-derek
Pawan Chitrakar <[EMAIL PROTECTED]> writes:
> Dear All,
>
> We are working on gnucash translation to Nepali and we are not been able to
> get the translated strings in
Dear All,
We are working on gnucash translation to Nepali and we are not been
able to get the translated strings in nepali and we are glad that now
it is being ported to Gnome2/gtk+
Could we get the latest build with UTF-8 support so that we can start checking our translation.
Thanks in advance
Le dim 25/09/2005 à 22:53, Derek Atkins a écrit :
> Quoting Didier Vidal <[EMAIL PROTECTED]>:
>
> [snip]
>
> Good to hear the tests worked. That bodes well.
>
> > But maybe one could add a unit test in gnucash that opens a gnucash file
> > with non ascii parameters, and checks that the objects
Quoting Didier Vidal <[EMAIL PROTECTED]>:
[snip]
Good to hear the tests worked. That bodes well.
But maybe one could add a unit test in gnucash that opens a gnucash file
with non ascii parameters, and checks that the objects are built
properly. The test could even save the file and read it ag
Le dim 25/09/2005 à 22:20, Derek Atkins a écrit :
> Didier Vidal <[EMAIL PROTECTED]> writes:
>
> > Even with 2.6.16 of libxml, there is no *visible* problem as long as you
> > keep opening your file with libxml.
>
> Oh? So if you save it with gnucash + libxml2-2.6.16 and then open
> it with gnuc
Didier Vidal <[EMAIL PROTECTED]> writes:
> Even with 2.6.16 of libxml, there is no *visible* problem as long as you
> keep opening your file with libxml.
Oh? So if you save it with gnucash + libxml2-2.6.16 and then open
it with gnucash + libxml2-2.2.x, it will do the right thing? Even if
we har
Le dim 25/09/2005 à 19:08, Didier Vidal a écrit :
> First, I apologize for an error I made in parent email. The libxml
> version I tested that fixed the problem is 2.6.22. It didn't require any
> change in the gnucash code (ie: still using xmlNodeDump)
I meant xmlElemDump
Didier.
First, I apologize for an error I made in parent email. The libxml
version I tested that fixed the problem is 2.6.22. It didn't require any
change in the gnucash code (ie: still using xmlNodeDump)
The actual bug report in libxml is
http://bugzilla.gnome.org/show_bug.cgi?id=159547
Daniel Veillard
On Sunday 25 September 2005 4:40 pm, Didier Vidal wrote:
> gnucash looks fine with utf-8. Neil's suggestion to write the encoding
> in write_v2_header in io-gncxml-v2.c makes a lot of sense.
(I wish my other code problems were so easy to solve!)
> The error I observed ("é" written with an ISO-885
Le dim 25/09/2005 à 18:03, Derek Atkins a écrit :
> Quoting David Hampton <[EMAIL PROTECTED]>:
>
> > On Sun, 2005-09-25 at 17:40 +0200, Didier Vidal wrote:
> >
> >> >From my tests, with a correct libxml realease, gnucash writes in utf-8
> >> whatever the current locale is.
> >>
> >> So, there is n
Quoting David Hampton <[EMAIL PROTECTED]>:
On Sun, 2005-09-25 at 17:40 +0200, Didier Vidal wrote:
>From my tests, with a correct libxml realease, gnucash writes in utf-8
whatever the current locale is.
So, there is no encoding problem.
Hallelujah!
Except for the fact that FC3 ships 2.6.16
On Sun, 2005-09-25 at 17:40 +0200, Didier Vidal wrote:
> >From my tests, with a correct libxml realease, gnucash writes in utf-8
> whatever the current locale is.
>
> So, there is no encoding problem.
Hallelujah!
David
___
gnucash-devel mailing list
Finally,
gnucash looks fine with utf-8. Neil's suggestion to write the encoding
in write_v2_header in io-gncxml-v2.c makes a lot of sense.
The error I observed ("é" written with an ISO-8859-1 encoding) was due
to a bug in libxml. I had libxml 2.6.16 on my machine.
I downloaded libxml 2.6.20 and
13 matches
Mail list logo
