AaronFiore/plaintextaccounting
1
0
Fork 0
Code Activity

small text cleanups

Browse Source
This commit is contained in:
Simon Michael
2016-08-05 19:53:22 -07:00
parent d6ef2288d4
commit b0cab1386c
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
index.html
View File

@@ -108,7 +108,7 @@ Plain Text Accounting
</div>
</div>
<div>
<h3 id="frequently-asked-questions">Frequently Asked Questions</h3>
<h3 id="frequently-asked-questions">frequently asked questions</h3>
<p><strong>Who is this for ?</strong><br />
Mostly techies and power users for now. If you need a complete GUI providing lots of guidance, you may prefer to use something else.</p>
<p><strong>Must I edit text and type cryptic commands ?</strong><br />
@@ -145,7 +145,7 @@ Accounting is modelling flows of money (or other value). Such a model aggregates
Understandable. The current plain text accounting tools provide a very generic double entry accounting system with which you can model such things, and script them. There are a number of generic GUIs available (hledger has curses and web interfaces, and there are web/curses/GTK interfaces for Ledger and beancount). But there are not yet a lot of rich task-specific GUIs. There's no reason they can't be built, though.</p>
<p><strong>Isn't a plain text format too limited for large organizations ?</strong><br />
<em>&quot;it's pretty obvious that plain-text files don't scale to a multinational, with hundreds of accountants of various types all trying to work with the same files. Even with proper use of Git I bet that would get old fast. You would instead want a real database, with a schema, and some data validation and some programs/webpages to smooth out the data entry and querying and whatnot.&quot;</em><br />
I'm not sure. Current plain text accounting tools can do some schema definition and data validation, and will do more in future. The plain text storage format is open, human-readable, future-proof (useful even without the software), scales smoothly from simple to complex needs, and taps a huge ecosystem of highly useful tooling, such as version control systems. And, despite the name, there's no reason these tools can't support other kinds of storage, such as a database. (hledger has four storage formats and is designed to accept more).</p>
I'm not sure. Current plain text accounting tools can do some schema definition and data validation, and will do more in future. The plain text storage format is open, human-readable, future-proof (useful even without the software), scales smoothly from simple to complex needs, and taps a huge ecosystem of highly useful tooling, such as version control systems. And, despite the name, there's no reason these tools can't support other kinds of storage, such as a database.</p>
<p><strong>Where can I see a comparison of hledger, Ledger, beancount, and the rest ?</strong><br />
Glad you asked! See below, and also <a href="#comparisons">comparisons</a>. hledger's FAQ discusses differences from Ledger, Beancount docs probably do too.</p>
</div>

4
index.md
View File

@@ -127,7 +127,7 @@ This simple model makes them easy to understand and rely on.
<div class="">
### Frequently Asked Questions
### frequently asked questions
**Who is this for ?**\
Mostly techies and power users for now.
@@ -206,7 +206,7 @@ There are a number of generic GUIs available (hledger has curses and web interfa
**Isn't a plain text format too limited for large organizations ?**\
*"it's pretty obvious that plain-text files don't scale to a multinational, with hundreds of accountants of various types all trying to work with the same files. Even with proper use of Git I bet that would get old fast. You would instead want a real database, with a schema, and some data validation and some programs/webpages to smooth out the data entry and querying and whatnot."*\
I'm not sure. Current plain text accounting tools can do some schema definition and data validation, and will do more in future. The plain text storage format is open, human-readable, future-proof (useful even without the software), scales smoothly from simple to complex needs, and taps a huge ecosystem of highly useful tooling, such as version control systems. And, despite the name, there's no reason these tools can't support other kinds of storage, such as a database. (hledger has four storage formats and is designed to accept more).
I'm not sure. Current plain text accounting tools can do some schema definition and data validation, and will do more in future. The plain text storage format is open, human-readable, future-proof (useful even without the software), scales smoothly from simple to complex needs, and taps a huge ecosystem of highly useful tooling, such as version control systems. And, despite the name, there's no reason these tools can't support other kinds of storage, such as a database.
**Where can I see a comparison of hledger, Ledger, beancount, and the rest ?**\
Glad you asked! See below, and also [comparisons](#comparisons). hledger's FAQ discusses differences from Ledger, Beancount docs probably do too.