It depends on the business-reports module which is not available to
standard-reports at build time
Interestingly this only is an issue for the makefile generator
The ninja generator works fine
- only abort configuration if gettext is older than 0.18.1 (required for string extraction from scheme files)
- otherwise always continue but disable a few other build steps depending on the gettext version
- use feature variables to more clearly convey what is enabled or disabled
Simple report to visualise lots (business and non-business) in a
spreadsheet. Each column is a unique lot, and each row is a unique
transaction. The lot balance, and the associated lot invoice are also
included.
Each transaction is analysed to render the split in the lot column,
and non-lot splits are rendered in a last column.
An account must be chosen in options, and all splits in the specified
date range will be scanned to find unique lots which are all reported
in order of first appearance.
A heavy APAR account will lead to an impractical number of columns
signifying multiple lots, therefore date-range filtering and
description filtering are both encouraged to narrow down the list of
transactions.
This starts by setting the gnucash version number in the 'project' call.
This will result in a number of variables set by cmake. The remainder
of this commit is to reuse the auto-generated
PROJECT_NAME, PROJECT_VERSION, PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR, PROJECT_VERSION_PATCH and PROJECT_VERSION_TWEAK
instead of all the various instances of PACKAGE, GNUCASH_MAJOR_VERSION
and so on.
One parameter is worth mentioning - GETTEXT_PACKAGE
GnuCash is not using this directly (any more) but it has to be set before
including gi18n-lib.h.
Other meanings of previous " -> " are now:
" -> " conversion
" .. " a range
Other fixes:
1. "File>Save" typo
2. Remove $ from sort order tooltips as it is
a. not relevant,
b. untranslatable for languages used in different regions.
On recommendation of the Translation Project's Benno Schulenberg.
Required re-annotating some comments. Also removed several comments
about leaving a line break to prevent inserting it into gnucash.pot.
That didn't actually work: they were inserted anyway.
In continuation to 67b508ba (and now including the script
po/remove-suffix.sh as well) some more strings were scriptedly
updated in all available translations.
The trailing colons have been removed in the source e.g.
here 6897f13e ff, but this created a lot of fuzzy translations.
With the po/remove-suffix.sh script, those changes are
adapted in all po files in order to make translators' life
easier.
The trailing colons have been removed in the source e.g.
here 6897f13e ff, but this created a lot of fuzzy translations.
With the po/remove-suffix.sh script, those changes are
adapted in all po files in order to make translators' life
easier.
