1.9.6
Andreas Köhler
andi5.py at gmx.net
Sat May 27 06:18:28 EDT 2006
Hi,
On Saturday, 27 May 2006, 04:48 CEST, don Paolo Benvenuto wrote:
> I installed 1.9.6 from unstable.
>
> First impressions.
>
> - The xml conversion druid: it's drammatically frightening the newbye.
> Some more explication is due.
>
> It showed me a cyrillic encoding, and I can't understand why: I have a
> localization es_DO, I suppose it should have shown UTF, ISO8859-1,
> iso8859-15.
The translator specifies which encodings should be presented to the
user. Please ask yours to change the list to something more
reasonable.
> Besides that, everyone knows that 1.8 didn't use UTF-8, so why present
> this possibility?
1.8 used what it got. So if you ran it in a UTF-8 locale, you got a
data file with UTF8 strings. It was just as easy to mix encodings:
Simply run GnuCash 1.8 twice in different locales and create some
transactions. The druid pops up when your data file does not specify
an encoding, it does not know anything about the environment
(program version, locales) the file was created or modified with.
> Every time a different localization is chosen, the druid apparently
> must re-read all the file, with very large times for me (my data file is
> 43 M).
I will try to improve that.
> If UTF-8 is selected, in the drop down lists nothing is shown: UTF-8
> doesn't permit to read those strings?
Perfectly possible.
> When I put the cursor over a drop down lists, the letters get the
> colors of the tool, and so I can't read the string (the same thing is
> present in all gnucash2)
Is GnuCash2 the only GTK2 application with this behavior?
> The conversion of my 43M file took 2 minutes.
GnuCash reads the old file with the specified substitutions and
saves it afterwards. This takes a little time, but you can be sure
that GnuCash will be able to read the file now.
> - When the conversion druid ends, the main gnucash window is presented,
> reading again the file (2 more minutes). The indicator in the bottom
> right corner moves very very very rapidly! Fortunately after a short
> time it gets tired and reduces the speed!
GnuCash is reading the new file.
You might think that reading the file twice is a waste of time, but
it was by far the easiest implementation.
> [...]
-- andi5
More information about the gnucash-devel
mailing list