Hi Sébastien, Thanks for quick reply.
> I am not sure about the way to handle this issue. The reports being > easily customisable, upstream seems to answer such requests by telling > people to create custom reports, instead of incorporating many variants > of the reports in the main package. See for example: > > http://wiki.gnucash.org/wiki/FAQ#Q:_How_do_I_change_.22Invoice.22_to_.22Tax > _Invoice.22_as_required_in_Australia.3F No, I've spent weeks trying to figure out how to customise those reports so I'm fairly confident it's not possible to the extent I need to comply with Australian requirements. By the way this advice dated years ago. Read the gory details below. > > Concerning the patches that you provided, I don't intend to incorporate > the invoice-au.* ones, since I think it does not make sense to have a > report per country. Sorry if I wasn't clear enough - I never meant to incorporate invoice-au if you accept the patch. (Nevertheless you may consider shipping it as examples) I included invoice-au for evaluation of how customisable the standard taxinvoice will be after patching (with the exception of default values). > > The patch to taxinvoice.* seems a better solution, but as such I cannot > incorporate it. First, it does too many things at a time: it indeed adds > new customization options, but it also contains unrelated cosmetic > changes. Moreover, it contains commented out code, and some values are > by default set to Australian settings, which is not convenient for a > general-purpose report. Well, those things are connected together. Patch introduces new options menus and use those options to make the template more flexible. This include the logic to change number of columns according to settings etc. Patch do not set new defaults. (AU defaults only provided by invoice-au which I included for reference). Even if default look is slightly changed we can always document it so our users won't complain if the template provided become more flexible. In some cases cosmetic changes may be considered necessary, so we might need to discuss specifically by change. I invite you to try new invoice by placing invoice-au files in your ~/.gnucash so you will see the changes yourself. Patch is actually not as intrusive as you might think. If you have concerns regarding a particular change - let's discuss so I could alter the patch to your satisfaction. > Don't hesitate to follow-up if you have any idea or comments on the > above. Thank you, I'm trying. :) > > Also, I am lowering the severity of this bug to wishlist since it is > more an enhancement request than a bug. Sorry, but I respectfully disagree. It is a fairly serious problem for Australian users. Currently Gnucash is not ready for small business use in Australia. Without this (or similar) change we will have no Australian users and given the issue is there for years I don't expect upstream to do this work for us. Apparently there was a lack of contributions but I'm trying to address exactly this. Sadly upstream is busy with something else - for example the FAQ entry you mentioned actually advice to manually patch files provided by the package!!! This is not only intolerable but also bring implications which make the real usage impossible for mere mortals. Not to mention the necessity for root access plus understanding that package update will overwrite the changes etc. I don't need to tell you how difficult may be the altering of Scheme templates even for IT professional so we can't expect this from our users. Please understand that at the present moment invoicing with Gnucash is impaired due to lack of customisation options and the mentioned FAQ explains how to change the older templates which doesn't help much. Apparently there is a transition towards new templating system (eguile) which is easier to customise but still do not have the expected flexibility especially regarding printable invoices, Australian invoices, invoices in foreign currency etc. I'm addressing the issues in the new template. My patch is not perfect but it is a step forward in the right direction. I invite you to bring your ideas what you think would be the best to do. I think there may be three options: * The patch may be considered acceptable as is if we agree. * We discuss the acceptable changes so I could alter the patch to make it suitable for inclusion. * I prepare README-AU.txt describing the use of provided 'invoice-au' files so we can deliver a ready to use solution for Australian users. At the moment there is nothing in the installable package to help Australian users with Gnucash. I'm sure together we can change this. Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
