Skip to content
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

Choosing a Register Style #319

Open
wants to merge 1 commit into
base: stable
Choose a base branch
from
Open

Conversation

flywire
Copy link
Contributor

@flywire flywire commented May 3, 2023

I'm offering this for discussion.

  1. Double-line format is not clearly explained and easily misunderstood as having something to do with splits
  2. Auto-Split Ledger style is more easily explained after Basic Ledger and Transaction Journal style, and the two-point list is removed since there are three options

I'm envisaging a discussion about Description/Notes/Memo in relation to Tags.

I'm offering this for discussion.

1. Double-line format is not clearly explained and easily misunderstood as having something to do with splits
1. Auto-Split Ledger style is more easily explained after Basic Ledger and Transaction Journal style, and the two point list removed since there are three options

It's not clear what double-line format is and how it is different from splits Current text does not clearly explain what double-line format is in terms of transactions and distingish it frm splitsis not explained very well and it is
@@ -82,42 +82,27 @@
<title>Choosing a Register Style</title>

<para>&app; offers several options for viewing your registers. The default style is <guilabel>Basic
Ledger</guilabel> mode, which displays only the summary of splits affecting the current
Ledger</guilabel>, which displays only the total of splits affecting the current
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's only a total if we are dealing with a 1-to-many split, even there it's the 1 you are seeing. Or this could be a many-to-many split, in which case it's certainly not a total, it's just a split amount. So I think it's better to simply say:
which displays only the amount of the split affecting the current ledger.
I know there is more to it with the transfer account being shown (or "split transaction" if there are more than 2 splits) but that's just more info than needed here I think.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also maybe we should say register instead of ledger. It seems the 2 are used but I see register used below as well.

@dawansv
Copy link

dawansv commented May 10, 2023

  1. Double-line

The use of "double" here certainly is not great considering the use of the same word in "double entry accounting" while it has nothing to do with it here. But I am not even sure what I would replace it with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants