[PATCH] Questions about missing strings, crash,
and Norwegian Translation update
Christian Stimming
stimming at tuhh.de
Fri Dec 30 06:00:03 EST 2005
(starting a new thread because this one is unrelated to the gnucash-changes
discussion)
Am Freitag, 30. Dezember 2005 07:21 schrieb linux at strigen.com:
> I have now successfully downloaded with tortoiseSvn on a memorystick and
> brought it to my linux drive, and built rev. 12195. (Worked perfect, but
> slow on the download :-)
Good to hear. That revision also has my latest string changes and the improved
tooltip displaying.
> With that version I have found the following strings missing in the po
> file, and made the program crash as well.
Ok. Not too good to hear, but certainly any kind of testing is very good in
this stage.
> I know it's a developer verison, but i supplied the bugbuddy output
> Is it usefull if I supply the crash output or is it too early in the
> develop stage/not usefull?
If you can supply a 100%-reliable way of reproducing the crash (as you did
below), then you can for now skip the bugbuddy output. We should be able to
crash it ourselves :-)
> For the strings, please advice me to supply the information in another
> way, if it is easier for you to track/find it.
> (Remember i'm not an experienced linux/gnucash/programming user :-)
Your way of supplying the missing strings looks good. I'll look into this
during the next days.
> Attached is also an updated Norwegian Bokmaal Translation file: 1973 out
> of 3417 Translated.
Thanks. Applied to SVN.
> Is there anyone who has some sample Qif, qsf, Ofx or whatever they are all
> called, so i can try the import actions & dialogs as well?
There's an OFX test file in the tarball of libofx, under doc/ofx_sample_files/
there. Note that if you imported that one once, then gnucash will remember
the unique ids of all imported transactions in the "online-id" kvp frame of
the respective transactions. That will make a second import of the file very
boring. Workaround: Before importing the OFX file a second time, edit the
gnucash file and remove the XML tags with "online-id" in them, then open the
edited gnucash file and you can import the OFX file again.
If you want to try the HBCI features, read gnucash's
src/import-export/hbci/HACKING-HBCITEST.txt
> Click File -> Open -> Budget. In the "select a budget" window:
(will look into the string problems later) As for the whole budget features,
please note that they are still considered experimental (as far as I know)
and it's not yet clear and/or decided whether these features will actually
make it into a 2.0.0 or might be delayed until a later 2.x release. So these
should probably not be your first priority for translations.
> -----------
>
> I still got the following string in the tip of the day dialog when I start
> GnuCash, even if it is translated 2 places (I know it's the tip of the day
> one)
>
> "Warning·This·is·a·DEVELOPMENT·version·of·GnuCash.·It·prob...."
> ../src/gnome/glade/totd.glade.h:3
> ../doc/tip_of_the_day.list.in:1
That one will certainly disappear for the 2.0.0 (non-development) release, so
you don't have to care too much about that.
> ------------
>
> I got the version to crash as well, to reconstruct do:
> Click File -> New -> When the account hierarchy comes up, check the
> business accounts box, press forward until the last screen, then click
> cancel. The crash1.txt file attached is the bugbuddy output.
Thanks.
Christian
More information about the gnucash-devel
mailing list