-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
728910: Added more documentation for Budget Balance Sheet #327
Open
datajunkie-eng
wants to merge
12
commits into
Gnucash:stable
Choose a base branch
from
datajunkie-eng:issue/728910
base: stable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 10 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
3648454
728910: Added more documentation for Budget Balance Sheet
4c21d04
Revert "728910: Added more documentation for Budget Balance Sheet"
c92d073
728910: Moved Budgeted Balance Sheet technical details to the manual
b02c254
728910: Better formatting
e645b23
728910: switched to use glosslist, more formatting
81c8a76
728910: added link from guide to manual for Budget Balance Sheet
3036732
728910: clarified Unallocated Assets
6c44090
728910: fixed xml typo
af02c26
728910: better formatting of equations, cleared up 'existing equity' …
3d1c049
728910: turned - into − and dash into ‐
e3a3c3f
Revert "728910: turned - into − and dash into ‐"
e566836
728910: turned some minuses into &minus, others into colons
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO most of the
<sect1 id="budget_reporting1">
is still descriptive and belongs into the manual. Here I would expect rules to get the best results from using the reports like e.g.At first use report x to check for input errors. Some common rules are …