Re: [GNC-dev] Transactions vs Splits
David, that's a very elaborate explanation. I'm sure there will be enough information once you are through with testing. So far our findings match. One thing I'd like to note, David Cousens wrote > Date,Transaction ID,Number,Description,Notes,Commodity/Currency,Void > Reason,Action,Memo,Full Account Name,Account Name,Amount With Sym,Amount > Num.,Reconcile,Reconcile Date,Rate/Price > 15/11/18,b60da83af9b84334aa2f5e129c23016f,,Transfer with currency > exchange,,CURRENCY::AUDAssets:Current Assets:Savings Account,Savings > Account,$100.00,100.00,n,,1.00 > ,Assets:Current Assets:Savings USD,Savings > USD,-$110.00,-110.00,n,,10/11 > > The Price is what should control the currency conversion. I find the Price and Amount information redundant, if both are sent. For example, if they don't match, which one is the relevant one? If amounts are sent in all splits, it would be better to read the amounts and calculate the price/rate on import. I assume your export is from GnuCash so it is good to learn that it exports the Price element, too. I'll adjust my export to do the same, just in case. In conclusion, the current state of import would work fine for transactions in single currency. Another issue I had with QIF import was that it was matching accounts by name, which is not what I wanted. When exporting transactions that use categories, then expenses in all currencies go to, for example, Dining. QIF import would always match Dining to Expenses:Dining, which is in EUR, in my case. So it would always create duplicate accounts after the holidays. One thing for me to check is if the CSV importer is better in that regard and will match (or at least remember manually set values) the categories to the accounts in correct currency (i.e. Expenses:Dining:AUD etc.). -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Translators struggle with commit 2020bee
hello I would prefer c) too thanks for bringing up. Regards MEchtilde Am 06.03.19 um 22:42 schrieb Frank H. Ellenberger: > Hi Alex, > > while I did some translation I had Problems to understand the meaning of > > #: gnucash/gnome-utils/dialog-options.c:858 > msgid "" > "You have selected a placeholder account, which is shown so that child " > "accounts are displayed, but is invalid. Please select another account. > (You " > "can expand the tree below the placeholder account by clicking on the > arrow " > "to the left.)" > msgstr "" > > I had to dive in the code to get the context. But we can not expect this > from normal translators. > > We could > a) Insert a translator comment with the context, > b) Insert the subject in the first sentence, or > c) Simplify it and reuse an already existing string: > > #: gnucash/import-export/import-account-matcher.c:201 > #: gnucash/import-export/import-account-matcher.c:378 > #, c-format > msgid "" > "The account %s is a placeholder account and does not allow transactions. " > "Please choose a different account." > > I would prefer c), but what is your opinion? > > Regards > Frank > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] GnuCash 3 on Linux
hi, Adrien Monteleone writes: > I’ll hazard a quick guess that everything not in the accounts tab is > non-book specific. I'm not sure I completely agree with this statement. > At the very least, the display and general tabs are not. Maybe.. > How you want figures to be displayed, which sets of figures, which periods... Different companies might have different periods; therefore, the period is tied to the book, not the person. > Content settings may be tied to the book, but formatting settings are > likely to be the most likely to be used cross-book. I can certainly > see someone wanting all of their reports looking the same. I mostly agree with this statement, but I think it depends greatly on the definitions of "content settings" and "formatting settings". Sure, window sizes, tabs v windows, color schemes -- those are clearly formatting setting and should be per-user. But "default currency", "periods", and certain parts of report configurations (e.g. accounts to include) are definitely content settings and belong with the book data. > Regards, > Adrien -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] GnuCash 3 on Linux
Derek, I don’t disagree with your assessments of what certainly *can* (and maybe even, more often than not) be specific to a book rather than a user. I was thinking more along the lines of what someone *might* most likely want to carry over across multiple books. For example, I keep books for a few entities. Everything is in USD. (except for my personal book which has a smattering of left over currency from travels and some bullion I track as currency) I have no need for other currencies, and likely never will. At the least, I’d want to start books for a new entity, should one arise, with that same default currency in my reports. (simple enough since the default book currency is also the default report currency) But I might also like to never show zero balance amounts or the corresponding accounts, and I might like to always roll up the sub account totals into the parent (since I set all parents as placeholders) and *not* show any duplicative ’total’ lines. These were the types of settings I was thinking of that someone might want to carry over across all books and maybe even all reports. (where applicable) The same might very well applied to financial periods. Separating preferences for reports is, I suspect, more useful to a multi-user environment, which GnuCash does not support, but can be useful for a single user who keeps books for multiple entities that are all in the same jurisdiction and might well even use the same CPA. (and certainly have to file the same tax forms) They might even all follow a July-June fiscal year, for example. It might be that this is too small of a use case, and the user’s setup work so light that the development burden is simply not worth the effort. (and I’m by no means advocating for more work for the team already, I’m just chiming in with my own user story to consider.) I started a project to map out report preferences as part of a revamp of the tab content and I didn’t finish it. Perhaps completing that project will offer more insight. (and very likely allow me to discover that the present situation is optimal) Regards, Adrien > On Mar 7, 2019, at 10:14 AM, Derek Atkins wrote: > > hi, > > Adrien Monteleone writes: > >> I’ll hazard a quick guess that everything not in the accounts tab is >> non-book specific. > > I'm not sure I completely agree with this statement. > >> At the very least, the display and general tabs are not. > > Maybe.. > >> How you want figures to be displayed, which sets of figures, which periods... > > Different companies might have different periods; therefore, the period > is tied to the book, not the person. > >> Content settings may be tied to the book, but formatting settings are >> likely to be the most likely to be used cross-book. I can certainly >> see someone wanting all of their reports looking the same. > > I mostly agree with this statement, but I think it depends greatly on > the definitions of "content settings" and "formatting settings". Sure, > window sizes, tabs v windows, color schemes -- those are clearly > formatting setting and should be per-user. But "default currency", > "periods", and certain parts of report configurations (e.g. accounts to > include) are definitely content settings and belong with the book data. > >> Regards, >> Adrien > > -derek ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] GnuCash 3 on Linux
Wm, I backup all user data including hidden directories on my hard disk to an NAS so no matter where it is I have it copied. I do full backups monthly with daily incrementals and usually retain them for 3 months these days. I off load the backups onto USB for offsite storage as well now that they are big enough. I'm retired so the data flow is very much reduced these days. I also do selective backups to offsite cloud locations of critical data including GnuCash. For those I backup all the data in the locations given for v3+ in the wiki Configuration Locations for GnuCash. I don't bother with the aplication config in /usr/local/etc/gnucash as I don't edit anything in it. My desktop is also synced with my laptop and my wife's laptop- not really secure as a backup as any saved changes get propagated including those that might take the system down but it has helped with some simple problems. My NAS is NFS4 based so my Linux boxes communicate pretty easliy with it (it is mounted when switched on on all computers and Samba takes care of the one Windows machine. Took a while to setup but the NAS initiates backups to itself on a schedule. Also backs up our mobile phones. When I was operating a business and in a past side job as a systems manager, I used a Towers of Hanoi (annual/quarterly/monthly/weekly/incremental) backup plan. The locations I would backup as a matter of course would be the ones labelled GNC_DATA_HOME and GNC_CONFIG_HOME ( and all files and subdirectories in those locations) in the diagrams. I haven't bothered customising the gtk-3 setup for GnuCash so I wouldn't bother with the GTK locations. David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
