French translation
Hi, I have noticed the french portal of you website might need a little proof read. The translation is barely understandable (both syntax and spelling need checking). I would be willing to help you out fixing this (at least the welcome part of the webpage for the moment) Let me know on how i can help out. Keep up the good work. The software is great. j -- Jeremie Gaucher ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Win32 build problem
Hello all, I tried to build gnucash on Windows today, with the automatic build script. Everything went well until the GOffice-Stage: ### GOffice Extracting goffice-0.3.0.tar.bz2 ... done patching file `configure.in' patching file `goffice/utils/go-file.c' patching file `configure.in' patching file `goffice/Makefile.am' gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:134: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here And that's it, the build stops. Any ideas? regards, Stefan PS: please CC me, I'm not on the list. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Win32 build problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 See https://lists.gnucash.org/pipermail/gnucash-devel/2006-October/018688.html and the necessary file starts in the archived article below --- next part ---. We'll fix this in SVN soon, but right now I don't have time. Christian Stefan Schwandter schrieb: Hello all, I tried to build gnucash on Windows today, with the automatic build script. Everything went well until the GOffice-Stage: ### GOffice Extracting goffice-0.3.0.tar.bz2 ... done patching file `configure.in' patching file `goffice/utils/go-file.c' patching file `configure.in' patching file `goffice/Makefile.am' gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:134: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here And that's it, the build stops. Any ideas? regards, Stefan PS: please CC me, I'm not on the list. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRS0UhWXAi+BfhivFAQK0lQP/U/FWDBsPMx5qrxOwvGwwXhJvWqT6+KSm w3ec2fr0Wc1TfZ9zp0JnjFNx0RU0O2/zWBRp+GRc2L9DkB0oYoElTw0BXdLbb100 wv/y3R+Y4Csq7Cb+C38h8ljF17xAm+vj7lW2jB1ABFInrnkBoKy1T4/1TFIEgPpA dewM9BWnoHM= =f9ZQ -END PGP SIGNATURE- ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: French translation
Hi, Thank you for volunteering. You can find the PO file for translation in subversion: http://svn.gnucash.org/repo/htdocs/trunk/po/fr.po Just send us an updated version of that file and we can put it up for you. Thanks, -derek Jeremie Gaucher [EMAIL PROTECTED] writes: Hi, I have noticed the french portal of you website might need a little proof read. The translation is barely understandable (both syntax and spelling need checking). I would be willing to help you out fixing this (at least the welcome part of the webpage for the moment) Let me know on how i can help out. Keep up the good work. The software is great. j -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Win32 build problem
Oh, I suspect that when we changed from installing glade to installing individual packages we just didn't install gtk-doc. We should just install the gtk-doc package, too. -derek Christian Stimming [EMAIL PROTECTED] writes: See https://lists.gnucash.org/pipermail/gnucash-devel/2006-October/018688.html and the necessary file starts in the archived article below --- next part ---. We'll fix this in SVN soon, but right now I don't have time. Christian Stefan Schwandter schrieb: Hello all, I tried to build gnucash on Windows today, with the automatic build script. Everything went well until the GOffice-Stage: ### GOffice Extracting goffice-0.3.0.tar.bz2 ... done patching file `configure.in' patching file `goffice/utils/go-file.c' patching file `configure.in' patching file `goffice/Makefile.am' gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:134: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here And that's it, the build stops. Any ideas? regards, Stefan PS: please CC me, I'm not on the list. -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: SWIGification status, Part 2
As of last night this branch built cleanly (modulo the -Wno-unused flag) AND it passed make check. Nice job, guys! Granted, it requires swig-1.3.28, which is newer than what's in FC5 -- but a simple backport of 1.3.29 from FC6 and all is happy. -derek Chris Shoemaker [EMAIL PROTECTED] writes: Devs and Testers, The swig-redo branch has a swigified GnuCash. I've smoke-tested it, but it needs some more exercise. Several steps in the process were pretty manual and error-prone. Fortunately, the type of bugs I'm most likely to have introduced are very easy to fix. The whole process went pretty smoothly except for one horrendous bug that killed many, many hours. (Giving guile a NULL when it expects an SCM_UNDEFINED will eventually bite you, perhaps sometime in the distant future and in the bowels of the garbage collector.) I'm even more impressed with SWIG's flexibility than I previously was, and I've continued to receive good support from swig-user. I expect there are some gwrap-specific tests that still have to be disabled, and probably some dist-check related errors, but otherwise, it's ready to be stress-tested. I hope it will get some review/comments in the swig-redo branch, but I hope it can be merged to trunk for wider testing soon. If you notice any regressions from trunk please send them here. -chris ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Win32 build problem
I had this problem too. Christian gave me a workaround in the thread earlier this month with subject GnuCash on Windows - problem with install.sh and GOffice. Here is a copy of that message: https://lists.gnucash.org/pipermail/gnucash-devel/2006-October/018688.html By the way, I don't know if this helps any of the devs, but I found some information in cases where other people setup a fake GTK-Doc package. http://www.go-evolution.org/Building_Evolution_on_Windows#Fake_gtk-doc http://mail.gnome.org/archives/gtk-devel-list/2005-January/msg00091.html Mike Taylor Derek Atkins wrote: Oh, I suspect that when we changed from installing glade to installing individual packages we just didn't install gtk-doc. We should just install the gtk-doc package, too. -derek Christian Stimming [EMAIL PROTECTED] writes: See https://lists.gnucash.org/pipermail/gnucash-devel/2006-October/018688.html and the necessary file starts in the archived article below --- next part ---. We'll fix this in SVN soon, but right now I don't have time. Christian Stefan Schwandter schrieb: Hello all, I tried to build gnucash on Windows today, with the automatic build script. Everything went well until the GOffice-Stage: ### GOffice Extracting goffice-0.3.0.tar.bz2 ... done patching file `configure.in' patching file `goffice/utils/go-file.c' patching file `configure.in' patching file `goffice/Makefile.am' gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:134: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here And that's it, the build stops. Any ideas? regards, Stefan PS: please CC me, I'm not on the list. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Win32 build problem
Hi, See https://lists.gnucash.org/pipermail/gnucash-devel/2006-October/018688.html and the necessary file starts in the archived article below --- next part ---. We'll fix this in SVN soon, but right now I don't have time. Done in r15007. @Stefan: May you retry and report further errors? @Derek: I think this is due to the additional aclocal call, which overwrites the macros in aclocal.m4. I have not seen gtk-doc.zip yet. @Mike: Yes, I have seen those and implemented a subset by only copying gtk-doc.m4. I hope it works nonetheless :) Extracting goffice-0.3.0.tar.bz2 ... done patching file `configure.in' patching file `goffice/utils/go-file.c' patching file `configure.in' patching file `goffice/Makefile.am' gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here gtk-doc.make:134: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:68: `gtk-doc.make' included from here PS: Webmail sucks ;-) -- GMX DSL-Flatrate 0,- Euro* - Überall, wo DSL verfügbar ist! NEU: Jetzt bis zu 16.000 kBit/s! http://www.gmx.net/de/go/dsl ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Patch to partially add recursion to budgets
On Tue, Oct 10, 2006 at 08:43:35AM -0500, Gregory Alexander wrote: Alright, I got the patch updated. I like the idea of using the unset value. I was just unfarmiliar with the value structure holding code. Ok, I've committed this to trunk as 15009, with some slight tweaks. I will note that there will be minor migration problems from old versions, since values that are currently 0 will display as 0, and values that are currently unset will display as blank. This shouldn't really break anyone, but it might be a little confusing. I don't think that's a huge deal. It's not incorrect behavior, just inconvenient. On 10/3/06, Chris Shoemaker [EMAIL PROTECTED] wrote: On Mon, Oct 02, 2006 at 08:26:07PM -0500, Gregory Alexander wrote: If the error value was the only way to convey unset I could see adding a code for it, but I'm thinking it's better to handle it at the budget-level. E.g. ... and then just unset the value if an error code is passed to gnc_budget_set_account_period_value(): Not that simple, because error values are not the same as blank values. I still handle errors as errors, but also will display unset as unset. I'm not sure the api should actually store gnc_numerics with errors, so I don't know if the difference is that important, but I basically left this as you had it. User interface changes: 1.) Budget values of 0/1 are now displayed when editing as $0.00 (as appropriate) instead of being left blank. okay, good. Now, zero is a legit budget value. 2.) If the user removes all text when editing a budget value entry, it will be initialized to GNC_ERROR_UNSET. With code above, any error code will do, and will actually _unset_ the value. Agreed. That code works better. 3.) GNC_ERROR_UNSET is displayed when editing as a blank budget value. ?? It should be just blank, right? Isn't that what I said? Sorry, I didn't parse it. 4.) cleanup/debug: Other errors display as error when editing. That's a good idea. I preserved this behavior, while implementing using a NULL budget value. 5.) In the existing budget report, entries with a value of GNC_ERROR_UNSET display as . instead of a currency value. Other errors continue to display as a single $ (as appropriate.) I'd prefer that the report display and editor display were more similar, like just and error, but I might change my mind if I actually saw it. The problem is that as the tables get larger, and larger portions are blank, it gets hard to track the columns, especially since we use boxless tables. Hmm, it looks ok, so I'll leave it as .. What I haven't been able to figure out is how to have new budget entries default to GNC_ERROR_UNSET instead of 0. I think changing the default to GNC_ERROR_UNSET would be the correct behavior, although again, this is open to discussion. Well, I think the default should be unset as per above, and I think it's just automatic. Nothing's there until it's set. Yup, works great. However, this is what introduces the weird upgrade behavior. Thanks for the patch! -chris ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: French translation
Hi, Please make sure to CC gnucash-devel on all your replies.. more info inline.. Jeremie Gaucher [EMAIL PROTECTED] writes: Hi Derek, I am slightly confused about a few things. Could you just clear me up on that. I can try. First, can i just type the accents in the file or do i need tu use the codes (acute, etc...). What is the file encoding anyway? I think you should use the codes. But you can choose to use accents if you prefer.. The file should be in ISO-8859-1 format. Second, how can i verify the file? I have read the section on the wiki on .po files but i don't see how that is done since the po's discussed there are for the software, not the website. What do you mean, verify the file? You can checkout htdocs and put it into a webspace, and then you can access that webspace via a web browser. Lastly, are there other people involved in the french translation? As far as I know, nobody else is working on this. j -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: French translation
Again, PLEASE CC ALL RESPONSES TO THE LIST! We look forward to your work! Thanks -derek Quoting Jeremie Gaucher [EMAIL PROTECTED]: ok perfect got my answers i will use the accents in the file hoping they will not disappear the actual file is missing all the accented letters i was wondering if this was due to a past encoding problem i will fix that j On 10/11/06, Derek Atkins [EMAIL PROTECTED] wrote: Hi, Please make sure to CC gnucash-devel on all your replies.. more info inline.. Jeremie Gaucher [EMAIL PROTECTED] writes: Hi Derek, I am slightly confused about a few things. Could you just clear me up on that. I can try. First, can i just type the accents in the file or do i need tu use the codes (acute, etc...). What is the file encoding anyway? I think you should use the codes. But you can choose to use accents if you prefer.. The file should be in ISO-8859-1 format. Second, how can i verify the file? I have read the section on the wiki on .po files but i don't see how that is done since the po's discussed there are for the software, not the website. What do you mean, verify the file? You can checkout htdocs and put it into a webspace, and then you can access that webspace via a web browser. Lastly, are there other people involved in the french translation? As far as I know, nobody else is working on this. j -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available -- Jeremie Gaucher [EMAIL PROTECTED] 514.273.1518 514.343.6111 #1762 -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Budget report improvements
Hi Steven, Sorry for the late reply, I'm just getting back to stuff like this now. Thanks for the patch. That's pretty impressive for not having programmed in guil or lisp before - you must be a natural. I have some comments below. On Sat, Sep 09, 2006 at 11:51:58AM +0800, Steven Wilton wrote: I like the budget feature in gnucash 2.0, but there were a few features that I felt were missing in the report. Unfortunately I've not programmed in guile or lisp before, but I gave it a shot, and thought I'd send the work I'd done to this list in case anyone else thinks the features are useful. The patch does 3 things: 1 - It adds the sub-accounts in the budget columns to give a total. I did this because the actual columns already contained the total of all sub-accounts. I don't think that's generally correct behavior. What if not all sub-accounts are budgeted for? If a user wants to budget at the level of the parent account, they can enter a budget value for the parent account. This may or may not be the sum of budgeted children (if there even are any). 2 - It adds an option to make the budget and actual amounts cumulative. Interesting. I'm ambivalent about this behavior. On the one hand, I understand why it is useful to see this information. You're basically viewing actual and budgeted account _balances_. I'd like to see this information be easily available. On the other hand, this means reporting budget values that are _accumulation_ of the specified values, instead of identical to the specified values. Also, there are clearly uses when seeing the accumulated values is definitely not what you want. (But, yes, it's optional.) I'm going to think about this some more, but in any case, if we want this optional behavior, there are easier ways to get account balances - and it could probably use some assistance from the C-side of budgets. 3 - It allows the user to select a single budget period to show data for. That's clearly useful. Maybe a range of periods? 4 - It reduces the displayed accounts to income and expense only (not a core feature, but it was the only way I could see to easily remove all the asset and liability accounts from the report) You just changed the default. There's a full account selector in the options. But, I like that as default setting. 5 - It makes the default display depth 3, once again not a core feature. There are a few bugs that I'm aware of: 1 - For some reason the code that adds the sub-totals for the budget columns sometimes ends up with a blank entry. I have no idea why this is ocurring, as there is no pattern that I can see. 2 - The report takes a very long time to run. I've probably done something wrong int he code to make it run slowly. 3 - The number of periods that are displayed in the options menu is hard-coded to 12. This value should really be obtined from the number of periods in the budget. That's _really_ tricky to do right. It's the sort of thing I'd try to figure out how to avoid altogether. :) I hope the work I've done is useful. Thanks for sharing the patch. I'll see if I can commit some of these improvements some time in the future. -chris regards Steven ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
