This document is targeted at SQL-Ledger contributors.
If you are not a contributor and not interested in becoming one,
this page is not for you.

Providing feedback

A valuable way to contribute to SQL-Ledger is by using the
software, and then providing
feedback.

Tell the developers about your use of the
software product, your experiences, issues you encountered,
stuff like that. Your story will likely be very welcome
and you'll probably receive some enthusiastic response
from the developers (if not, don't worry, they're
probably just busy with other things).

Creating Patches

When you want to contribute a change or addition to existing source code,
you should create a patch file. This makes it easier for us to see what you
have changed.

Then submit the patch file to
contrib.
Be sure to tell us for which version the patch is for, very important!
If you don't want to use the online form send a message to
contrib (add the domain sql-ledger.org)

Translations

Translations are easy to make and all you need to know is how to use a
text editor. Just don't be intimidated by some of the funny looking stuff
in the translation file, it's nothing to be afraid of. So, here it goes.

add a new directory in the 'locale' directory. The name of the directory
is not important but to conform to standards we use a two letter
country code which is in accordance to
ISO 3166-1 standards
.

make a symlink or copy locales.pl from one of the other directories

copy one of the 'LANGUAGE' files to the new directory and enter the
longform for the language
i.e Spanish

copy one of the 'COPYRIGHT' files and enter your name and email address

run 'perl locales.pl -a' from the command line

edit the file 'all'

run 'perl locales.pl -a' again

submit the 'all', 'LANGUAGE' and 'COPYRIGHT' file so it can be
included in the distribution. Be sure to tell us for which version the
translation is for.

If you have to finetune the translations because of different meanings
in different modules do this:

edit the individual files

submit everything from the directory to us.

Templates

To set up a new set of templates copy one of the masterset
(Default-) templates. The templates are all in the templates directory.
Name the templates by language and add
industry specific or other keywords. i.e Spanish_A4-invoice.tex,
Spanish invoice, A4, LaTeX template.
Test your templates and submit to contrib.

Chart of Accounts

Chart of accounts are made up of two parts, a working chart of accounts and
an official chart of accounts (GIFI) issued by your Government.
GIFI stands for General Index for Financial Information and is a
cross-reference to provide financial
information to a Goverment. If your country does not require one it
may be used for other purposes, like consolidating accounts or providing
a translation for accounts. Some folks
think this GIFI is something specific to Canada but it really
has quite a different purpose and not only can it be used in Canada but
anywhere in the world. Like I said before, it is a cross-reference to
build reports conforming to a standard accepted by your Government.

Nameing convention for the COA follows a simple rule. If it
is industry specific anything goes, i.e. Manufacturing-chart.sql. If the
working COA is to be tied to a GIFI the Manufacturing setup becomes
Country_Manufacturing-chart.sql and Country-gifi.sql. If the GIFI is not
required but the working COA is an official one it is then named
Country-chart.sql. Notice there is no link to an industry specific COA.

set up a working COA and create all the links (use the Default-chart as
a guide. It is best to set up the Default COA alongside your own to compare
the two)

set up tax accounts and defaults

export the tables chart, tax and gifi (don't worry about financial data,
there is nothing stored in the tables)