mirror of
https://github.com/Gnucash/gnucash.git
synced 2025-02-25 18:55:30 -06:00
*** empty log message ***
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2054 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Dave Peticolas
parent
a9be6f13cd
commit
1da4e807a7
19
ChangeLog
19
ChangeLog
@ -1,5 +1,24 @@
|
||||
2000-03-04 Dave Peticolas <peticola@cs.ucdavis.edu>
|
||||
|
||||
* src/guile/gnucash.c (main): load the locale from the environment
|
||||
with setlocale. This is needed so that guile can find the locale.
|
||||
|
||||
* Docs/: reorganized the Docs directory. Then english language
|
||||
stuff moved to the "C" directory. The french stuff goes under
|
||||
"fr". The "En" and "Fr" directories are gone. The standard for
|
||||
country codes uses lower-cases letters, so we should stick to
|
||||
that. The graphics files go under "pix" directories under their
|
||||
respective language directories.
|
||||
|
||||
* src/scm/path.scm: create documentation search paths based on the
|
||||
current locale. The default "C" locale is always searched last.
|
||||
|
||||
* src/reports/File.c (gncFindFile): take out dead code.
|
||||
|
||||
2000-03-03 Dave Peticolas <peticola@cs.ucdavis.edu>
|
||||
|
||||
* src/register/pricecell.c (PriceMV): accept thousands separators.
|
||||
|
||||
* src/scm/c-interface.scm: new functionality for registering
|
||||
translatable strings and saving them to a file in a suitable
|
||||
format for po creation. This touched a bunch of other .scm
|
||||
|
||||
41
Docs/C/bofa-mym.html
Normal file
41
Docs/C/bofa-mym.html
Normal file
@ -0,0 +1,41 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>Importing MYM Files</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Managing Your Money --> GNUCash</h1>
|
||||
|
||||
I have finally put the Perl script that allowed me to use GNUCash
|
||||
up on a web site. I had a couple years of data in Managing Your
|
||||
Money 2.x that I didn't want to reenter. The script will output a
|
||||
single QIF file with all transactions, accounts, and categories.
|
||||
(Currently only non-investment transactions are handled.) The QIF
|
||||
file can be imported to xacc-1.0.18 if a small patch is applied to
|
||||
QIFIO.c. The site is
|
||||
|
||||
<p> <a href="http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html">
|
||||
MyMdump</a></p>
|
||||
|
||||
<h1>Duplicate Transactions</h1>
|
||||
|
||||
I also have a script that I use to remove duplicate transactions at
|
||||
the QIF level. I use this script because Xacc is very strict about
|
||||
duplicates (which is good) and because editing imported
|
||||
transactions will cause a re-import of the same transactions to
|
||||
produce duplicates. (I download the same month's transactions from
|
||||
my bank several times each month, so each downloaded QIF
|
||||
file--after the first--contains transactions I have already
|
||||
imported. I don't want to rely on the bank sending me the
|
||||
transactions in the same order or with the same formatting.) The
|
||||
site is
|
||||
|
||||
<p> <a href="http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html">
|
||||
qifuniq</a></p>
|
||||
|
||||
<p> I hope others find these scripts useful.</p>
|
||||
|
||||
<p>Ken Yamaguchi October 1998</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 9.6 KiB After Width: | Height: | Size: 9.6 KiB |
|
Before Width: | Height: | Size: 7.1 KiB After Width: | Height: | Size: 7.1 KiB |
|
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 7.6 KiB |
|
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 7.4 KiB |
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 7.4 KiB |
|
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 7.6 KiB |
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.5 KiB |
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 66 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 65 KiB After Width: | Height: | Size: 65 KiB |
|
Before Width: | Height: | Size: 9.7 KiB After Width: | Height: | Size: 9.7 KiB |
|
Before Width: | Height: | Size: 7.0 KiB After Width: | Height: | Size: 7.0 KiB |
|
Before Width: | Height: | Size: 9.1 KiB After Width: | Height: | Size: 9.1 KiB |
|
Before Width: | Height: | Size: 9.8 KiB After Width: | Height: | Size: 9.8 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 5.5 KiB After Width: | Height: | Size: 5.5 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
1558
Docs/C/projects.html
Normal file
1558
Docs/C/projects.html
Normal file
File diff suppressed because it is too large
Load Diff
38
Docs/fr/bofa-mym.html
Normal file
38
Docs/fr/bofa-mym.html
Normal file
@ -0,0 +1,38 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Importing MYM Files</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
|
||||
<H1>
|
||||
Managing Your Money --> GNUCash</H1>
|
||||
J'ai finallement produit le script Perl qui me permet d'utiliser GNUCash
|
||||
jusque sur un site web. J'ai deux années de données dans
|
||||
Managing Your Money 2.x que je ne veux pas réentrer. Le script sortira
|
||||
un simple fichier QIF avec toutes les transactions, comptes, et catégories.
|
||||
(Actuellement seulement les transactions de non-investissement sont traitées.)
|
||||
Le fichier QIF peut être importé vers xacc-1.0.18 si un petit
|
||||
patch est appliqué à QIFIO.c. Le site est:
|
||||
<P>http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html
|
||||
<H1>
|
||||
Transactions dupliquées</H1>
|
||||
J'ai aussi un script que j'utilise pour enlever les transactions dupliquées
|
||||
au niveau du QIF. J'utilise ce script parce que Xacc est très strict
|
||||
à propos des duplications (ce qui est très bon) et parce
|
||||
qu'éditer des transactions importées causera une ré-importation
|
||||
des mêmes transactions qui produiront des doubles. (Je télécharge
|
||||
les transactions du même mois depuis ma banque plusieurs fois
|
||||
chaque mois, alors chaque fichier QIF téléchargé --après
|
||||
le premier--contient des transactions que j'ai déjà
|
||||
importé. Je ne veux pas compter sur ma banque pour m'envoyer les
|
||||
transactions dans le même ordre ou avec le même formatage.)
|
||||
Le site est
|
||||
<P>http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html
|
||||
<P>J'espère que les autres trouveront ces scripts facile à
|
||||
utiliser.
|
||||
<P>Ken Yamaguchi Octobre 1998
|
||||
</BODY>
|
||||
</HTML>
|
||||
BIN
Docs/fr/pix/contract.gif
Normal file
BIN
Docs/fr/pix/contract.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.6 KiB |
BIN
Docs/fr/pix/expand.gif
Normal file
BIN
Docs/fr/pix/expand.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.0 KiB |
BIN
Docs/fr/pix/foliowin-single.gif
Normal file
BIN
Docs/fr/pix/foliowin-single.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
Docs/fr/pix/foliowin.gif
Normal file
BIN
Docs/fr/pix/foliowin.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
Docs/fr/pix/newaccwin-code.gif
Normal file
BIN
Docs/fr/pix/newaccwin-code.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.1 KiB |
BIN
Docs/fr/pix/newaccwin-trade.gif
Normal file
BIN
Docs/fr/pix/newaccwin-trade.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.3 KiB |
BIN
Docs/fr/pix/newaccwin.gif
Normal file
BIN
Docs/fr/pix/newaccwin.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.1 KiB |
BIN
Docs/fr/pix/recnwin.gif
Normal file
BIN
Docs/fr/pix/recnwin.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
BIN
Docs/fr/pix/regwin-double.gif
Normal file
BIN
Docs/fr/pix/regwin-double.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
Docs/fr/pix/regwin-multi.gif
Normal file
BIN
Docs/fr/pix/regwin-multi.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
Docs/fr/pix/regwin-single.gif
Normal file
BIN
Docs/fr/pix/regwin-single.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
Docs/fr/pix/regwin.gif
Normal file
BIN
Docs/fr/pix/regwin.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.7 KiB |
BIN
Docs/fr/pix/report-baln.gif
Normal file
BIN
Docs/fr/pix/report-baln.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.0 KiB |
BIN
Docs/fr/pix/report-folio.gif
Normal file
BIN
Docs/fr/pix/report-folio.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.1 KiB |
BIN
Docs/fr/pix/ticker-a.gif
Normal file
BIN
Docs/fr/pix/ticker-a.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.5 KiB |
BIN
Docs/fr/pix/ticker-b.gif
Normal file
BIN
Docs/fr/pix/ticker-b.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
817
Docs/fr/projects.html
Normal file
817
Docs/fr/projects.html
Normal file
@ -0,0 +1,817 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>GnuCash Project Goals</title>
|
||||
<meta name="description" content="The Linux GnuCash (X-Accountant)
|
||||
project aims at creating a world-class personal finance package.
|
||||
Goals include ease-of use, double entry, OFX support, charts,
|
||||
and reports, and multi-user support.">
|
||||
|
||||
<meta name="keywords" content="linux, ofx, accounting, finance,
|
||||
financial, ledger, double entry, GPL, gnu, corba, gnome, Qt, Motif">
|
||||
</head>
|
||||
|
||||
<body bgcolor="#eeeeee">
|
||||
<h1>GnuCash Project Goals</h1>
|
||||
<a href="http://gnucash.org">GnuCash</a>
|
||||
(previously known as X-Accountant) is a personal finance
|
||||
accounting application. The project goals are to create a world-class
|
||||
GPL'ed Open Source personal financial application for GNU/Linux and other
|
||||
Unix's. The project is the result of a merger
|
||||
of the GnoMoney project with X-Accountant development. There are currently
|
||||
two versions: xacc-1.0.18, and gnucash-1.1.x. Version <tt>xacc-1.0.18</tt>
|
||||
is written in Motif, and is considered to be stable/production quality.
|
||||
You can read more about X-Accountant at its home page
|
||||
<a href="http://www.cs.hmc.edu/~rclark/xacc/index.html">
|
||||
http://www.cs.hmc.edu/~rclark/xacc/index.html</a>. Versions
|
||||
numbered as <tt>gnucash-1.1.x</tt> are the current development
|
||||
versions, and are unstable. GnuCash is in active development;
|
||||
this page is an effort to summarize the project goals and status.
|
||||
|
||||
<p>
|
||||
The <a href="http://gnucash.org/">GnuCash</a> pages
|
||||
provide overview & introductory material about GnuCash, and in
|
||||
general present a glossier, more accessilbe format. This page is
|
||||
aimed at developers, not users.
|
||||
<p>
|
||||
We believe that a GNU GPL project should provide goals and motivations
|
||||
at both the large and the small scales, in order to focus and motivate
|
||||
the developers. Over-arching and grand goals are difficult to grasp
|
||||
and carry out; yet their lack serves only to dissuade the grand
|
||||
thinkers. A list of detailed goals may be mind-numbing to the casual
|
||||
reader; yet, without them, the roll-up-your-sleeves-and-do-it
|
||||
coder cannot know where to begin. Detailed goals lend a concreteness
|
||||
to the discussion: they can be architected, designed and coded at any time
|
||||
by coders of any ability. Thus, we present a list of goals, large and
|
||||
small, with the hope that the small goals will fall quickly, and the
|
||||
large ones shall turn into a multitude of small ones.
|
||||
<p>
|
||||
|
||||
<h2>News</h2>
|
||||
<dl>
|
||||
<dt><b>September 1998</b>
|
||||
<dd>Version 1.1.18 is begining to get stable; most things work the way they're
|
||||
supposed to. New features include variety of ways of viewing an account,
|
||||
a simple query engine, and support for multiple currencies.
|
||||
<p>
|
||||
|
||||
<dt><b>April 1998</b>
|
||||
<dd>The domain "gnucash.org" has been registered; web site is up.
|
||||
<p>
|
||||
|
||||
<dt><b>10 April 1998</b>
|
||||
<dd>Work on OFX support, and user-prefrences, has begun in earnest.
|
||||
<p>
|
||||
|
||||
<dt><b>10 March 1998</b>
|
||||
<dd>Source is available with CVS. See instructions at bottom.
|
||||
<p>
|
||||
|
||||
<dt><b>4 March 1998</b>
|
||||
<dd>The folks involved with
|
||||
<a href="http://www.dnaco.net/~bcooper/watermark/index.html">
|
||||
WaterMark</a>,
|
||||
<a href="http://gnomoney.ml.org/gnomoney/index.hts">GnoMoney</a>,
|
||||
and
|
||||
<a href="http://www.cs.hmc.edu/~rclark/xacc">
|
||||
X-Accountant</a>
|
||||
have tentatively agreed to join forces to work on a unified
|
||||
personal-finance project. Subscribe to the xacc mailing list
|
||||
for more info.
|
||||
<p>
|
||||
</dl>
|
||||
|
||||
<h2>Meta-Architecture Goals</h2>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Create and maintain a clean separation between the data structures and the
|
||||
GUI that manipulates them, along the lines of a <b>Model-View-Controller</b>
|
||||
paradigm. Lists of accounts and the transactions in
|
||||
them can be thought of as a representation of financial data,
|
||||
a <b>Model</b>. The GUI that adds, modifies and deletes these should
|
||||
be thought of as a manipulator of the data, a <b>Controller</b>.
|
||||
The current Motif GUI is just
|
||||
one possible manipulator of the data; other GUI's,
|
||||
some simple, some complex, some possibly based on other graphical
|
||||
toolkits (Qt, gtk, emacs) should be possible.
|
||||
The <b>View</b> of the data is a modern way of saying "report".
|
||||
One typically does not view, or want to view all of the data,
|
||||
but only a subset: say, only the transactions for the month of May,
|
||||
or only the account totals for certain accounts. The concept of "View"
|
||||
in fact consists of two very separate ideas: the <b>Query Engine</b>
|
||||
and the <b>Report Generator</b>. The Query Engine is used to extract
|
||||
a list of transactions from the Model database, based on a set of dates,
|
||||
a set of types, or other criteria. This list is then typically
|
||||
edited by the controller, or possibly printed. The Report Generator
|
||||
is used to create summary reports about average account balances,
|
||||
or profit&loss statements, or cash-flow statements, or may be graphed
|
||||
as pie charts of asset allocations, or graphs asset value over time.
|
||||
<p>
|
||||
|
||||
<li>
|
||||
Create a mechanism for obtaining data from multiple financial sources.
|
||||
Currently, GnuCash stores data in its own file format; it can also
|
||||
import Quicken(TM) QIF files. However, other sources & sinks of data
|
||||
might be stock-quote web sites, on-line banking interfaces such as OFX,
|
||||
access to SQL databases, such as those of Linux-Kontor, or CORBA interfaces,
|
||||
such as the GL Ledger submission to the OMG. It should be possible to have
|
||||
any of these at as data sources, and with the appropriate security mechanisms,
|
||||
it should also be possible for a user of GnuCash to manipulate the data
|
||||
at the other end.
|
||||
<p>
|
||||
In particular, with respect to OFX & online banking, one should be able to think
|
||||
of GnuCash as a very special browser, capable of browsing financial web sites.
|
||||
Instead of talking HTML/HTTP, it would talk OFX or Gold with the remote
|
||||
server. Besides just statically viewing ones bank account, it should also
|
||||
allow bill payment and other account manipulation.
|
||||
<p>
|
||||
|
||||
<li>
|
||||
Create both a personal-financial accounting system, as well as a
|
||||
business accounting framework. Although these two goals may seem at
|
||||
odds with each other, there is no reason why they could not share
|
||||
a considerable amount of framework. The goals of a personal finance
|
||||
system is a system that is easy to use, has a simple yet powerful menu
|
||||
system, provides graphs, charts, and interfaces to on-line banking and
|
||||
stock systems. The goals of a business system is multi-user
|
||||
capabilities built on an SQL database and/or CORBA objects for
|
||||
multi-user use, with support for inventory control, shipping &
|
||||
receiving, billing, accounts payable & receivable. A pie-in-the-sky
|
||||
system might even include interfaces to on-line shopping carts,
|
||||
credit-card clearing interfaces, or even a subset of SAP R/3 (TM)
|
||||
functions. Note that all of these systems require at their base
|
||||
both a strong model of a "financial transaction", as well as
|
||||
a ledger window, and a report generation mechanism. The tools
|
||||
created to allow one should be portable enough to be deployed in the
|
||||
other application as well.
|
||||
<p>
|
||||
</ul>
|
||||
|
||||
|
||||
<h2>Concrete Architectural and Development Goals</h2>
|
||||
The following is a list of the larger, more abstract, and more difficult
|
||||
architectural goals.
|
||||
|
||||
<dl>
|
||||
<dt><b>Graphs, Reports</b>
|
||||
<dd>Add the whole host of reports, including Net Worth statements,
|
||||
Balance Sheets, and Profit & Loss statements. These should be
|
||||
printable: it might be best to create them as ordinary HTML pages,
|
||||
and use the printing abilities of the browser. In an ideal
|
||||
situation, the user should be able to create custom reports.
|
||||
<p>
|
||||
Other output format possibilities include SGML and XML. In the
|
||||
long run, these are preferable to HTML, since DSSSL and
|
||||
<a href="http://www.jclark.com/jade/"> Jade (James DSSSL Engine</a>
|
||||
can be used to convert to RTF, Postscript, etc. XML is the wave
|
||||
of the future.
|
||||
<p>
|
||||
The Report Generator should be a "dockable" subsystem of the
|
||||
whole. Thus, it should be possible to run the report generator
|
||||
in a stand-alone, read-only fashion without having to start up the main
|
||||
application.
|
||||
<p>
|
||||
Graphs, charts, etc. too ...
|
||||
<p>
|
||||
One hard part of reporting is designing a configurable interface,
|
||||
so that people can build custom reports.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Simple HTML output is implemented. GnuCash will even act as a one-shot
|
||||
web server.
|
||||
<li>Reports for profit & loss, balance sheet, & portfolio valuation
|
||||
implemented as html-embedded perl scripts.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Web Site Maintenance & Marketing</b>
|
||||
<dd>Put together an active, relevent web site. Mailing list archives.
|
||||
Screen shots. Announces on c.o.l.a, freshmeat. Put minor news items,
|
||||
etc. on web site news. Bug tracker. Maintain repository of
|
||||
co-requisite tools & packages.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Jeremy Collins
|
||||
<a href="mailto:jcollins@gnucash.org">jcollins@gnucash.org</a>
|
||||
has put together the web site and is the current maintainer.
|
||||
Almost everything on the list above is now available. Thanks Jeremy!
|
||||
<li>Dec 1998 -- Yannick LE NY has provided French tranlations of the
|
||||
lead web pages.
|
||||
<li>Nov 1998 -- Many thanks to Patrick Condron
|
||||
<pcondon@rackspace.com>
|
||||
and <b><tt>rackspace.com</tt></b> forgh-bandwidth hosting of the web
|
||||
site.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>OFX support</b>
|
||||
<dd>Provide the SGML DTD parsers to handle the OFX reports that many
|
||||
banking institutions are providing, or will soon be providing, to
|
||||
retail customers. See below for OFX references. OFX is an open spec
|
||||
from Microsoft, Intuit, & Checkfree, and will be supported by Integrion.
|
||||
The OFX DTD's are included in the 1.1 distributions. See
|
||||
<a href="http://www.ofx.net">OFX HomePage</a> for details.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Work on an OFX DTD parser has begun. headers generated
|
||||
correctly. Constrcutors generated almost correctly.
|
||||
Parser work done by Linas.
|
||||
<li>Simple scripts have been run against real-live OFX servers.
|
||||
Ueli Rutishauser <urutishauser@bigfoot.com>
|
||||
has been able to do e*trade transactions to a real account.
|
||||
<li> how it will intereact with the GUI is a wide-open question.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Budgeting</b>
|
||||
<dd>Ability to handle budgeted future transactions.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>A design doc has been submitted by Bob Drzyzgula.
|
||||
Take a look at <tt>./src/budget.txt</tt> in the source directory.
|
||||
<p>
|
||||
|
||||
<dt><b>Ledger Widget</b>
|
||||
<dd>Create a more powerful ledger widget. Currently, the X-Accountant
|
||||
uses the powerful XbaeMatrix widget to display the ledger windows.
|
||||
This is a good widget for displaying and maintaining tables.
|
||||
However, it could, and should, be further customized to handle
|
||||
the needs of accounting use. Thus, it should be possible to
|
||||
designate cells as being date cells, and provide completely
|
||||
automated handling of date entry within these cells. Similarly,
|
||||
it should be possible to designate monetary cells which can handle
|
||||
input. General text fields, for the description and the memo,
|
||||
should be endowed with quick-fill abilities, allowing completion
|
||||
by comparing the current types text to previous entries. Finally,
|
||||
there should be pull-down (combo-box) cells that can contain
|
||||
pull-down item lists. Each of these functions are currently
|
||||
implemented in X-Accountant; however, there is no separation between
|
||||
these features and the specific accounting functions. A clean
|
||||
separation would make the design and implementation of new ledger
|
||||
windows much simpler and easier.
|
||||
<p>
|
||||
<b>Current Status:</b> the latest beta-development releases (version
|
||||
1.1.x) contain such an object.
|
||||
<ul>
|
||||
<li>Currently Motif-based
|
||||
<li>GTK port mostly work, but is hung up on the inadequacies of
|
||||
underlying table widget.
|
||||
<li>No Qt port yet of the register.
|
||||
<li>the simple single-account ledgers (incl. stock ledgers) seem
|
||||
to be working correctly, but no heavy testing yet.
|
||||
<li>The multiple-account ledger is very broken.
|
||||
<li>The multi-split ledger seems to work. One can display
|
||||
one line per transaction, two lines per transaction, one line
|
||||
per split, or a dynamic-expansion version of these.
|
||||
<li>GTK version published, thanks to Rob Browning.
|
||||
(other comments above are for motif version).
|
||||
<li>No curses or emacs version yet.
|
||||
<li>Taxes: For handling e.g. new zealand GST tax (12.5%) or british VAT,
|
||||
it would be enough to add a checkbox to say y/n, add tax ...
|
||||
(of course other schemes would be more sophisticated.)
|
||||
<li>Linas Vepstas <linas@linas.org> is handling the "GUI-independent"
|
||||
parts of the register, as well as the Motif code.
|
||||
<li>Ted Lemon <mellon@hoffman.vix.com>
|
||||
is creating/fixing/extending
|
||||
the underlying gtk widget to have the features that GnuCash needs.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Engine, Financial Objects</b>
|
||||
<dd>The current system makes a distinction between the data (account,
|
||||
transaction) and they GUI that displays it. The data is embeded
|
||||
within and controlled by the "Engine", which is a set of routines
|
||||
to access accounts, transactions, etc. The flexibility and features
|
||||
of the engine can be improved, and in particular, the sophistication of
|
||||
the query generator, and the level of multiple-currency support.
|
||||
But possibly the most important task is to review the paradigm
|
||||
and adjust it to bring it in line with a transaction-processing
|
||||
model.
|
||||
<p>
|
||||
<b>Current Status:</b>
|
||||
<ul>
|
||||
<li>The basic engine has been detangled from
|
||||
the GUI elements, as of version gnucash-1.1.4.
|
||||
<li>Binary file I/O mostly detangled into a separate module.
|
||||
<li>Crude transaction logging in place; should be suitable
|
||||
for error/crash recovery but has not been tried by fire.
|
||||
<li>Backup files automatically created & timestamped.
|
||||
<li>BeginEdit()/RoolbackEdit()/CommitEdit() routines mostly in place,
|
||||
These "Transaction processing constructs"
|
||||
should simplify creation of an SQL back end.
|
||||
<li>Multiple currency support is present but shaky/untested.
|
||||
<li>Query engine is minimal/sparse in capabilities.
|
||||
<li>Linas <linas@linas.org> is maintaining the engine code.
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
||||
<dt><b>Extension Language Support</b>
|
||||
<dd>Currently, the application is wired together entirely with
|
||||
C code. A goal of the project is to replace this wiring with
|
||||
a highly-configurable extension-language interface.
|
||||
<p>
|
||||
The overall architecture is envisioned to be as so:
|
||||
All code, including the transaction engine, the file I/O routines,
|
||||
the menus, and the ledger, will be abstracted into
|
||||
compact modules that can function independently of each other.
|
||||
At the highest level, there will be a infrastructure with
|
||||
extension language interfaces that will "wire together" the
|
||||
various modules.
|
||||
<p>
|
||||
Such "wiring together" will consist of a dispatch infrastructure
|
||||
that will allow arbitrary menu entries to be hooked to arbitrary
|
||||
modules. The configuration for menu entries, and thier associated
|
||||
callbacks, will be specified in an ext-lang configuration file.
|
||||
At the final stages, it is hoped that new modules can be imported
|
||||
without requiring that the application itself be recompiled & relinked.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Work has begun.
|
||||
<li>The transaction engine interfaces are avaialable via
|
||||
<a href="http://starship.skyport.net/crew/beazley/swig.html">
|
||||
SWIG</a>.
|
||||
<li>The main loop is controlled by the Guile scheme interpreter.
|
||||
<li>Rob Browning is the reigning expert.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Multi-user Support</b>
|
||||
<dd>Multi-user support should be added with either an SQL backend
|
||||
to the engine, and/or through CORBA interfaces to the engine.
|
||||
Project Kontor and also FreeMoney is working on SQL schemas;
|
||||
Kontor is also working on Java RMI/CORBA interfaces.
|
||||
<p>
|
||||
The following industrial-strength features are still needed:
|
||||
<ul>
|
||||
<li>transaction-oriented queuing of updates
|
||||
<li>event subscription channel for updates
|
||||
<li>user authentication
|
||||
<li>user authorization
|
||||
<li>non-repudiability
|
||||
<li>encryption of network connections
|
||||
</ul>
|
||||
<p>
|
||||
<ul>
|
||||
<li>Stephan Lichtenauer <s_lichtenauer@muenchen.org>
|
||||
is working on corba interfaces.
|
||||
<li>"Alexander L. Belikoff" <abel@bfr.co.il> may start work on corba
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
||||
<dt><b>SQL I/O</b>
|
||||
<dd>A module is necessary to allow data to be fetched from an SQL
|
||||
database, and for that database to be updated. Some thoughts:
|
||||
SQL databases do not need to be locked during editing: instead,
|
||||
an optimistic approach, similar to that employed by CVS (concurrent
|
||||
version system, a mechanism for storing versions of source code)
|
||||
could be used: if the edits conflict with changes made by others,
|
||||
the edit could be rejected en-masse, allowing the user to merge and
|
||||
correct their changes. This is a very important note: updating
|
||||
SQL does NOT require locks to be held for long periods of time!
|
||||
<p>
|
||||
|
||||
<dt><b>Network Banking</b>
|
||||
<dd>Add ability to do on-line banking, billpay, etc.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Can obtain stock quotes from Yahoo (NYSE), Fidelity Investments,
|
||||
T.Rowe Price, and do automated update of GnuCash data files
|
||||
(with the gnc-price perl script). Need to add more data sources.
|
||||
See src/quotes/Quote.pm and src/quotes/gnc-price for details.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
</dl>
|
||||
|
||||
<h2>Incremental Development Goals</h2>
|
||||
The following is a list of goals and "bug fixes" that should be solved
|
||||
immediately, independent of the major goals.
|
||||
|
||||
<dl>
|
||||
<dt><b>User Interface Ports</b>
|
||||
<dd>Port the package as a whole to gtk/gnome, Qt, Emacs.
|
||||
<p>
|
||||
<b>Status:</b>
|
||||
<ul>
|
||||
<li>Currently, the most functional interface is the Motif interface.
|
||||
This primarily due to historical reasons, i.e. the Motif interface was
|
||||
inherited from X-Accountant. Maintained by Linas Vepstas.
|
||||
<li>The gnome/gtk version is second in line. It frequently doesn't
|
||||
compile, although sometimes it runs. The #1 showstopper for this
|
||||
port is the lack of a suitable table widget that can be used
|
||||
as a Ledger. The ledger currently uses the gtk_clist widget,
|
||||
but this isn't really powerful enough. Volunteers?
|
||||
<p>
|
||||
Most of the work has been done by
|
||||
Jeremy Collins, with considerable help from Rob Browning.
|
||||
Daniel R Risacher <magnus@alum.mit.edu> keeps threatening to
|
||||
do something ...
|
||||
<li>First draft of Qt code submitted by
|
||||
Dirk Schoenberger <schoenberger@signsoft.com>.
|
||||
<li>Jim Pick <jimpick@jimpick.com> may be working on an emacs version...
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
||||
<dt><b>Internationalization</b>
|
||||
<dd>All menus, markup and help-text should be internationalized,
|
||||
so that GnuCash could be usable in any country. This
|
||||
would include the printing of currency values in the local
|
||||
country conventions.
|
||||
<p>
|
||||
<b>Current status:</b>
|
||||
<ul>
|
||||
<li>Most English-language messages have been
|
||||
<tt>#defined</tt> and moved to a single header file
|
||||
<tt>include/messages_en.h</tt>
|
||||
<li>Plan to use gnu <tt>gettext()</tt> for the message catalogues.
|
||||
<li>Looking for routines that can parse and print
|
||||
monetary values in different formats, as well as date/time
|
||||
parsing/printing routines. (gnucash contains such parsing
|
||||
routines, but they're not very powerful or i18n'ed.)
|
||||
<li>Henning Spruth has translated the README into German.
|
||||
<li>Yannick Le Ny <y-le-ny@ifrance.com> traduction en francais
|
||||
et <tt>include/messages_fr.h</tt>
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Icons, Glitz, Icons, Glitz</b>
|
||||
<dd>A set of pretty icons and button pixmaps should be created for
|
||||
minimized windows, and for the various buttons. A user-configurable
|
||||
button-bar would be nice too. This should probably be coupled with
|
||||
the creation of an X resource file, which does not currently exist.
|
||||
<p>
|
||||
|
||||
<dt><b>User Preferences</b>
|
||||
<dd>Create menu system & file format for manipulating user
|
||||
preferences. Preferences include things like showing/not
|
||||
showing categories, forcing double-entry, etc.
|
||||
<p>
|
||||
<b>Current status:</b>
|
||||
<ul>
|
||||
<li>Rob Browning has put together a basic infrastructure
|
||||
that unifies command-line flags with sceme-based config files.
|
||||
<li>Rob also is auto-generating the GUI ...
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Categories</b>
|
||||
<dd>Provide a default list of "Categories" (Income/Expense Accounts).
|
||||
These are categories such as "Automobile Expense", "Bank Interest
|
||||
Income", and "Employment Income". The user should be able to
|
||||
select a default set of accounts, and have those be created.
|
||||
To actually implement this, it might be best to simple create
|
||||
a file with these in them, and load that file. A mechanism should
|
||||
be provided to allow the user to weed-out the unwanted accounts
|
||||
without hampering their ability to use them at a later date, if
|
||||
desired.
|
||||
<p>
|
||||
<b>Current status:</b>
|
||||
<ul>
|
||||
<li>There exists the ability to merge
|
||||
accounts from multiple files, and the ability to hide/show
|
||||
Income/Expense Account types.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Recurring Transactions</b>
|
||||
<dd>Add support for automatic, recurring transactions, e.g.
|
||||
mortgage payments, fixed-interest bonds, bank accounts, etc.
|
||||
Note that the design for this could be very different, depending on
|
||||
whether the multi-user functions are available or not.
|
||||
Note also, maybe the engine needs to support two dates per
|
||||
transaction: expected, and actual ??
|
||||
<b>Current status:</b>
|
||||
<ul>
|
||||
<li>April 1998 -- Design Doc contributed by Bob Drzyzgula. See
|
||||
<tt>src/budget.txt</tt>
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>Navigation</b>
|
||||
<dd>Menu navigation using the keyboard should be possible.
|
||||
Although menu mnomenics exist, they seem to be broken.
|
||||
Similarly, tab-key navigation should be possible. Currently,
|
||||
it is possible to use the tab key to navigate from field to
|
||||
field in the register window, to user arrow keys to navigate menus,
|
||||
and quick-fill to automatically complete fields. However,
|
||||
it is not possible to tab over to the "Commit" button. It should be.
|
||||
<p>
|
||||
|
||||
<dt><b>Folder Tabs</b>
|
||||
<dd>Currently, Income/Expense accounts can be shown or hidden by
|
||||
selecting from a menu. It would be nice to be able to examine
|
||||
different account types (Asset, Liability, Income, Expense,
|
||||
Payables, Receivables, Inventory) by selecting a tab folder.
|
||||
<p>
|
||||
|
||||
<dt><b>Fly-Over Help</b>
|
||||
<dd>When the user pauses the mouse over a button, "fly-over" pop-up
|
||||
help windows should appear.
|
||||
<p>
|
||||
|
||||
<dt><b>Simplified Stock Ledger</b>
|
||||
<dd>Stocks and Mutual funds are handled by placing them each in their
|
||||
own account. Each account can be viewed individually. If all of
|
||||
the stock accounts are children of a master trading account, then
|
||||
the trading account can be viewed and modified in a General Ledger
|
||||
window. The current stock general ledger window is a bit obtuse,
|
||||
and difficult to understand and use. A simplified but still
|
||||
powerful ledger window is desperately needed.
|
||||
<p>
|
||||
|
||||
<dt><b>Forced Double-Entry</b>
|
||||
<dd>The system supports double-entry: every transaction
|
||||
indicates a pair of accounts: one is debited, and one is credited.
|
||||
Double-entry is a powerful way of ensuring the integrity of
|
||||
of the financial data. Currently, while double-entry is supported,
|
||||
its use is not forced: the user can create dangling transactions,
|
||||
where only one account is indicated. Although this is acceptable
|
||||
for home use (even desirable, since it allows the casual user
|
||||
the simplicity they desire), it is not acceptable for business use.
|
||||
It must be possible to enable forced-double entry, so that a
|
||||
transaction cannot be completed until two accounts have been specified.
|
||||
<p>
|
||||
<b>Current status:</b>
|
||||
<ul>
|
||||
<li>April 1998 -- The engine has a couple of flags in it that control
|
||||
double-entry behaviour: it can be made lax, or strict:
|
||||
however, they are compiled in, there is no way to change them
|
||||
from the gui.
|
||||
<li> Dec 1998 -- Scruber functions implemented to crawl through data,
|
||||
and find all unbalanced or orphaned transactions.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
<dt><b>emacs, vi, motif, kde, gnome Key Bindings for Text Fields</b>
|
||||
<dd>Make sure that text fields can handle the vi & emacs key bindings,
|
||||
so that e.g. emacs-style ctrl-a, ctrl-k does the right thing.
|
||||
<p>
|
||||
|
||||
<dt><b>Bonds & Interest Bearing Instruments</b>
|
||||
<dd>Support should be added for Mortgages, Bonds, CD's and other
|
||||
instruments (e.g. savings accounts) that pay interest on a regular
|
||||
basis. It should be possible to specify the interest rate,
|
||||
the payment schedule, and other regularly recurring transactions.
|
||||
<p>
|
||||
|
||||
<dt><b>Household Assets</b>
|
||||
<dd>Add an example showing how regular household assets (house, car,
|
||||
jewelry, etc.) should be treated. In particular, show how
|
||||
appreciation and depreciation should be treated.
|
||||
<p>
|
||||
|
||||
<dt><b>Inventory, Job Costing</b>
|
||||
<dd>Add the business features needed to maintain a stock of items for
|
||||
sale, estimating jobs.
|
||||
<p>
|
||||
|
||||
<dt><b>Payables & Receivables</b>
|
||||
<dd>Add features to track sales receipts and other pending sources
|
||||
of income, as well as owed sums.
|
||||
<p>
|
||||
|
||||
<dt><b>Check Printing</b>
|
||||
<dd>Create a check-printing ability.
|
||||
<p>
|
||||
|
||||
<dt><b>Locks</b>
|
||||
<dd>When splits are implemented, and the parent transaction has been
|
||||
marked as cleared, the record should be locked, so that further
|
||||
modifications to the amount can't be performed (or at least, a warning
|
||||
is generated. This prevents accidental garbaging up of old
|
||||
transactions.)
|
||||
<p>
|
||||
|
||||
<dt><b>Grayed-out Form Help</b>
|
||||
<dd>Create grayed out entries in the ledger, titled "Memo",
|
||||
"Description", etc, helping users understand what should be typed into
|
||||
each field.
|
||||
<p>
|
||||
|
||||
<dt><b>Accounting Periods</b>
|
||||
<dd>Ability to permanently lock records as non-editable. This should
|
||||
be straight-forward by using the "reconciled" field to hold
|
||||
"locked", and not allowing the GUI to edit locked records.
|
||||
<p>
|
||||
|
||||
<dt><b>Quicken(TM) Export</b>
|
||||
<dd>Ability to export Quicken QIF files. Quicken import is implemented
|
||||
and mostly works.
|
||||
(Note: Quicken import worked in v 1.0, but got slightly broken in v 1.1
|
||||
It no longer merges duplicate transactions when importing two or
|
||||
more QIF files. This should be easy to fix, as the "merge" routine
|
||||
is there in the code somewhere; its just not called because it was
|
||||
never restructured for the vv 1.1 engine.)
|
||||
<p>
|
||||
|
||||
<dt><b>Transaction Window Fixes</b>
|
||||
<dd>The transaction window should allow the user to specify a share
|
||||
price (when purchasing/selling shares) as well as the load
|
||||
and/or fees associated with the purchase. Fees, of course,
|
||||
are handled as separate transactions: however, it should
|
||||
still be possible to specify the fees, the transfer, and other
|
||||
details from a single window.
|
||||
<p>
|
||||
<b>Status</b>: Some basic reorganization of register was done to
|
||||
support mixed multi-line split display. However, the actual
|
||||
display of such things remaions unimplemented.
|
||||
<p>
|
||||
|
||||
<dt><b>Tab-delimited ASCII file format</b>
|
||||
<dd>People *like* to be able to read file contents in ASCII. There are
|
||||
many Unix tools for manipulating ASCII. An ASCII equivalent of the
|
||||
current file format should be easy to develop ... just substitute
|
||||
the writes with printf's. The tab-delimited format should
|
||||
be compatible with that of /rdb. The /rdb format is like so:
|
||||
<pre>
|
||||
field-name tab fieldname tab fieldname \n
|
||||
------------------------------------------ \n
|
||||
value tab value tab value \n
|
||||
value tab value tab value \n
|
||||
etc ...
|
||||
</pre>
|
||||
Its a very simple, very basic flat table format. It should match
|
||||
the SQL schemas in order to minimize I/O complexity and incompatibility.
|
||||
<p>
|
||||
|
||||
|
||||
</dl>
|
||||
</p>
|
||||
|
||||
<h2>Status</h2>
|
||||
Well, just to show that we are getting things done.
|
||||
|
||||
<dl>
|
||||
<dt><b>Getting Source with CVS</b>
|
||||
<dd> A read-only version of the cvs tree is available on the net.
|
||||
To access it, first, login, as so:
|
||||
<pre>
|
||||
cvs -d :pserver:cvs@linas.org:/home/cvs/cvsroot login
|
||||
</pre>
|
||||
The password is "guest". To get a copy of the source, do a
|
||||
<pre>
|
||||
cvs -d :pserver:cvs@linas.org:/home/cvs/cvsroot checkout xacc
|
||||
</pre>
|
||||
Note that various versions can be accessed with tags.
|
||||
For example, the tag <tt>xacc-10b17</tt> will get you version
|
||||
1.0.17 and the tag <tt>xacc-11b6</tt> will get you version 1.1.6
|
||||
In particular, the latest code in the 1.0.x series (the stable series)
|
||||
is available on the branch <tt>xacc-10-patch</tt>. For historical
|
||||
record, you can view Robin Clark's original source from October 1997
|
||||
at <tt>xacc-09a</tt>. Things have changed a *lot* since then.
|
||||
<p>
|
||||
(March 1988)
|
||||
<p>
|
||||
|
||||
|
||||
<dt><b>Version 1.1 Alpha</b>
|
||||
<dd>The Alpha development version 1.1 is out. Features include:
|
||||
<ul>
|
||||
<li>Data engine cleanly separated from GUI
|
||||
<li>Redesigned register infrastructure will make it much easier to
|
||||
create new/customer register displays, and to port to other GUI's.
|
||||
<li>Splits have been added to the engine; the GUI does not yet expose them.
|
||||
<li>Source available via anonymous CVS
|
||||
<li>Work on GTK ports have begun (thanks to Jeremy Collins & Rob
|
||||
Browning)
|
||||
</ul>
|
||||
(January 1998)
|
||||
<p>
|
||||
|
||||
<dt><b>New Improved Web Site</b>
|
||||
<dd>We now have a spiffy web site, with good graphics and
|
||||
exciting text, a mailing list, mailing list archives, and a read-only
|
||||
CVS tree. (December 1997)
|
||||
<p>
|
||||
|
||||
<dt><b>Splits</b>
|
||||
<dd>When performing a transfer, it is well-useful to allow the transfer
|
||||
to be "split" between several accounts. To implement a split,
|
||||
the best direction might be to have each transaction be a pointer
|
||||
to a set of splits, with each split having its own distinct
|
||||
credited account, memo field and currency value. Suggestion is to
|
||||
leave the debited account pointer in the main transaction, and have one
|
||||
credited account pointer in each of the splits. Also, suggest
|
||||
leaving a "cleared" flag in the main transaction, *and* putting a
|
||||
separate cleared flag in each split as well. This allows the
|
||||
cleared flag to be independently set for both the debited & credited
|
||||
accounts.
|
||||
<p>
|
||||
<b>Status:</b> Essentially more-or-less done (July/August 1998)
|
||||
<p>
|
||||
|
||||
</dl>
|
||||
|
||||
<h2>Misc Bugs</h2>
|
||||
<ul>
|
||||
<li>Allow command line to specify qif
|
||||
<li>motif -- register colors are bogus
|
||||
<li>place num trans in account in the main window.
|
||||
<li> cbb-export.qif seems to come in with the wrong sign
|
||||
<li>Ability to change bank account name -- check for prexist & merge?
|
||||
<li> ability to reparent bank account,
|
||||
<li> ability to merge accounts
|
||||
<li>ability to change account type.
|
||||
</ul>
|
||||
|
||||
<h2>Volunteers</h2>
|
||||
Your name here as project contributor!
|
||||
<ul>
|
||||
<li>Linas Vepstas <linas@linas.org> is maintaining the current GnuCash
|
||||
and is attempting to coordinate the project work.
|
||||
<li>Jeremy Collins <jcollins@gnucash.org>, originated the GnoMoney
|
||||
project, created the intial GTK port, and set up the GnuCash web site.
|
||||
<li><a href="mailto:rlb@cs.utexas.edu">Rob Browning (rlb@cs.utexas.edu)</a>
|
||||
ex-cbb'er, has ported the register to gtk, built a generic preferences
|
||||
infrastructure, got the extension language pieces to work.
|
||||
and has done some work on a GTK-based graphing package.
|
||||
<li>Robin Clark <rclark@cs.hmc.edu> wrote the *original* X-Accountant,
|
||||
which was later renamed as GnuCash.
|
||||
<li>Daniel R Risacher <risacher@worldnet.att.net> is working on a
|
||||
GTK ledger/register/spread-sheet infrastructure.
|
||||
</ul>
|
||||
This list only mentions some of the recently active developers; many,
|
||||
many others have contributed fixes and patches both large and small.
|
||||
I've tried to credit them in the README.
|
||||
<p>
|
||||
|
||||
<h2>References</h2>
|
||||
<ul>
|
||||
<li><a href="http://gnucash.ml.org/">GnuCash Home Page</a>
|
||||
<li><a href="http://www3.hmc.edu/~rclark/xacc/">X-Accountant Home Page</a>
|
||||
<li><a href="http://www.hex.net/~cbbrowne/finances.html">CBBrowne's List
|
||||
of GNU/Linux Accounting Software</a>
|
||||
<li><a href="http://www.mail-archive.com/gnucash-devel@gnucash.org/">
|
||||
GnuCash Mail archives</a>
|
||||
<li><a href="http://gnucash.org/gnucash-devel/">Official GnuCash mail archives</a>
|
||||
<li><a href="http://www.pathcom.com/~sstratos/">gstalker</a> gtk/gnome stock
|
||||
grapher.
|
||||
<li><a href="http://prope.insa-lyon.fr/~rhertzog/geniustrader/">Genius Trader</a>
|
||||
stock graphing tool. Perl & Tk based.
|
||||
<li><a href="http://www.daveware.com/linuxrapid.html">Xrapid</a>
|
||||
stock technical analysis.
|
||||
<li><a href="http://www.ios-online.de/Linux-Kontor/">Linux-Kontor,
|
||||
an industrial accounting package project.</a>
|
||||
<li>The original <a href="http://www.dnaco.net/~bcooper/watermark/index.html">
|
||||
WaterMark</a> Gnome/KDE personal finance project page.
|
||||
<li><a href="http://www.telly.org/freemoney/">FreeMoney</a> Linux
|
||||
small-business accounting s/w.
|
||||
<li><a href="http://www.didx.com/xml-builder.html">XML Builder</a>
|
||||
allows GUI screens to be described using XML markup.
|
||||
See also mozilla.org's xpfe ...
|
||||
<li><a href="http://www.ofx.net/">Open Financial Exchange</a>
|
||||
a consortium backed by Intuit, CheckFree and Microsoft
|
||||
do advance on-line banking.
|
||||
<li><a href="http://www.sabotage.net/redhat/ssl.html">SSLeay RPM's</a>
|
||||
<li><a href="http://www.sabotage.net/security/ecash/lucre/">-lucre</a>
|
||||
a publically available version of e-cash.
|
||||
<li><a href="http://www.openapplications.org/">Open Applications Group</a>
|
||||
is developing specs for accounting systems.
|
||||
<li><a href="http://www.ibm.com/java/sanfrancisco">IBM San Francisco</a>
|
||||
Business and Financial Java classes.
|
||||
<li><a href="http://www.integrion.com/">Integrion</a>, a 16-bank + IBM
|
||||
consortium aimed at building up on-line banking infrastructure.
|
||||
Mostly aimed at mainframes, middle-ware, high transaction volumes
|
||||
& data integrity.
|
||||
<li><a href="http://www.sun.com/980224/javapos/">Java Point of Sale</a>
|
||||
interfaces.
|
||||
<li><a href="ftp.gnu.org:/pub/gnu/plotutils/">Gnu Plotutils</a>
|
||||
needed for building the graphing portions of the code.
|
||||
<li><a href="http://www.im.lcs.mit.edu/~magnus/ml/">partly finished
|
||||
GTK grid widget</a> may be better than Clint, gtktable.
|
||||
<li><a href="http://glade.pn.org/">Glade</a> an XML-based
|
||||
GTK+ User Interface Builder
|
||||
<li><a href="www.php.net">PHP-3</a> for html-embedded perl-like language.
|
||||
<li><a href="http://www.engelschall.com/sw/eperl">Embedded Perl</a>
|
||||
<li><a href="http://www.transaction.net/money/">How Money Works</a>
|
||||
<li><a href="http://www.chieti.com/lpc/">Linux Projects Catalogue</a>
|
||||
<li><a href="http://www.penguincomputing.com/antarctic.html">
|
||||
Antarctic Project Server</a>
|
||||
<li><a href="http://www.projects.ml.org/">ALPS -- Another Linux Project
|
||||
Server</a>
|
||||
<li><a href="http://www.im.lcs.mit.edu/~magnus/ml/">Maxwell's Lemur
|
||||
-- a GTK based table widget</a>
|
||||
<li><a href="mailto:nw@hydaspes.if.org">Nathan Wagner (nw@hydaspes.if.org)
|
||||
</a> is working on an accounting
|
||||
<a href="http://granicus.if.org/~nw/accounting/">
|
||||
SQL table layout</a>.
|
||||
<li><a href="mailto:carew@hotmail.com">Evan Carew
|
||||
(carew@hotmail.com)</a> is working on an accounting SQL table
|
||||
layout. Evan has strong corporate accounting experience.
|
||||
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
Draft version 0.25 -- October 1998<br>
|
||||
Linas Vepstas <a href="mailto:linas@linas.org">linas@linas.org</a><br>
|
||||
</body>
|
||||
</html>
|
||||
7
Docs/fr/tidy-up
Executable file
7
Docs/fr/tidy-up
Executable file
@ -0,0 +1,7 @@
|
||||
#!/bin/ksh
|
||||
# $ID$
|
||||
# If you have Dave Raggett's "tidy" utility, this will tidy up
|
||||
# the HTML files here.
|
||||
for i in *.html ; do
|
||||
tidy -m -i $i
|
||||
done
|
||||
393
Docs/fr/xacc-about.html
Normal file
393
Docs/fr/xacc-about.html
Normal file
@ -0,0 +1,393 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>A propos de X-Accountant</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
A propos de GnuCash</H1>
|
||||
|
||||
<HR>GnuCash est un programme de suivis de vos finances personnelles. Quelques
|
||||
une de ces fonctions sont :
|
||||
<UL>
|
||||
<LI>
|
||||
Des comptes multiples , qui peuvent être ouverts en même temps.
|
||||
Créez un compte xacc pour chacun de vos comptes bancaires.</LI>
|
||||
|
||||
<LI>
|
||||
Chaque compte garde un solde actuel en plus d'un solde de pointage, alors
|
||||
vous pouvez suivre les transactions qui n'ont pas encore été
|
||||
pointés, comme les chèques en cours de règlement qui
|
||||
n'ont pas encore été débités de votre compte.</LI>
|
||||
|
||||
<LI>
|
||||
Interface facile à utiliser. Si vous savez utiliser le talon de
|
||||
votre carnet de chèques , vous savez utiliser xacc.</LI>
|
||||
|
||||
<LI>
|
||||
Rapprochement automatique du compte. A la fin du mois , ouvrez la fenêtre
|
||||
de rapprochement , entrez le solde final de votre relevé bancaire,
|
||||
et pointez les transactions qui apparaissent sur le relevé bancaire.
|
||||
Celà rend facile le dépistage de n'importe quelle écart
|
||||
ou erreurs.</LI>
|
||||
|
||||
<LI>
|
||||
QuickFill (saisie rapide)... lorsque vous commencez une saisie dans les
|
||||
champs de description , s'il retrouve une précédente transaction,
|
||||
il vous la propose,frappez <TAB> copiera alors la précédente
|
||||
transaction. Commode si vous avez des transactions semblables assez régulierement
|
||||
.</LI>
|
||||
|
||||
<LI>
|
||||
Portefeuille d'actions/de societes d'investissements (n.d.t: pour ces dernieres
|
||||
FCP et SICAV en France). Suivis d'actions individuellement (une par compte)ou
|
||||
dans un portefeuille de comptes (un groupe de comptes qui peuvent etre
|
||||
affichés ensemble ).</LI>
|
||||
|
||||
<LI>
|
||||
Support pour de multiples monnaies et comptes d'achat/vente de devises
|
||||
. (partiel, toujours défaillant). Les comptes bancaires peuvent
|
||||
être établient dans différentes monnaies, et vendus/achetés
|
||||
avec les prix indiqués qui peuvent être fait, comme les actions
|
||||
doivent être vendus/achetés.</LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-quicken.html">Importation des fichiers de Quicken</A> . Importation
|
||||
des fichiers QIF de Quicken Version 3.0 .</LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-reports.html">Rapports</A>. Affiche ou produit en HTML les
|
||||
rapports du solde et pertes/profits.</LI>
|
||||
</UL>
|
||||
|
||||
<H2>
|
||||
Fonctions Avancées</H2>
|
||||
X-Accountant possède quelques une des fonctions qui ne se trouve
|
||||
pas habituellement dans un simple logiciel de gestion de finances personnelles:
|
||||
<UL>
|
||||
<LI>
|
||||
Sous-comptes: Un compte principal peut avoir un classement de petits comptes
|
||||
ou de comptes specialisés au-dessous de lui. Cela permet d'avoir
|
||||
des types de comptes semblables (par exemple : Espèces, Banque,
|
||||
Actions) qui peuvent etre groupés dans un compte principal (par
|
||||
exemple: Possessions ou Avoirs).</LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-double.html">Double livret:</A> Chaque transaction peut apparaitre
|
||||
dans deux comptes; un compte est debité et l'autre est credité
|
||||
avec exactement le même montant. Avec le double livret , une transaction
|
||||
affichée dans une fenêtre sera automatiquement mise à
|
||||
jour dans toutes les autres fenêtres montrant cette transaction,
|
||||
et dans les deux comptes.</LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-expense.html">Types de comptes revenus/dépenses (Catégories)</A>.
|
||||
Correctement utilisés avec la fonction du double livret, ils peuvent
|
||||
être utilisés pour créer un Bilan et un rapport des
|
||||
Profits et des Pertes Par example, l'épargne des interets du compte,
|
||||
les dividendes d'actions, ou la feuille de paie peuvent etre marqué
|
||||
l'un et l'autre comme depot dans un compte bancaire , et comme gains/revenus
|
||||
dans un compte de type Revenus, utilisant la fonction du double livret
|
||||
(transfert). De la meme maniere, les paiements par la carte de credit peuvent
|
||||
etre notés dans un compte de carte de crédit , en plus du
|
||||
compte correspondant aux dépenses.</LI>
|
||||
|
||||
<LI>
|
||||
Registre general/Grand livre : Des comptes multiples peuvent être
|
||||
affichés dans une fenetre registre au même moment. Cela peut
|
||||
soulager de l'ennui du depistage d'erreurs de saisie ou d'enregistrement
|
||||
.Il permet aussi une vision pratique d'un portefeuile de beaucoup d'actions,
|
||||
en y montrant toutes les transactions dans ce portefeuille.</LI>
|
||||
</UL>
|
||||
|
||||
<H2>
|
||||
Version</H2>
|
||||
Cette version est gnucash-1.2.x, et est la dernière version stable
|
||||
de GnuCash.
|
||||
<BR>
|
||||
<H2>
|
||||
Développeurs principaux</H2>
|
||||
|
||||
<DL>
|
||||
<DT>
|
||||
Robin Clark <rclark@hmc.edu></DT>
|
||||
|
||||
<DD>
|
||||
a écrit le X-Accountant originel en Motif comme un projet scolaire,
|
||||
l'amenant jusqu'à la version 0.9 en Octobre 1997.</DD>
|
||||
|
||||
<DT>
|
||||
Linas Vepstas <linas@linas.org></DT>
|
||||
|
||||
<DD>
|
||||
comme il le dit: le GUI était léger, le code était
|
||||
documenté et bien structuré, et il était entièrement
|
||||
sous GPL. Et aussi il le ré-écrit : ajoutant des widgets
|
||||
de cellules avec XbaeMatrix, alors que les combobox et flèches devaient
|
||||
faire de nouveau une même GUI légère, réécrivant
|
||||
le code interne de X-Accountant pour lui ajouter la double-entrée,
|
||||
une hiérarchie de comptes, l'augmenta d'un mini moteur de transaction,
|
||||
ajouta le support pour les actions, et ajouta les menus d'aide. C'était
|
||||
la version 1.0 de Janvier 1998. Depuis lors, pour la version 1.1, le moteur
|
||||
fut étandu et redéfini , et le code de la fenêtre d'enregistrement
|
||||
fut completement reconçu et fait pour la plupart en Motif et independent
|
||||
du GUI. Présentant un certain prototype de OFX fonctionnant.</DD>
|
||||
|
||||
<DT>
|
||||
Jeremy Collins <jcollins@gnucash.org></DT>
|
||||
|
||||
<DD>
|
||||
fit connaitre au public largement et grandement le projet GnoMoney, et
|
||||
alors changea son nom en GnuCash. Jeremy créa le site web de gnucash.org,
|
||||
enregistra le domaine, fit fonctionner le code initial en GTK/gnome.</DD>
|
||||
|
||||
<DT>
|
||||
Rob Browning <rlb@cs.utexas.edu></DT>
|
||||
|
||||
<DD>
|
||||
abusa tout le monde pour ne pas utiliser perl, et alors ajouta le support
|
||||
guile/scheme. Rob maintient l'infrastructure de construction, traite de
|
||||
toute chose qui touche au langage d'extension guile/perl, et traite de
|
||||
configuration et configurabilité.</DD>
|
||||
|
||||
<DT>
|
||||
Dirk Schoenberger <schoenberger@signsoft.com></DT>
|
||||
|
||||
<BR> travaillle sur
|
||||
le portage en Qt/KDE
|
||||
<P>Yannick Le Ny <y-le-ny@ifrance.com>
|
||||
<BR> Localise
|
||||
(traduction et adaptation) de Xacc et Gnucash pour la France et les pays
|
||||
francophones.
|
||||
<BR> Travail
|
||||
effectué :traduction du Readme, des messages et de l'aide en ligne
|
||||
de Gnucash en français
|
||||
<BR> Essaie
|
||||
de finir de traduire tout le site web de Gnucash en français sauf
|
||||
la liste de courriers et de le maintenir à jour</DL>
|
||||
|
||||
<H2>
|
||||
Correctifs et patches</H2>
|
||||
Andrew Arensburger <arensb@cfar.umd.edu> for FreeBSD & other patches
|
||||
<BR>Matt Armstrong <matt_armstrong@bigfoot.com> for misc fixes
|
||||
<BR>Fred Baube <fred@moremagic.com> for attempted Java port/MoneyDance
|
||||
<BR>Christopher B. Browne <cbbrowne@hex.net> for perl stock scripts
|
||||
<BR>Graham Chapman <grahamc@zeta.org.au> for the xacc-rpts addon package
|
||||
<BR>George Chen <georgec@sco.com> for MS-Money QIF's & fixes
|
||||
<BR>Jeremey Collins <jcollins@gnucash.org> for GnoMoney & GTK port
|
||||
<BR>Patrick Condron <pcondon@rackspace.com> for webserver and T1 connection.
|
||||
<BR>Ciaran Deignan <Ciaran.Deignan@bull.net> for AIX binary version
|
||||
<BR>Tyson Dowd <tyson@tyse.net> for config/make patches & debian
|
||||
maint.
|
||||
<BR>Koen D'Hondt <ripley@xs4all.nl> for Solaris patches to XmHTML
|
||||
<BR>Bob Drzyzgula <bob@mostly.com> for budgeting design notes
|
||||
<BR>Jan-Uwe Finck <ju_finck@mail.netwave.de> for German message translation
|
||||
<BR>Ron Forrester <rjf@aracnet.com> for gnome patches
|
||||
<BR>Dave Freese <DFreese@osc.uscg.mil> for leap-year fix
|
||||
<BR>Otto Hammersmith <otto@bug.redhat.com> for RedHat RPM version
|
||||
<BR>Alexandru Harsanyi <haral@codec.ro> for misc core dumps & lockups.
|
||||
<BR>Jon K}re Hellan <jk@isdn-a33.itea.ntnu.no> misc core dump fixes
|
||||
<BR>Prakash Kailasa <PrakashK@bigfoot.com> for gnome build fixes
|
||||
<BR>Tom Kludy <tkludy@csd.sgi.com> for SGI Irix port
|
||||
<BR>Sven Kuenzler <sk@xgm.de> for SuSE README file
|
||||
<BR>Ted Lemon <mellon@andare.fugue.com> for NetBSD port
|
||||
<BR>Yannick Le Ny <y-le-ny@ifrance.com> pour la traduction en francais
|
||||
<BR>G. Allen Morris III <gam3@ann.softgams.com> for QIF core dump
|
||||
<BR>Peter Norton <spacey@inch.com> for a valiant attempt at a GTK port
|
||||
<BR>OmNiBuS <webmaster@obsidian.uia.net> web site graphics & content
|
||||
<BR>Myroslav Opyr <mopyr@IPM.Lviv.UA> for misc patches
|
||||
<BR>Alain Peyrat <Alain.Peyrat@nmu.alcatel.fr> for configure.in patches
|
||||
<BR>Gavin Porter <maufk@csv.warwick.ac.uk> for euro style dates
|
||||
<BR>Ron Record <rr@sco.com> for SCO Unixware & OpenServer binaries
|
||||
<BR>Christopher Seawood <cls@seawood.org> for XbaeMatrix core dump
|
||||
<BR>Mike Simons <msimons@fsimons01.erols.com> misc configure.in patches
|
||||
<BR>Richard Skelton <rich@brake.demon.co.uk> for Solaris cleanup
|
||||
<BR>Henning Spruth <spruth@bigfoot.com> for German text & euro date
|
||||
rework
|
||||
<BR>Ken Yamaguchi <gooch@ic.EECS.Berkeley.EDU> QIF import fixes; MYM
|
||||
import
|
||||
<BR>
|
||||
<H2>
|
||||
Systèmes d'exploitation supportés</H2>
|
||||
gnucash-1.0.18 (ex xacc-1.0.18) est conu pour fonctioner dans ces différentes
|
||||
configurations:
|
||||
<BR>Linux 2.0.x -- Intel w/ RedHat Motif
|
||||
<BR>Linux 2.0.x -- Intel w/ Lesstif v0.81
|
||||
<BR>Linux Debian -- Intel w/ Lesstif v0.81
|
||||
<BR>SGI IRIX -- MIPS
|
||||
<BR>IBM AIX 4.1.5 -- RS/6000
|
||||
<BR>SCO Unixware 7 -- Intel
|
||||
<BR>SCO OpenServer 5.0.4 -- Intel
|
||||
<BR>NetBSD -- Intel
|
||||
<BR>
|
||||
<P><A HREF="http://www.gnucash.org/"><IMG SRC="linux.gif" HEIGHT=102 WIDTH=121></A><A HREF="http://www.sco.com/skunkware"><IMG SRC="skunkware.gif" HEIGHT=80 WIDTH=108></A><A HREF="http://www.bull.de/pub/"><IMG SRC="bullogogross.gif" HEIGHT=75 WIDTH=75></A><A HREF="http://www.bull.de/pub/"><IMG SRC="ibm.gif" HEIGHT=54 WIDTH=93></A><A HREF="http://www.sgi.com/"><IMG SRC="sgi.gif" HEIGHT=43 WIDTH=151></A><A HREF="http://www.debian.org/"><IMG SRC="debian.jpg" HEIGHT=140 WIDTH=114></A><IMG SRC="NetBSD-banner.gif" HEIGHT=44 WIDTH=98>
|
||||
<H2>
|
||||
Historique</H2>
|
||||
Le tableau ci-dessous montre quelques historiques de lignes de code et
|
||||
le nombre de fichiers comptés pour le dévelopement du projet
|
||||
X-Accountant/GnuCash
|
||||
<TABLE BORDER >
|
||||
<CAPTION>Statistiques de l'historique du dévelopement</CAPTION>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TH>Version </TH>
|
||||
|
||||
<TH>moteur </TH>
|
||||
|
||||
<TH>registre </TH>
|
||||
|
||||
<TH>grand livre </TH>
|
||||
|
||||
<TH>motif </TH>
|
||||
|
||||
<TH>prefs (scm) </TH>
|
||||
|
||||
<TH>docs (html) </TH>
|
||||
|
||||
<TH>divers </TH>
|
||||
|
||||
<TH>Total </TH>
|
||||
</TR>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TD>xacc-0.9
|
||||
<BR>Sept 97 </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>34 fichiers
|
||||
<BR>(7.5+0.9) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>5 fichiers
|
||||
<BR>(0.4) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>39 fichiers
|
||||
<BR>(8.8) </TD>
|
||||
</TR>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TD>xacc-0.9w
|
||||
<BR>Dec 97 </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>51 fichiers
|
||||
<BR>(13.8+1.5) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>9 fichiers
|
||||
<BR>(0.8) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>60 fichiers
|
||||
<BR>(16.1) </TD>
|
||||
</TR>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TD>xacc-1.0.17
|
||||
<BR>Fev 98</TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>52 files
|
||||
<BR>(14.8+1.8) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>12 files
|
||||
<BR>(1.4) </TD>
|
||||
|
||||
<TD>- </TD>
|
||||
|
||||
<TD>64 files
|
||||
<BR>(18.0) </TD>
|
||||
</TR>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TD>gnucash-1.1.15
|
||||
<BR>Aou 98 </TD>
|
||||
|
||||
<TD>24 fichiers
|
||||
<BR>(6.2+1.5) </TD>
|
||||
|
||||
<TD>31 fichiers
|
||||
<BR>(6.1+1.7) </TD>
|
||||
|
||||
<TD>5 fichiers
|
||||
<BR>(1.4+0.4) </TD>
|
||||
|
||||
<TD>30 fichiers
|
||||
<BR>(7.4+0.7) </TD>
|
||||
|
||||
<TD>3 fichiers
|
||||
<BR>(0.3) </TD>
|
||||
|
||||
<TD>16 fichiers
|
||||
<BR>(1.9) </TD>
|
||||
|
||||
<TD>non compté
|
||||
<BR>(>1.0) </TD>
|
||||
|
||||
<TD>109 fichiers
|
||||
<BR>(32.9) </TD>
|
||||
</TR>
|
||||
|
||||
<TR ALIGN=CENTER>
|
||||
<TD>gnucash-1.2.2
|
||||
<BR>Aou 99 </TD>
|
||||
|
||||
<TD>41 fichiers
|
||||
<BR>(10.2+3.6) </TD>
|
||||
|
||||
<TD>28 fichiers
|
||||
<BR>(5.5+1.7) </TD>
|
||||
|
||||
<TD>14 fichiers
|
||||
<BR>(2.4+0.6) </TD>
|
||||
|
||||
<TD>26 fichiers
|
||||
<BR>(8.7+0.5) </TD>
|
||||
|
||||
<TD>14 fichiers
|
||||
<BR>(1.4) </TD>
|
||||
|
||||
<TD>30 fichiers
|
||||
<BR>(2.6) </TD>
|
||||
|
||||
<TD>non compté
|
||||
<BR>(>1.0) </TD>
|
||||
|
||||
<TD>153 fichiers
|
||||
<BR>(37.2) </TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
|
||||
<P>Chaque cellule contient:
|
||||
<P>nombre de fichiers *c et *.h
|
||||
<BR>(KLOCS dans *.c + KLOCS dans *.h),
|
||||
<P>où KLOC == kilo-lignes-de-code, comme rapported par <TT>wc</TT>.
|
||||
<BR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
83
Docs/fr/xacc-acctypes.html
Normal file
83
Docs/fr/xacc-acctypes.html
Normal file
@ -0,0 +1,83 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Account Types</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Types de comptes</H1>
|
||||
|
||||
<DL>
|
||||
<DT>
|
||||
<B>Banque</B></DT>
|
||||
|
||||
<DD>
|
||||
Le type de compte banque contient l'épargne ou le compte chèques
|
||||
détenu dans une banque. Souvent rémunéré(n.d.t
|
||||
: pas en france).</DD>
|
||||
|
||||
<DT>
|
||||
<B>Liquidités</B></DT>
|
||||
|
||||
<DD>
|
||||
Le type de compte liquidités est utilisé pour contenir une
|
||||
réserve , une boite à chaussures ou une taie d'oreiller bourré
|
||||
d'argent/ liquidités .</DD>
|
||||
|
||||
<DT>
|
||||
<B>Carte de crédit</B></DT>
|
||||
|
||||
<DD>
|
||||
Le compte carte de crédit est utilisé pour contenir des comptes
|
||||
de carte de credit (par exemple american express) et debit (par exemple
|
||||
visa, eurocard/mastercard, carte bleue).</DD>
|
||||
|
||||
<DT>
|
||||
<B>Avoir, Dette</B></DT>
|
||||
|
||||
<DD>
|
||||
Les compte avoir et dette indique des comptes généralisés,
|
||||
générique qui ne sont dans aucun de ceux ci-dessus.</DD>
|
||||
|
||||
<DT>
|
||||
<B>Actions, OPCVM (SICAV et FCP)</B></DT>
|
||||
|
||||
<DD>
|
||||
Les comptes d'actions et OPCVM seront typiquement montré dans des
|
||||
registres qui montreront trois colonnes: cours, nombre de titres, et montant.</DD>
|
||||
|
||||
<DT>
|
||||
<B>Revenus, Dépenses</B></DT>
|
||||
|
||||
<DD>
|
||||
Les comptes de revenus et dépenses sont utilisés pour contenir
|
||||
les revenus et dépenses. Ainsi, quand les données dans ces
|
||||
comptes sont affichées, le signe des entrées est inversé
|
||||
par rapport à l'usage habituel.</DD>
|
||||
|
||||
<DT>
|
||||
<B>Capitaux propres</B></DT>
|
||||
|
||||
<DD>
|
||||
Le compte capitaux propres est utilisé pour équilibrer la
|
||||
feuille du bilan.</DD>
|
||||
|
||||
<DT>
|
||||
<B>Devises</B></DT>
|
||||
|
||||
<DD>
|
||||
Les comptes de devises sont utilisés pour faire du commerce/spéculer
|
||||
sur les devises. Dans beaucoup de cas, ils se comportent comme les actions,
|
||||
excepter que le calcul de la valeur est différent. Noter que les
|
||||
transferts ne peuvent pas être fait directement entre deux comptes
|
||||
libellés dans des monnaies/devises différentes. De tel transferts
|
||||
ne peuvent être seulement fait qu'à l'intérieur de
|
||||
comptes de commerce de devises. (Les vérification de sécurité
|
||||
pevent être en partie toujours défaillantes ... )</DD>
|
||||
</DL>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
32
Docs/fr/xacc-accwin.html
Normal file
32
Docs/fr/xacc-accwin.html
Normal file
@ -0,0 +1,32 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Fenêtre nouveau compte</TITLE>
|
||||
<X-SAS-WINDOW TOP=0 BOTTOM=481 LEFT=0 RIGHT=786>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Fenêtre Nouveau Compte</H1>
|
||||
|
||||
<P><BR>Ci-dessous se trouve à quoi ressemble une fenêtre nouveau
|
||||
compte :
|
||||
<BR>
|
||||
<P><IMG SRC="newaccwin-code.gif" HEIGHT=550 WIDTH=494>
|
||||
<P>Choisissez <A HREF="xacc-acctypes.html><b>Account Type</b></a>. Fill in the blanks ... blah blah blah. The <b>Currency</b> field should typically be a three-letter ISO curency code (e.g. USD for U.S. Dollars, etc.) The <b>Account Code</b> is a number that determines the <a href=" xacc-groups.html">trier
|
||||
par ordre</A> pour le compte quand il apparait dans un rapport ou dans
|
||||
le <B><A HREF="xacc-groups.html">Tableau de comptes</A></B>.
|
||||
<P>L'image ci-dessus montre un exemple pour un compte d'actions ou de d'achat/ventes
|
||||
de monnaies/devises. Noter que le champ Security n'est pas grisé,
|
||||
et que vous pouvez entrer une valeur. Cette valeur est typiquement un code
|
||||
de valeur d'une action, ou un code monétaire à trois lettres
|
||||
ISO.
|
||||
<BR>
|
||||
<P><IMG SRC="newaccwin-trade.gif" HEIGHT=550 WIDTH=494>
|
||||
<BR>
|
||||
<BR>
|
||||
<BR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
20
Docs/fr/xacc-adjbwin.html
Normal file
20
Docs/fr/xacc-adjbwin.html
Normal file
@ -0,0 +1,20 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Fenêtre d'ajustement du solde</TITLE>
|
||||
<META NAME=GENERATOR CONTENT="Claris Home Page 2.0">
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>CE FICHIER EST VIDE</H1>
|
||||
|
||||
<P>Fenêtre d'ajustement du solde. Utiliser la pour ajuster le
|
||||
solde. Entrez le montant en francs , et une entrée dans le
|
||||
registre sera créée qui mettra le solde courant
|
||||
équivalent à ce nouveau solde. Ajouter plus de
|
||||
documentation ici.
|
||||
<HR>
|
||||
</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
54
Docs/fr/xacc-apar.html
Normal file
54
Docs/fr/xacc-apar.html
Normal file
@ -0,0 +1,54 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
|
||||
<H1>
|
||||
Dettes (dus aux) fournisseurs et crédit ( à recevevoir des)
|
||||
fournisseurs</H1>
|
||||
C/F et D/F sont des types en profondeur,
|
||||
<P>En tous cas, considérons C/F. Nous ne pouvons rien réellement
|
||||
raconter sur les D/F parce que nous payons toujours *nos* factures à
|
||||
temps, n'est ce pas ? :-)
|
||||
<P>Ainsi de toute façon, disons que nous donnons à nos clients
|
||||
30 jours pour payer.
|
||||
<P>Quand nous faisons une vente, les deux comptes affectés sont
|
||||
les Ventes (un compte revenus) et C/F. C/F est un avoir, mais il n'est
|
||||
pas liquide, et il n'est pas forcément en espèces/argent
|
||||
comptant.
|
||||
<P>Alors quand ils réusissent à payer leurs factures, diminuant/déposant
|
||||
un gros sac de vingt dollars de factures, nous transférons le montant
|
||||
depuis C/F vers liquidités.
|
||||
<P>La raison pour laquelle nous le faisons en deux étapes est que
|
||||
nous avons decidés de faire notre comptabilité sur une base
|
||||
d'accumulation et non sur une base de liquidités, parce que , et
|
||||
bien, la plupart de nos transactions ne sont pas en liquidités,
|
||||
ce sont des engagements.
|
||||
<P>Nous reportons les ventes dans nos chiffres de ventes au moment où
|
||||
nous les faisons, mais si l'auditeur veut savoir à propos de ou
|
||||
si nous les avions récupérer avec des erreurs (stuck)
|
||||
avec de mauvais débits, nous brisons ces A/R par une durée
|
||||
telle qu'ils ont : 0-30 supposés, 31-60 supposés, etc. A
|
||||
un certain point quand un débit particulier est "nul ou annulé",
|
||||
comme quand les salauds qui en n'ont marre vont en faillite, nous coupons/arrimons
|
||||
ensemble C/F et les ventes, ainsi nous reprenons et arrangeons (ou plutôt,
|
||||
"désarrangeons") le compte ventes pour montrer que les ventes
|
||||
n'était jamais très bonnes.
|
||||
<P>Nous pouvons utiliser la même technique pour les choses que nous
|
||||
payons à l'avance. Si nous devons payer six mois de location en
|
||||
avance, c'est un "avoir accru", et tandis qu'il porte une atteinte saine
|
||||
dans le compte de liquidités, il apparait sur les livres comme un
|
||||
avoir. Et if nous avons été collecter les taxes des feuilles
|
||||
de paie de nos employés et les conservont dans un compte bancaire
|
||||
spécial, l'argent n'est pas réellement le nôtre, alors
|
||||
nous avons une augmentation dans le compte des liquidités
|
||||
d'un coté, et une augmentation dans un compte nommé Liquidités
|
||||
accumulés, et les Taxes de la feuille de paie à payer d'un
|
||||
autre côté. Quand nous envoyons le chèque trimestriel
|
||||
aux Impots (ndt : aux USA) ainsi qu'ils peuvent faire une feuille de paie
|
||||
aussi, notre dette chute et ainsi de même pour notre compte de Liquidités.
|
||||
</BODY>
|
||||
</HTML>
|
||||
43
Docs/fr/xacc-currency.html
Normal file
43
Docs/fr/xacc-currency.html
Normal file
@ -0,0 +1,43 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
Un système à double entrée stocke les valeurs ensemble
|
||||
<BR>(et effectue le solde/bilan des transactions):
|
||||
<P>états de la double entrée où value1+value2+value3+
|
||||
... = 0
|
||||
<BR>et dont chaque valeur est enregistrée dans un compte différent.
|
||||
<BR>Une valeur est : valeur=Taux de change*montant (pour les comptes de
|
||||
devises/monnaies)
|
||||
<BR> valeur=cours*nombre
|
||||
de parts (pour les actions/FCP et SICAV)
|
||||
<P>Ainsi, acheter un gadget au japon et utiliser des dollars pour le payer
|
||||
devrait apparaitre
|
||||
<BR>commme ceci:
|
||||
<P>SpendAcct: (un compte banque/liquidités ordinaire libellé
|
||||
en USD)
|
||||
<BR>----------
|
||||
<BR>Date transfert depuis
|
||||
mémo
|
||||
cout
|
||||
<BR>1/5/99 [YenAcct]
|
||||
Achat gadget $1.00
|
||||
<BR>
|
||||
<P>YenAcct: (un compte d'achat/vente de devises libellé en yen)
|
||||
<BR>--------
|
||||
<BR>Date transfert depuis
|
||||
mémo
|
||||
achat taux
|
||||
<BR>1/5/99 [SpendAcct] Buy widget
|
||||
Y150 0.00667
|
||||
<BR>
|
||||
<P>Le moteur lie ,toutes les trois, ces valeurs ensemble (1.0, 150, 0.00667)
|
||||
<BR>en permanence et les rend imposssible à changer sans en changer
|
||||
une autre,
|
||||
<BR>ainsi que la grande addition est toujours zéro.
|
||||
<BR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
45
Docs/fr/xacc-date.html
Normal file
45
Docs/fr/xacc-date.html
Normal file
@ -0,0 +1,45 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
|
||||
<H1>
|
||||
L'entrée de date</H1>
|
||||
La cellule/case de la date fonctionne avec les raccourcis clavier suivant
|
||||
:
|
||||
<PRE> '+':
|
||||
'=': incrémente d'un jour
|
||||
|
||||
'_':
|
||||
'-': décremente d'un jour
|
||||
|
||||
'}':
|
||||
']': incrémente d'u mois
|
||||
|
||||
'{':
|
||||
'[': décrémente d'un mois
|
||||
|
||||
'M':
|
||||
'm': début du mois
|
||||
|
||||
'H':
|
||||
'h': fin du mois
|
||||
|
||||
'Y':
|
||||
'y': début de l'année
|
||||
|
||||
'R':
|
||||
'r': fin de l'année
|
||||
|
||||
'T':
|
||||
't': aujourd'hui
|
||||
|
||||
</PRE>
|
||||
GnuCash peut-être compiler pour comprendre/utiliser soit les dates
|
||||
au format européen ou les dates au format américain . Chercher
|
||||
UK_DATES dans dates.h
|
||||
</BODY>
|
||||
</HTML>
|
||||
75
Docs/fr/xacc-double.html
Normal file
75
Docs/fr/xacc-double.html
Normal file
@ -0,0 +1,75 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Utilisation de la fonction de la double entrée</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H2>
|
||||
Qu'est-ce que c'est la Double Entrée?</H2>
|
||||
La double entrée est une méthodologie comptable utilisée
|
||||
par les professionnels pour s'assurer que tous les comptes sont correctement
|
||||
equilibré/égaux . Quand les comptes s'équilibrent
|
||||
, la probabilité qu'une erreur sur les données entrées
|
||||
est été faite est beaucoup moindre. Pour les grands et complexes
|
||||
comptes avec beaucoup de transactions , il est facile de faire des erreurs
|
||||
qui peuvent continuer à rester undétectées pendant
|
||||
longtemps. La double-entrée est une technologie décisive
|
||||
pour retrouver ces erreurs .
|
||||
<P>Une transaction à double entrée est une transaction qui
|
||||
apparaît dans deux comptes . Un compte est débité d'un
|
||||
montant exactement égal à celui qui est crédité.
|
||||
Ainsi , toutes les transactions sont toujours transférées
|
||||
entre deux comptes . Depuis qu'ils apparaisent toujours avec un signe plus
|
||||
dans un compte , et un signe moins dans l'autre , le total global des comptes
|
||||
sera toujours zero, et ainsi , les comptes équilibrés sont
|
||||
garantis.
|
||||
<P>La double entrée est déjà familiaire à beaucoup
|
||||
de gens comme un transfert d'un compte bancaire vers un autre , où
|
||||
l'argent est retiré d'un compte et déposé dans un
|
||||
autre. Beaucoup moins familier est l'idée que la double entrée
|
||||
peut être utilisée pour le suivi des revenus et dépenses
|
||||
aussi bien que pour les transferts bancaires . Regardez la fenêtre
|
||||
d'aide "<A HREF="xacc-expense-fr.html">Revenu/Dépense</A>" pour
|
||||
plus d'information.
|
||||
<H2>
|
||||
Utiliser la Double Entrée</H2>
|
||||
Pour utiliser la double entrée, cliquez sur le bouton dans la colonne
|
||||
marqué "Transfert depuis" sur le côté gauche du registre.
|
||||
Un menu se déroulera , listant tous les comptes depuis lequel un
|
||||
transfert peut être réalisée. Selectionnez-en un. Quand
|
||||
vous enregistrez la transaction, la double entrée sera automatiquement
|
||||
réalisée, et la transaction apparaîtra automatiquement
|
||||
dans toutes les fenêtres montrant les comptes transféré-depuis
|
||||
et transféré-vers.
|
||||
<P>Pour changer une transaction à double entrée, afficher
|
||||
la dans n'importe quelle fenêtre dans laquelle elle apparait. N'importe
|
||||
quel changement effectué sera automatiquement reflété
|
||||
dans l'ensemble des comptes et toutes les fenêtres affichant la transaction.
|
||||
Similairement, quand une transaction à double entrée est
|
||||
supprimée , elle esr supprimée depuis l'ensemble des comptes
|
||||
; les soldes sont automatiquement recalculés pour l'ensemble des
|
||||
comptes .
|
||||
<P>Pour changer le compte de transfert, sélectionnez simplement
|
||||
un nouveau compte depuis le menu déroulant . Quand vous enregistrez
|
||||
la transaction, elle sera automatiquement selectionnée depuis le
|
||||
vieux compte , et insérée dans le nouveau compte .
|
||||
<H2>
|
||||
Nettoyage impeccable</H2>
|
||||
GnuCash peut être configuré pour être strict à
|
||||
propos de la double entrée, ou d'être relaché. En mode
|
||||
relaché, vous pouvez créer des transactions anormales, c'est
|
||||
à dire, les transactions qui ne s'apparie pas avec une entrée
|
||||
appariée, et ainsi ne s'équilibre pour faire zéro.
|
||||
Pour nettoyer ces transactions anormales, vous pouvez <B>nettoyer</B> le
|
||||
compte pour être net en choisissant "Nettoyage" à partir de
|
||||
la fenêtre du menu. Celà examinera chaque transaction; si
|
||||
la transaction ne s'équilibre pas, une entrée divisée
|
||||
sera créée et placée dans un compte nommé "Anormal".
|
||||
Vous pouvez alors revoir ces divisions et les déplacer vers leurs
|
||||
comptes appropriés.
|
||||
</BODY>
|
||||
</HTML>
|
||||
89
Docs/fr/xacc-expense.html
Normal file
89
Docs/fr/xacc-expense.html
Normal file
@ -0,0 +1,89 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Utilisation des comptes Revenus/Dépenses</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H2>Qu'est-ce qu'un compte Revenu/Dépense?</H2>
|
||||
|
||||
<P>Les mots "Revenu" et "Dépenses " sont bigrement simple;
|
||||
n'importe qui sait ce qu'ils veulent dire. Ne les laisser pas vous
|
||||
amuser: ils ont une signification spéciale quand ils sont
|
||||
appliqué à un compte à double entrée.
|
||||
</P>
|
||||
|
||||
<P>Pour enregistrer correctement les revenus et dépenses dans
|
||||
un système à double entrée , deux comptes
|
||||
spéciaux doivent être créés: un de type
|
||||
"Revenu" et un de type "Dépenses ". Les Revenus de ce genre:
|
||||
salaire, primes , intérêt bancaire et les dividendes
|
||||
d'actions sont alors enregistrés comme transferts depuis un
|
||||
compte revenus vers un compte bancaire (ou
|
||||
générallement actif(avoirs)) . Semblablement, les
|
||||
dépenses sont enregistrés comme des transferts depuis
|
||||
un compte de carte de crédit (ou générallement,
|
||||
un compte de passif(dettes)).</P>
|
||||
|
||||
<P>Pourquoi les comptes de type "Revenu" et "Dépenses " sont
|
||||
considérés comme speciaux? La réponse ruse avec
|
||||
la nature de la double entrée. Avec une transaction à
|
||||
double entrée, un compte est toujours crédité,
|
||||
et un autre compte est toujours débité. Quand le
|
||||
salaire est déposé dans un compte bancaire , le compte
|
||||
bancaire est crédité, et le compte revenus est
|
||||
débité. Afin de faire apparaitre revenus comme positif
|
||||
(ce qu'il est), et dépenses paraissant négatives, la
|
||||
signification de "débit" et "crédit" est
|
||||
renversée pour les comptes de revenus et dépenses .
|
||||
Celà les rends spéciaux.</P>
|
||||
|
||||
<P>Une autre manière de voir dans laquelle les comptes revenus
|
||||
et dépenses sont spéciaux est que leurs totaux de
|
||||
compte n'apparaissent pas sur le bilan. Un bilan montre "Valeur nette
|
||||
": la somme de tous les actifs(avoirs) moins les passifs(dettes).
|
||||
Depuis lors revenus et dépenses ne sont ni actifs(avoirs) ni
|
||||
passifs(dettes), ils n'apparaissent pas sur le bilan. Il y a
|
||||
différente sorte de rapport, un rapport "Profit et Pertes"
|
||||
(P&P) , qui montre revenus et dépenses . Le profit total
|
||||
(ou pertes) est le total des revenus moins le total des
|
||||
dépenses. Depuis lors actifs(avoirs) et passifs(dettes) ne
|
||||
sont ni revenus ni dépenses, ils n'apparaissent pas sur
|
||||
l'état des P&P.</P>
|
||||
|
||||
<P>Même si malgré tout les comptes peuvent être
|
||||
"spéciaux", vous n'avez pas besoin de faire quelque chose de
|
||||
"spécial" pour utiliser les comptes revenus et dépenses
|
||||
. Tout est traité automatiquement , tant que vous vous
|
||||
souvenez de transférer revenus et dépenses entre les
|
||||
comptes de revenus/dépenses et les comptes bancaire
|
||||
courant/Actif/Carte(de crédit)/Passif(dettes).</P>
|
||||
|
||||
<H2>Utiliser les comptes Revenus/Dépenses</H2>
|
||||
|
||||
<P>Pour utiliser un compte revenus/dépenses, créez -en
|
||||
un simplement depuis la fenêtre de dialogue "Nouveau Compte" ,
|
||||
et alors soyez sûr de transférer revenus/dépenses
|
||||
vers celui oû vous enregistrez feuille de paie ,
|
||||
intérêt, etc.</P>
|
||||
|
||||
<P>Si vous avez un arrangement complexe de compte, vous pouvez
|
||||
vouloir creer des comptes multiples de revenus/dépenses . Un
|
||||
peut être utilisé pour enregistrer le salaire , et
|
||||
seulement le salaire , un autre pour enregistrer seulement les
|
||||
intérêts de banque, et un troisième seulement
|
||||
pour enregistrer les dividendes d'actions. Ce partitionnement est
|
||||
particulièrement utile quand le temps des impôts arrive.
|
||||
</P>
|
||||
|
||||
<H2>Notes</H2>
|
||||
|
||||
<P>Les utilisateurs des produits Quicken (TM) doivent réaliser
|
||||
que ce que Quicken appelle "Catégories" sont juste
|
||||
réellement des comptes Revenus/Dépenses . Ainsi , si
|
||||
vous utilisez la spécification d'une catégorie dans
|
||||
Quicken, créez juste un compte revenus/dépenses du
|
||||
même nom dans X-Accountant, et utilisez le.</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
334
Docs/fr/xacc-gpl.html
Normal file
334
Docs/fr/xacc-gpl.html
Normal file
@ -0,0 +1,334 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>GNU General Public License</title>
|
||||
</head>
|
||||
|
||||
<body bgcolor=#eeeeee>
|
||||
<h1>GNU General Public License</h1>
|
||||
<h2>Version 2, June 1991</h2>
|
||||
|
||||
<CENTER>
|
||||
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
|
||||
675 Mass Ave, Cambridge, MA 02139, USA<P>
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.<P>
|
||||
</CENTER>
|
||||
<P>
|
||||
<h3><a name="SEC001">Preamble</a></h3>
|
||||
|
||||
<P>
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
License is intended to guarantee your freedom to share and change free
|
||||
software--to make sure the software is free for all its users. This
|
||||
General Public License applies to most of the Free Software
|
||||
Foundation's software and to any other program whose authors commit to
|
||||
using it. (Some other Free Software Foundation software is covered by
|
||||
the GNU Library General Public License instead.) You can apply it to
|
||||
your programs, too.
|
||||
|
||||
<P>
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
this service if you wish), that you receive source code or can get it
|
||||
if you want it, that you can change the software or use pieces of it
|
||||
in new free programs; and that you know you can do these things.
|
||||
|
||||
<P>
|
||||
To protect your rights, we need to make restrictions that forbid
|
||||
anyone to deny you these rights or to ask you to surrender the rights.
|
||||
These restrictions translate to certain responsibilities for you if you
|
||||
distribute copies of the software, or if you modify it.
|
||||
|
||||
<P>
|
||||
For example, if you distribute copies of such a program, whether
|
||||
gratis or for a fee, you must give the recipients all the rights that
|
||||
you have. You must make sure that they, too, receive or can get the
|
||||
source code. And you must show them these terms so they know their
|
||||
rights.
|
||||
|
||||
<P>
|
||||
We protect your rights with two steps: (1) copyright the software, and
|
||||
(2) offer you this license which gives you legal permission to copy,
|
||||
distribute and/or modify the software.
|
||||
|
||||
<P>
|
||||
Also, for each author's protection and ours, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
software. If the software is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original, so
|
||||
that any problems introduced by others will not reflect on the original
|
||||
authors' reputations.
|
||||
|
||||
<P>
|
||||
Finally, any free program is threatened constantly by software
|
||||
patents. We wish to avoid the danger that redistributors of a free
|
||||
program will individually obtain patent licenses, in effect making the
|
||||
program proprietary. To prevent this, we have made it clear that any
|
||||
patent must be licensed for everyone's free use or not licensed at all.
|
||||
|
||||
<P>
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow.
|
||||
</P>
|
||||
<HR>
|
||||
<h3><a name="SEC002">GNU GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</a></h3>
|
||||
|
||||
<P>
|
||||
0. This License applies to any program or other work which contains
|
||||
a notice placed by the copyright holder saying it may be distributed
|
||||
under the terms of this General Public License. The "Program", below,
|
||||
refers to any such program or work, and a "work based on the Program"
|
||||
means either the Program or any derivative work under copyright law:
|
||||
that is to say, a work containing the Program or a portion of it,
|
||||
either verbatim or with modifications and/or translated into another
|
||||
language. (Hereinafter, translation is included without limitation in
|
||||
the term "modification".) Each licensee is addressed as "you".
|
||||
|
||||
<P>
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running the Program is not restricted, and the output from the Program
|
||||
is covered only if its contents constitute a work based on the
|
||||
Program (independent of having been made by running the Program).
|
||||
Whether that is true depends on what the Program does.
|
||||
|
||||
<P>
|
||||
1. You may copy and distribute verbatim copies of the Program's
|
||||
source code as you receive it, in any medium, provided that you
|
||||
conspicuously and appropriately publish on each copy an appropriate
|
||||
copyright notice and disclaimer of warranty; keep intact all the
|
||||
notices that refer to this License and to the absence of any warranty;
|
||||
and give any other recipients of the Program a copy of this License
|
||||
along with the Program.
|
||||
|
||||
<P>
|
||||
You may charge a fee for the physical act of transferring a copy, and
|
||||
you may at your option offer warranty protection in exchange for a fee.
|
||||
|
||||
<P>
|
||||
2. You may modify your copy or copies of the Program or any portion
|
||||
of it, thus forming a work based on the Program, and copy and
|
||||
distribute such modifications or work under the terms of Section 1
|
||||
above, provided that you also meet all of these conditions:
|
||||
|
||||
<blockquote>
|
||||
a) You must cause the modified files to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
<P>
|
||||
b) You must cause any work that you distribute or publish, that in
|
||||
whole or in part contains or is derived from the Program or any
|
||||
part thereof, to be licensed as a whole at no charge to all third
|
||||
parties under the terms of this License.
|
||||
<P>
|
||||
c) If the modified program normally reads commands interactively
|
||||
when run, you must cause it, when started running for such
|
||||
interactive use in the most ordinary way, to print or display an
|
||||
announcement including an appropriate copyright notice and a
|
||||
notice that there is no warranty (or else, saying that you provide
|
||||
a warranty) and that users may redistribute the program under
|
||||
these conditions, and telling the user how to view a copy of this
|
||||
License. (Exception: if the Program itself is interactive but
|
||||
does not normally print such an announcement, your work based on
|
||||
the Program is not required to print an announcement.)
|
||||
</P>
|
||||
</blockquote>
|
||||
|
||||
<HR>
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Program,
|
||||
and can be reasonably considered independent and separate works in
|
||||
themselves, then this License, and its terms, do not apply to those
|
||||
sections when you distribute them as separate works. But when you
|
||||
distribute the same sections as part of a whole which is a work based
|
||||
on the Program, the distribution of the whole must be on the terms of
|
||||
this License, whose permissions for other licensees extend to the
|
||||
entire whole, and thus to each and every part regardless of who wrote it.
|
||||
|
||||
<P>
|
||||
Thus, it is not the intent of this section to claim rights or contest
|
||||
your rights to work written entirely by you; rather, the intent is to
|
||||
exercise the right to control the distribution of derivative or
|
||||
collective works based on the Program.
|
||||
|
||||
<P>
|
||||
In addition, mere aggregation of another work not based on the Program
|
||||
with the Program (or with a work based on the Program) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
<P>
|
||||
3. You may copy and distribute the Program (or a work based on it,
|
||||
under Section 2) in object code or executable form under the terms of
|
||||
Sections 1 and 2 above provided that you also do one of the following:
|
||||
|
||||
<blockquote>
|
||||
a) Accompany it with the complete corresponding machine-readable
|
||||
source code, which must be distributed under the terms of Sections
|
||||
1 and 2 above on a medium customarily used for software interchange; or,
|
||||
<P>
|
||||
b) Accompany it with a written offer, valid for at least three
|
||||
years, to give any third party, for a charge no more than your
|
||||
cost of physically performing source distribution, a complete
|
||||
machine-readable copy of the corresponding source code, to be
|
||||
distributed under the terms of Sections 1 and 2 above on a medium
|
||||
customarily used for software interchange; or,
|
||||
<P>
|
||||
c) Accompany it with the information you received as to the offer
|
||||
to distribute corresponding source code. (This alternative is
|
||||
allowed only for noncommercial distribution and only if you
|
||||
received the program in object code or executable form with such
|
||||
an offer, in accord with Subsection b above.)
|
||||
</blockquote>
|
||||
|
||||
<P>
|
||||
The source code for a work means the preferred form of the work for
|
||||
making modifications to it. For an executable work, complete source
|
||||
code means all the source code for all modules it contains, plus any
|
||||
associated interface definition files, plus the scripts used to
|
||||
control compilation and installation of the executable. However, as a
|
||||
special exception, the source code distributed need not include
|
||||
anything that is normally distributed (in either source or binary
|
||||
form) with the major components (compiler, kernel, and so on) of the
|
||||
operating system on which the executable runs, unless that component
|
||||
itself accompanies the executable.
|
||||
|
||||
<P>
|
||||
If distribution of executable or object code is made by offering
|
||||
access to copy from a designated place, then offering equivalent
|
||||
access to copy the source code from the same place counts as
|
||||
distribution of the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
</P>
|
||||
|
||||
<HR>
|
||||
4. You may not copy, modify, sublicense, or distribute the Program
|
||||
except as expressly provided under this License. Any attempt
|
||||
otherwise to copy, modify, sublicense or distribute the Program is
|
||||
void, and will automatically terminate your rights under this License.
|
||||
However, parties who have received copies, or rights, from you under
|
||||
this License will not have their licenses terminated so long as such
|
||||
parties remain in full compliance.
|
||||
|
||||
<P>
|
||||
5. You are not required to accept this License, since you have not
|
||||
signed it. However, nothing else grants you permission to modify or
|
||||
distribute the Program or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Program (or any work based on the
|
||||
Program), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Program or works based on it.
|
||||
|
||||
<P>
|
||||
6. Each time you redistribute the Program (or any work based on the
|
||||
Program), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute or modify the Program subject to
|
||||
these terms and conditions. You may not impose any further
|
||||
restrictions on the recipients' exercise of the rights granted herein.
|
||||
You are not responsible for enforcing compliance by third parties to
|
||||
this License.
|
||||
|
||||
<P>
|
||||
7. If, as a consequence of a court judgment or allegation of patent
|
||||
infringement or for any other reason (not limited to patent issues),
|
||||
conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot
|
||||
distribute so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you
|
||||
may not distribute the Program at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Program by
|
||||
all those who receive copies directly or indirectly through you, then
|
||||
the only way you could satisfy both it and this License would be to
|
||||
refrain entirely from distribution of the Program.
|
||||
|
||||
<P>
|
||||
If any portion of this section is held invalid or unenforceable under
|
||||
any particular circumstance, the balance of the section is intended to
|
||||
apply and the section as a whole is intended to apply in other
|
||||
circumstances.
|
||||
|
||||
<P>
|
||||
It is not the purpose of this section to induce you to infringe any
|
||||
patents or other property right claims or to contest validity of any
|
||||
such claims; this section has the sole purpose of protecting the
|
||||
integrity of the free software distribution system, which is
|
||||
implemented by public license practices. Many people have made
|
||||
generous contributions to the wide range of software distributed
|
||||
through that system in reliance on consistent application of that
|
||||
system; it is up to the author/donor to decide if he or she is willing
|
||||
to distribute software through any other system and a licensee cannot
|
||||
impose that choice.
|
||||
</P>
|
||||
|
||||
<HR>
|
||||
This section is intended to make thoroughly clear what is believed to
|
||||
be a consequence of the rest of this License.
|
||||
|
||||
<P>
|
||||
8. If the distribution and/or use of the Program is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Program under this License
|
||||
may add an explicit geographical distribution limitation excluding
|
||||
those countries, so that distribution is permitted only in or among
|
||||
countries not thus excluded. In such case, this License incorporates
|
||||
the limitation as if written in the body of this License.
|
||||
|
||||
<P>
|
||||
9. The Free Software Foundation may publish revised and/or new versions
|
||||
of the General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to
|
||||
address new problems or concerns.
|
||||
|
||||
<P>
|
||||
Each version is given a distinguishing version number. If the Program
|
||||
specifies a version number of this License which applies to it and "any
|
||||
later version", you have the option of following the terms and conditions
|
||||
either of that version or of any later version published by the Free
|
||||
Software Foundation. If the Program does not specify a version number of
|
||||
this License, you may choose any version ever published by the Free Software
|
||||
Foundation.
|
||||
|
||||
<P>
|
||||
10. If you wish to incorporate parts of the Program into other free
|
||||
programs whose distribution conditions are different, write to the author
|
||||
to ask for permission. For software which is copyrighted by the Free
|
||||
Software Foundation, write to the Free Software Foundation; we sometimes
|
||||
make exceptions for this. Our decision will be guided by the two goals
|
||||
of preserving the free status of all derivatives of our free software and
|
||||
of promoting the sharing and reuse of software generally.
|
||||
<P>
|
||||
|
||||
<h3><a name="SEC003">NO WARRANTY</a></h3>
|
||||
|
||||
<P>
|
||||
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
|
||||
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
|
||||
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
|
||||
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
|
||||
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
||||
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
||||
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
|
||||
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
|
||||
REPAIR OR CORRECTION.
|
||||
|
||||
<P>
|
||||
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
||||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
|
||||
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
|
||||
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
|
||||
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
|
||||
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
|
||||
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
|
||||
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGES.
|
||||
|
||||
<h3>END OF TERMS AND CONDITIONS</h3>
|
||||
|
||||
<hr>
|
||||
</body>
|
||||
</html>
|
||||
372
Docs/fr/xacc-groups.html
Normal file
372
Docs/fr/xacc-groups.html
Normal file
@ -0,0 +1,372 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Chart of Accounts and Account Numbering</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Tableau de comptes</H1>
|
||||
Typiquement les comptes sont arrangés comme un arbre, dans une forme
|
||||
hiérarchique. Le tronc principal représente les catégories
|
||||
ou groupes en entier, tandis que les feuillles de l'arbre contiennent des
|
||||
comptes bancaires individuels ou des catégories de dépenses.
|
||||
Quand un rapport sommaire est demandé, typiquement seulement les
|
||||
branches principales sont montrés dans le rapport, pas chacun des
|
||||
comptes individuels. Par example, un tableau de comptes devrait ressembler
|
||||
à ce
|
||||
<BR>qui suit:
|
||||
<PRE> 300 Dépenses
|
||||
|
|
||||
+--310 Dépenses en cours
|
||||
| |
|
||||
| +--311 Bière
|
||||
| |
|
||||
| +--312 Cable
|
||||
|
|
||||
+--320 Dépenses commerciales
|
||||
| |
|
||||
| +--321 Disquettes 8 pouces
|
||||
| |
|
||||
: :</PRE>
|
||||
Noter que les comptes sont codés: quand un rapport est généré,
|
||||
l'ordre de tri est déterminé entièrement par la numérotation.
|
||||
Par tradition et pratique habituelle, les comptes qui ne sont des comptes
|
||||
feuilles ont un nombre qui tends vers zéro; chaque niveau supérieur
|
||||
a un plus zero dans le code du compte.
|
||||
<P>Quand vous faites une <A HREF="xacc-accwin.html">création d'un
|
||||
nouveau compte</A>, GnuCash offre une possibilité de deviner à
|
||||
quoi il pense que le code du compte devrait être; vous êtes
|
||||
libre de le changer. GnuCash ne prévient pas la duplication de numérotation,
|
||||
bien que vous êtes encouragés à l'éviter. Les
|
||||
codes de compte sont traités comme des numéros, base-36:
|
||||
ainsi, s'il n'y a plus de numéros, vous pouvez utiliser les lettres,
|
||||
de a jusqu'à z.
|
||||
<H2>
|
||||
Un gros example</H2>
|
||||
Un tableau "typique" de comptes est montré ci-dessous. C'est une
|
||||
combinaison de quelques comptes commerciaux et personnels typiques.
|
||||
<UL>
|
||||
<LI>
|
||||
Actifs</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Argent à portée de main / Liquidités</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Compte chèques ou courant</LI>
|
||||
|
||||
<LI>
|
||||
Compte de marché monétaire</LI>
|
||||
|
||||
<LI>
|
||||
Certificat de dépôt</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Actifs fixes / Immobilisations</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Meubles</LI>
|
||||
|
||||
<LI>
|
||||
Ordinateurs</LI>
|
||||
|
||||
<LI>
|
||||
Bijoux, articles de collection</LI>
|
||||
|
||||
<LI>
|
||||
Outils, machines</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Investissements</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Actions</LI>
|
||||
|
||||
<LI>
|
||||
Obligations</LI>
|
||||
|
||||
<LI>
|
||||
Sociétés d'investissements (n.d.t.: SICAV, FCP, OPCVM, SCPI
|
||||
en france)</LI>
|
||||
|
||||
<LI>
|
||||
Biens immobiliers</LI>
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Passifs</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Impôt/Taxes</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Sécurité sociale</LI>
|
||||
|
||||
<LI>
|
||||
Impôt sur le revenu</LI>
|
||||
|
||||
<LI>
|
||||
Taxe d'habitation</LI>
|
||||
|
||||
<LI>
|
||||
Impôt foncier</LI>
|
||||
|
||||
<LI>
|
||||
Vignette automobile</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Carte de crédit et carte a débit différé</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Eurocard/MasterCard</LI>
|
||||
|
||||
<LI>
|
||||
Visa</LI>
|
||||
|
||||
<LI>
|
||||
American Express</LI>
|
||||
|
||||
<LI>
|
||||
Diner's Club</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Emprunts</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Obligations(bourse)</LI>
|
||||
|
||||
<LI>
|
||||
Prêt étudiant</LI>
|
||||
|
||||
<LI>
|
||||
Prêt personel d'oncle Jean</LI>
|
||||
|
||||
<LI>
|
||||
Prêt immobilier</LI>
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Capitaux propres</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Reste de profits</LI>
|
||||
|
||||
<LI>
|
||||
Primes et profits de l'année en cours</LI>
|
||||
|
||||
<LI>
|
||||
Règlement d'une demande (justice)</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Revenus</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Revenus d'intérêts</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Intérêt du compte bancaire (compte rémunéré)</LI>
|
||||
|
||||
<LI>
|
||||
Certificat de depôt</LI>
|
||||
|
||||
<LI>
|
||||
Interêts d'obligations</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Dividendes</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Actions</LI>
|
||||
|
||||
<LI>
|
||||
Sociétés d'investissements (n.d.t.: SICAV, FCP, OPCVM, SCPI
|
||||
en france)</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Consultant</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
ABC Design</LI>
|
||||
|
||||
<LI>
|
||||
PQR Infomatics</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Salaire</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Mon travail de jour</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Commissions</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Royalties</LI>
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Dépenses</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Loyer and Sevices</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Loyer</LI>
|
||||
|
||||
<LI>
|
||||
Intérêts sur le loyer en retard</LI>
|
||||
|
||||
<LI>
|
||||
Electricité</LI>
|
||||
|
||||
<LI>
|
||||
Gaz</LI>
|
||||
|
||||
<LI>
|
||||
Téléphone</LI>
|
||||
|
||||
<LI>
|
||||
Internet</LI>
|
||||
|
||||
<LI>
|
||||
TV par cable</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Dépenses de bureau</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Comptabilité</LI>
|
||||
|
||||
<LI>
|
||||
Avocat (pour les USA)</LI>
|
||||
|
||||
<LI>
|
||||
Logiciels</LI>
|
||||
|
||||
<LI>
|
||||
Poste</LI>
|
||||
|
||||
<LI>
|
||||
Frais bancaires</LI>
|
||||
|
||||
<LI>
|
||||
Frais de cartes de crédit</LI>
|
||||
|
||||
<LI>
|
||||
Toner, Papier, Paper Clips</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Dépenses automobiles</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Carburant</LI>
|
||||
|
||||
<LI>
|
||||
Assurance</LI>
|
||||
|
||||
<LI>
|
||||
Réparation</LI>
|
||||
|
||||
<LI>
|
||||
Location</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Taxes</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Sécurité sociale</LI>
|
||||
|
||||
<LI>
|
||||
Assurance chomage</LI>
|
||||
|
||||
<LI>
|
||||
Amende des impôts</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Salaires et primes</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Consultant</LI>
|
||||
|
||||
<LI>
|
||||
Primes</LI>
|
||||
|
||||
<LI>
|
||||
Assurance santé</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Voyage</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Avion</LI>
|
||||
|
||||
<LI>
|
||||
Hotel</LI>
|
||||
|
||||
<LI>
|
||||
Repas</LI>
|
||||
|
||||
<LI>
|
||||
Auto</LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
Marketing/Mercatique</LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
Publicité</LI>
|
||||
|
||||
<LI>
|
||||
Salon professionnel / Foire commerciale</LI>
|
||||
|
||||
<LI>
|
||||
Donations/Gadgets</LI>
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
81
Docs/fr/xacc-main.html
Normal file
81
Docs/fr/xacc-main.html
Normal file
@ -0,0 +1,81 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Aide</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
<!--This file created 09:45 21/12/98 -->
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
Pour l'aide sur un sujet en particulier:
|
||||
<UL>
|
||||
<LI>
|
||||
<A HREF="xacc-about.html">A propos de GnuCash</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-acctypes.html">Types de compte</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-apar.html">Dettes fourniseurs et crédit fournisseurs</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-quicken.html">Catégories</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-groups.html">Tableau de comptes</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-accwin.html">Creation d'un nouveau compte</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-date.html">L'entrée de date</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-currency.html">Monnaies étrangères</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="bofa-mym.html">Importation des fichiers MYM (Managing Your Money)</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-quicken.html">Guide de l'utilisateur de Quicken (TM)</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-gpl.html">Licence</A></LI>
|
||||
|
||||
<UL>
|
||||
<LI>
|
||||
<A HREF="xacc-gpl.html#SEC003">Garantie</A></LI>
|
||||
</UL>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-mainwin.html">La fenêtre principale</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-print.html">Impression et serveur web</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-recnwin.html">La fenêtre de rapprochement</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-regwin.html">La fenêtre registre (ou d'enregistrement)</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-reports.html">Rapports</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-ticker.html">Codes des titres</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-double.html">Utilisation de la double entrée</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-expense.html">Utilisation des comptes de Revenus/Dépenses</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="xacc-y2k.html">Compatibilité an 2000 de GnuCash</A></LI>
|
||||
</UL>
|
||||
|
||||
<HR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
53
Docs/fr/xacc-mainwin.html
Normal file
53
Docs/fr/xacc-mainwin.html
Normal file
@ -0,0 +1,53 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Fenêtre principale</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>CE FICHIER EST PRESQUE VIDE</H1>
|
||||
|
||||
<P>C'est la fenêtre principale du compte . Controle des comptes
|
||||
depuis ici . Ajouter plus de documentation.</P>
|
||||
|
||||
<P>Ci dessous se trouve une image de la fenêtre principale ,
|
||||
avec seulement les comptes principaux affichés . Noté
|
||||
comment "ABC Bank" a été sélectionnée par
|
||||
surbrillance . Pour afficher les détails des comptes , cliquez
|
||||
sur les flèches sur le coté gauche .</P>
|
||||
|
||||
<P><IMG SRC="contract.gif" WIDTH=584 HEIGHT=279 X-SAS-UseImageWidth
|
||||
X-SAS-UseImageHeight ALIGN=bottom><BR>
|
||||
|
||||
</P>
|
||||
|
||||
<P>Ci-dessous se trouve la fenêtre principale , avec les
|
||||
détails des comptes affichés.</P>
|
||||
|
||||
<P><BR>
|
||||
|
||||
<IMG SRC="expand.gif" WIDTH=584 HEIGHT=279 X-SAS-UseImageWidth
|
||||
X-SAS-UseImageHeight ALIGN=bottom><BR>
|
||||
|
||||
</P>
|
||||
|
||||
<P>
|
||||
<HR>
|
||||
L'élément du menu "Ouvrir Sous-comptes" est
|
||||
intérresant seulement si vous choisissez un compte avec des
|
||||
sous-comptes (comptes détaillées). Les comptes avec des
|
||||
sous-comptes aura toujours des flèches sur sa gauche . En
|
||||
choisissant l'élément du menu "Ouvrir Sous-comptes" ,
|
||||
une fenêtre de registre général (ou
|
||||
d'enregistrement est ouverte , qui affiche toutes les transactions
|
||||
pour le compte principal et le compte de détail. Noté
|
||||
que la fenêtre de registre général est plus
|
||||
compliquée et dificile à utiliser que les registres de
|
||||
comptes individuels. La fenêtre du registre
|
||||
général permets une vision plus comprehensible des
|
||||
comptes dans un espace plus petit. A cause de sa complexité
|
||||
accrue , son utilisation est recommandé seulement pour les
|
||||
experts en comptabilité.</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
28
Docs/fr/xacc-print.html
Normal file
28
Docs/fr/xacc-print.html
Normal file
@ -0,0 +1,28 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Printing and Web Serving</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Impression et serveur web</H1>
|
||||
Actuellement, GnuCash ne supporte d'aucune sorte une sortie vers l'imprimante.
|
||||
Pourtant, vous pouvez créer une sortie d'impression des éléments
|
||||
de la fenêtre registre/d'enregistrement en ouvrant une fenêtre
|
||||
registre et en sélectionnant "Imprimer ... Vers fichier" depuis
|
||||
le menu "Fichier".
|
||||
<P>Suivant la dernière tendance à la mode, GnuCash peut aussi
|
||||
agir comme un serveur web sans valeur! Depuis une fenêtre registre
|
||||
ouverte, selectionnez "Imprimer ... Vers WWW" depuis le menu "Fichier".
|
||||
Alors pointer votre navigateur à <TT>http://localhost:1080/</TT>
|
||||
ou <TT>http://mon nom de machine.com:1080/et vous verrez votre fenêtre
|
||||
registre</TT>. Mais, souvenez-vous, nous disons "sans valeur": pour voir
|
||||
la page de nouveau, vous devrez reprendre la procédure précédente
|
||||
de nouveau.
|
||||
<BR>
|
||||
<HR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
64
Docs/fr/xacc-quicken.html
Normal file
64
Docs/fr/xacc-quicken.html
Normal file
@ -0,0 +1,64 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Guide de l'utilisateur de Quicken</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Guide de l'utilisateur de Quicken (TM)</H1>
|
||||
Tous les systèmes de comptabilité n'utilise pas les mêmes
|
||||
mots pour les mêmes concepts . Ci-dessous se trouve quelques notes
|
||||
pour les utilisateurs habitués des produits Quicken .
|
||||
<H2>
|
||||
Catégories</H2>
|
||||
Ce que Quicken appelle "Catégories" sont juste réellement
|
||||
des <A HREF="xacc-expense.html">comptes Revenus/Dépenses</A> . Ainsi,
|
||||
si vous utilisez les spécifications d'une catégorie dans
|
||||
Quicken, créez juste un compte revenus/dépenses du même
|
||||
nom dans X-Accountant, et utilisez le comme une catégorie.
|
||||
<H2>
|
||||
Importation des fichiers QIF de Quicken</H2>
|
||||
X-Accountant supporte l'importation des Quicken Import Fichiers (QIF).
|
||||
(Note: Seulement les fichiers QIF de la version 3.0 de Quicken ont été
|
||||
testé). Dû à la curieuse nature de QIF, s'il vous plaît
|
||||
liserz cette section prudemment, ou vous serez peut-être déçu
|
||||
avec les résultats.
|
||||
<P>Pour créer un fichier QIF avec Quicken , démarrez Quicken
|
||||
(oui, il fonctionne avec Wine, et probablement avec Wabi aussi), choisissez
|
||||
le menu "Fichier" et sélectionnez l'entrée du menu "Exporter..."
|
||||
. Sous la version 3.0 de Quicken , vous pouvez seulement exporter un compte
|
||||
à la fois , et ainsi , l'exportation démontrera être
|
||||
un processus pénible . Quand vous exportez , noté que il
|
||||
y a une séries de boites de vérification marqués "Transactions",
|
||||
"Liste de Comptes ", "Liste de Catégories", etc. Pour de meilleurs
|
||||
résultats, vous devrez etre sûr d'avoir ces trois dernières
|
||||
qui soit vérifiés. Si vous ne vérifiez *pas* la boite
|
||||
"Listes de Comptes ", alors le nom de votre compte sera perdu.
|
||||
<P>Pour importer un fichier QIF de Quicken, choisissez le menu "Fichier"et
|
||||
sélectionnez l'entrée "Importer QIF". Le fichier importé
|
||||
sera fusionné avec quel que soit les autres données que vous
|
||||
avez actuellement dans X-Accountant. Cette fusion permet aux multiples
|
||||
comptes Quicken d'être importés et fusionnés dans un
|
||||
groupe de compte . Notez que durant la fusion, une analyse est effectuée
|
||||
pour les transactions dupliquées , et les doubles sont enlevés.
|
||||
Une transaction dupliquée est une oû la date, la description
|
||||
(bénéficiaire), mémo, quantitée, prix de la
|
||||
part , et les comptes ou catégories débités/crédités
|
||||
se retrouve exactement. Ainsi, la fusion devrait être sûr à
|
||||
moins que vous ayez de multiples transactions à la même date,
|
||||
au même compte , pour le même montant , avec la même
|
||||
description et mémo.
|
||||
<P>Notez que quand la "Liste des Comptes " et la "Liste de Catégories"
|
||||
est exporté depuis Quicken, <B>tous</B> les comptes et catégories
|
||||
seront exportés même si, ils sont vides , et ne contiennent
|
||||
pas transactions. Quand ceux-ci sont importés, ils appazraitront
|
||||
comme des comptes avec un solde de zero. Si vous n'avez pas besoin ou n'utilisez
|
||||
pas ces comptes , supprimez les . Une amélioration future de X-Accountant
|
||||
vous permettra de les supprimer en-masse, ou de les rendre invisible sans
|
||||
les supprimer.
|
||||
</BODY>
|
||||
</HTML>
|
||||
50
Docs/fr/xacc-recnwin.html
Normal file
50
Docs/fr/xacc-recnwin.html
Normal file
@ -0,0 +1,50 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Fenêtre de rapprochement</TITLE>
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Fenêtre de rapprochement</H1>
|
||||
La fenêtre de rapprochement est utilisé pour rapprocher les
|
||||
transactions pointés depuis un relevé bancaire . Entrez le
|
||||
montant en francs depuis votre dernier relevé bancaire dans la fenêtre
|
||||
, et alors cliquez sur OK. La fenêtre montrera alors toutes les transactions
|
||||
non pointées depuis votre dernier relevé bancaire . Cette
|
||||
fenêtre de rapprochement ressemble à celà:
|
||||
<BR>
|
||||
<P><IMG SRC="recnwin.gif" X-SAS-UseImageWidth X-SAS-UseImageHeight HEIGHT=342 WIDTH=633>
|
||||
<P>La fenêtre de rapprochement est pour le rapprochement des enregistrements
|
||||
des utilisateurs à la fin du mois quand le relevé bancaire
|
||||
arrive. Par example, si vous écrivez un chèque pour quelqu'un
|
||||
, entrez la transaction. Quand vous savez que que le chèque a été
|
||||
pointé (débité de votre compte) , vous pouvez cliquez
|
||||
le champ entre les champs de description et de paiement , et le changer
|
||||
depuis 'n' vers 'c', indiquant que la transaction a été pointée
|
||||
A la fin du mois , ouvrez la fenêtre de rapprochement , et xacc vous
|
||||
suggèrera /soufflera l'entrée du solde final à partir
|
||||
du relevé bancaire . Alors la fenêtre de rapprochement apparaitra
|
||||
, et vous verrez une colonne de crédit et de débit qui listera
|
||||
toutes les transactions non rapprochés . Vous pouvez alors pointer
|
||||
les transactions qui apparaissent dans le relevé bancaire , et vérifier
|
||||
que le montant des champs soit correct. En bas de la fenêtre se trouve
|
||||
un champ différence , qui devrait être de 0.00F quand vous
|
||||
avez fait le rapprochement . Si'il ne l'est pas alors vous avez laisser
|
||||
échapper une transaction, ou un des montants est erroné (ou
|
||||
faux). Quand vous cliquez sur "Ok", alors le 'n' ou 'c' dans les transactions
|
||||
qui ont été pointé se changera en un 'y'. Quand vous
|
||||
changez quelque chose dans une transaction de rapprochement , une boite
|
||||
de dialogue de verification devrait apparaitre , mais celà ne semble
|
||||
pas être encore un évènement. Aussi , le total "pointé"
|
||||
en bas semble afficher F0.00 sans se soucier de ces transactions qui ont
|
||||
été pointés ou rapprochés . Le total"pointé"
|
||||
devrait afficher le total de seulement les transactions qui ont été
|
||||
pointés ('c') ou rapprochés ('y').
|
||||
<P>
|
||||
<HR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
97
Docs/fr/xacc-regwin.html
Normal file
97
Docs/fr/xacc-regwin.html
Normal file
@ -0,0 +1,97 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Fenêtre registre</TITLE>
|
||||
<X-SAS-WINDOW TOP=0 BOTTOM=481 LEFT=0 RIGHT=786>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
La fenêtre registre</H1>
|
||||
C'est la fenêtre du Registre/Grand Livre(ou d'enregistrement ). Entrez
|
||||
les transactions ici . Ajouter plus de documentation.
|
||||
<P>Ci-dessus se trouve à quoi la fenêtre registre devrait
|
||||
ressembler :
|
||||
<P><IMG SRC="regwin-single.gif" HEIGHT=372 WIDTH=683>
|
||||
<BR>
|
||||
<P><IMG SRC="regwin-double.gif" HEIGHT=417 WIDTH=800>
|
||||
<BR>
|
||||
<P><IMG SRC="regwin-multi.gif" HEIGHT=417 WIDTH=800>
|
||||
<HR>
|
||||
<H2>
|
||||
Rapprochement</H2>
|
||||
En bas de la fenêtre du compte, il y a deux soldes en cours, le solde
|
||||
"pointé et rapproché", et le solde "total"... le solde "pointé
|
||||
et rapproché " devrait correspondre à la totalité
|
||||
de l'argent que la banque pense que vous ayez sur votre compte, et le solde
|
||||
"total" inclut les transactions en cours de règlement.
|
||||
<P>Le rapprochement peut être fait dans la <A HREF="xacc-recnwin.html">fenêtre
|
||||
de rapprochement</A>
|
||||
<P>(pas encore implementé) Les transactions marquées avec
|
||||
un 'y' , et ne peuvent pas être éditées sans changer
|
||||
en premier ce drapeau. C'est parce que une transaction de rapprochement
|
||||
devrait être capable de se souvenir de tout chose qui a été
|
||||
vérifiée, et donc correcte. Changer ainsi une transaction
|
||||
devrait être difficile: nous voulons éviter les erreurs accidentelles.
|
||||
<P>(pas encore implementé) Les transactions marquées avec
|
||||
un 'f' sont gelées, et ne peuvent pas être éditées
|
||||
dans n'importe quelle circonstances. Celles-ci ont été gelées
|
||||
pendant une période du compte. C'est à dire, les livres ont
|
||||
été fermés pendant cette période; ils ne peuvent
|
||||
plus être réouvert pour être édités.
|
||||
<P>
|
||||
<HR>
|
||||
<H2>
|
||||
Portefeuilles d'actions</H2>
|
||||
Vous pouvez faire des transactions d'actions soit depuis une fenêtre
|
||||
avec une seule valeur(nom) d'actions , ou soit depuis une fenêtre
|
||||
de vue de porte-feuille , montré ci-dessous.
|
||||
<P><IMG SRC="foliowin.gif" X-SAS-UseImageWidth X-SAS-UseImageHeight HEIGHT=348 WIDTH=845 ALIGN=BOTTOM>
|
||||
<P><IMG SRC="foliowin-single.gif" HEIGHT=372 WIDTH=881>
|
||||
<P>Le registre du porte-feuille peut intimidé un peu au premier
|
||||
abord . Si vous avez de la peine à le comprendre , alors tournez
|
||||
vous vers la création de comptes qui contiennent une seule valeur
|
||||
d'action. Quelques points importants à se souvenir à propos
|
||||
de la fenêtre du porte-feuille:
|
||||
<UL>
|
||||
<LI>
|
||||
Elle montre toutes les actions de votre porte-feuille , pas juste quelques-une
|
||||
. Les montants des titres montrés sont pour chaque action en particulier
|
||||
.</LI>
|
||||
|
||||
<LI>
|
||||
Notez qu'elle utilise un affichage sur deux lignes . Les comptes débités
|
||||
et les montants débités sont sur la ligne supérieure
|
||||
, et les montants et comptes crédités sont sur la ligne inférieure.</LI>
|
||||
|
||||
<LI>
|
||||
Si vous achetez ou vendez une action avec de de l'argent d'un compte de
|
||||
courtage , le solde total ne changera pas , tant que la valeur de l'action
|
||||
égale le montant de l'argent échangé.</LI>
|
||||
|
||||
<LI>
|
||||
Si vous achetez ou vendez une action avec de de l'argent d'un compte de
|
||||
courtage , la valeur de la transaction apparaitra deux fois , une fois
|
||||
en rouge , et une fois en noir . Si les titres sont achetés , le
|
||||
montant de l'argent débité d'un compte de courtage sera en
|
||||
rouge, et la valeur des titres en noir . Si les titres sont vendus , alors
|
||||
la valeur des titres est en rouge , et l'argent crédité dans
|
||||
le compte de courtage en noir .</LI>
|
||||
|
||||
<LI>
|
||||
Si vous avez de la peine à indiquer un titre acheté/vendu
|
||||
dans le registre du porte-feuille , alors soyez sûr que les comptes
|
||||
"Transfert depuis" et "Transfert vers " sont dans le bon ordre . Un transfert
|
||||
depuis un compte d'actions est toujours interprété comme
|
||||
une vente, même si vous entrez la donnée comme un achat .
|
||||
Le contraire est aussi vrai .</LI>
|
||||
|
||||
<LI>
|
||||
Un jour X-Accountant sera amélioré avec une fenêtre
|
||||
simplifiée du registre du porte-feuille .</LI>
|
||||
</UL>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
35
Docs/fr/xacc-reports.html
Normal file
35
Docs/fr/xacc-reports.html
Normal file
@ -0,0 +1,35 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Reports</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Rapports</H1>
|
||||
Il ya deux types de rapports: un <B>Bilan </B> et un <B>Compte-rendu
|
||||
de profits et pertes</B>.
|
||||
<P>Un bilan montre Avoirs, Dettes et Capitaux propres. La sommes de tous
|
||||
les possessions devrait être égale à la somme des dettes
|
||||
et capitaux propres.
|
||||
<P>Un compte-rendu de profits et pertes montre les revenus et dépenses.
|
||||
La somme de tous les revenus moins toutes les dépenses est un profit
|
||||
ou une perte.
|
||||
<P>Le changement des capitaux propes de jour en jour (année en année)
|
||||
devrait être égal à ce profit ou perte du jour (année).
|
||||
<UL>
|
||||
<LI>
|
||||
<A HREF="report-baln.phtml">Cliquez ici pour voir le bilan</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="report-pnl.phtml">Cliquez ici pour voir le compte-rendu des pertes
|
||||
et profits</A></LI>
|
||||
|
||||
<LI>
|
||||
<A HREF="report-folio.phtml">Montre la valeur du portefeuille d'actions</A></LI>
|
||||
</UL>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
66
Docs/fr/xacc-ticker.html
Normal file
66
Docs/fr/xacc-ticker.html
Normal file
@ -0,0 +1,66 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Stock Ticker</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Cours des actions et codes des titres</H1>
|
||||
GnuCash actuellement fournit des possibilités de cotation d'actions
|
||||
automatisé. Si un compte est correctement configuré, et l'ordinateur
|
||||
hôte est connecté sur internet, l'exécutable <TT>gnc-prices</TT>
|
||||
peut être utilisé pour chargerv les cotations des cours d'actions
|
||||
ou FCP et SICAV à partir de divers sites web directement dans GnuCash.
|
||||
<P>Pour utiliser cette fonctionnalité, ce qui suit doit être
|
||||
fait:
|
||||
<UL>
|
||||
<LI>
|
||||
Créer un compte et marquer le comme étant du type "FCP/SICAV"
|
||||
ou "Actions".</LI>
|
||||
|
||||
<LI>
|
||||
Entrer un code de titre valide (ndt : code SICOVAM en france) dans le champ
|
||||
marqué "Valeur:"</LI>
|
||||
|
||||
<LI>
|
||||
Sélectionner une source de cotations depuis le menu déroulant.
|
||||
Actuellement les sources de cotations supportés incluent <B>Yahoo</B>,
|
||||
<B>Fidelity Investments</B>, <B>T. Rowe Price</B> et le <B>Vanguard Group</B>.
|
||||
Noter que Yahoo fournira le cours des cotations pour la plupart des fonds
|
||||
communs , incluant Fidelity, T.Rowe Price and Vanguard, et les cours/NAV
|
||||
cotés devrait être identique à ceux sur les sites
|
||||
sources.</LI>
|
||||
</UL>
|
||||
Un exemple d'image est montré ci-dessous:
|
||||
<P><IMG SRC="ticker-a.gif" HEIGHT=347 WIDTH=405>
|
||||
<P>Pour mettre à jour les cours stockés dans un fichier de
|
||||
compte de gnucash, lancez en ligne de commande <TT>gnc-price</TT>, en specifiant
|
||||
le nom du fichier; par exemple:
|
||||
<PRE> gnc-prices myaccts.xac</PRE>
|
||||
En lançant cette commande, elle affichera divers messages de diagnostic
|
||||
vers l'écran tandis qu'elle chargera les données. Elle fonctionnera
|
||||
seulement quand l'ordinateur hôte est connecté à internet.
|
||||
Elle fonctionnera si l'hôte est derrière un parefeu/firewall
|
||||
de style masqué. Elle ne fonctionne pas actuellement depuis derrière
|
||||
un proxy ou des parefeu de style socks. La commande peut être lancée
|
||||
plusieurs fois dans une journée; pourtant, elle mettra les
|
||||
comptes à jour au maximum une fois avec la plupart des données
|
||||
de cours de la journée échangé dernièrement.
|
||||
Ainsi, si gnc-prices est lancé le vendredi, samedi, dimanche
|
||||
et lundi, seulement deux chargement de cours seront effectué:
|
||||
un contenant les données du vendredi, et un contenant les données
|
||||
du lundi, tandis que celui du samedi et dimanche lancé retrouvera
|
||||
seulement les cours de cloture du vendredi. Pour empêcher gnc-prices
|
||||
de mettre à jour un compte, tandis que vous lui permettez de mettre
|
||||
à jour un autre compte, simplement marqué les données
|
||||
source pour ce compte comme "(aucun)". Vous pouvez le faire depuis la fenêtre
|
||||
"Afficher un compte".
|
||||
<P>Après avoir lancé gnc-prices pendant quelques jours, vos
|
||||
comptes commenceront à ressembler à ce qui suit:
|
||||
<P><IMG SRC="ticker-b.gif" HEIGHT=372 WIDTH=881>
|
||||
<HR>
|
||||
</BODY>
|
||||
</HTML>
|
||||
28
Docs/fr/xacc-y2k.html
Normal file
28
Docs/fr/xacc-y2k.html
Normal file
@ -0,0 +1,28 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>GnuCash Y2K Readiness</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>
|
||||
Compatibilité an 2000 de GnuCash</H1>
|
||||
La version 1.1.25 de Gnucash et suivantes stocke toutes les dates en secondes
|
||||
et nanosecondes, où les secondes sont stockés comme un entier
|
||||
signé de 64-bit. Celà devait suffire pour stocker les dates
|
||||
du passé distant aussi bien que le futur distant, aussi longtemps
|
||||
qu'il y aura moins plusieurs douzaines d'heures dans l'âge de l'univers.
|
||||
<P>Le format de fichier pour la version 1.1.25 et suivantes stocke les
|
||||
dates de la manière cité ci-dessus.
|
||||
<P>Quelques routines internes utilisent le type <TT>time_t</TT> pour exprimer
|
||||
les secondes. Noter que sur la plupart des OS, c'est une longueur de 32-bit,
|
||||
et elle est limité à l'ère Unix (Déc 1901 à
|
||||
Jan 2038).
|
||||
<P>Les fichiers de sauvegarde et log sont estampillé temporellement
|
||||
en utilisant la routine standard Unix <TT>ctime()</TT>, qui prend comme
|
||||
argument <TT>time_t</TT>. Ainsi, le mécanisme de sauvegarde et de
|
||||
log pourrait éprouver des troubles en 2038.
|
||||
</BODY>
|
||||
</HTML>
|
||||
26
Makefile.in
26
Makefile.in
@ -188,31 +188,21 @@ install:
|
||||
$(INSTALL_DATA) data/*.xac ${GNC_SHAREDIR}/data
|
||||
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/En
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/Fr
|
||||
$(INSTALL_DATA) Docs/*.html ${GNC_SHAREDIR}/Docs
|
||||
$(INSTALL_DATA) Docs/En/*.html ${GNC_SHAREDIR}/Docs/En
|
||||
$(INSTALL_DATA) Docs/Fr/*.html ${GNC_SHAREDIR}/Docs/Fr
|
||||
# XXX hack alert -- should fix scheme paths to find language directories.
|
||||
$(INSTALL_DATA) Docs/En/*.html ${GNC_SHAREDIR}/Docs
|
||||
# $(INSTALL_DATA) Docs/*.phtml ${GNC_SHAREDIR}/Docs
|
||||
$(INSTALL_DATA) Docs/*.gif ${GNC_SHAREDIR}/Docs
|
||||
# $(INSTALL_DATA) Docs/*.jpg ${GNC_SHAREDIR}/Docs
|
||||
# $(INSTALL_DATA) Docs/*.xpm ${GNC_SHAREDIR}/Docs
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/C
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/C/pix
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/fr
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/fr/pix
|
||||
$(INSTALL_DATA) Docs/C/*.html ${GNC_SHAREDIR}/Docs/C
|
||||
$(INSTALL_DATA) Docs/fr/*.html ${GNC_SHAREDIR}/Docs/fr
|
||||
$(INSTALL_DATA) Docs/C/pix/*.* ${GNC_SHAREDIR}/Docs/C/pix
|
||||
$(INSTALL_DATA) Docs/fr/pix/*.* ${GNC_SHAREDIR}/Docs/fr/pix
|
||||
$(INSTALL_DATA) Docs/*.css ${GNC_SHAREDIR}/Docs
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/images
|
||||
# $(INSTALL_DATA) Docs/logos/*.* ${GNC_SHAREDIR}/Docs/images
|
||||
@mkdir -p ${GNC_SHAREDIR}/Docs/logos
|
||||
$(INSTALL_DATA) Docs/logos/*.* ${GNC_SHAREDIR}/Docs/logos
|
||||
|
||||
@mkdir -p ${GNC_SHAREDIR}/Reports
|
||||
$(INSTALL_DATA) Reports/*.html ${GNC_SHAREDIR}/Reports
|
||||
$(INSTALL_DATA) Reports/*.phtml ${GNC_SHAREDIR}/Reports
|
||||
# $(INSTALL_DATA) Reports/*.gif ${GNC_SHAREDIR}/Reports
|
||||
# $(INSTALL_DATA) Reports/*.jpg ${GNC_SHAREDIR}/Reports
|
||||
# $(INSTALL_DATA) Reports/*.xpm ${GNC_SHAREDIR}/Reports
|
||||
@mkdir -p ${GNC_SHAREDIR}/Reports/images
|
||||
# $(INSTALL_DATA) Reports/logos/*.* ${GNC_SHAREDIR}/Reports/images
|
||||
|
||||
# ------------------------------------------------------------------
|
||||
# hack alert -- the config dir stuff is messed up in configure.in as well
|
||||
|
||||
@ -903,11 +903,13 @@ htmlReadImageProc (GtkWidget *widget, String file, gpointer data)
|
||||
|
||||
/* construct absolute path -- twiddle the relative path we received */
|
||||
filename = gncFindFile(file);
|
||||
|
||||
|
||||
/* use the default proc for the hard work */
|
||||
retval = XmHTMLImageDefaultProc(widget, filename, NULL, 0);
|
||||
|
||||
free(filename);
|
||||
if (filename != NULL)
|
||||
free(filename);
|
||||
|
||||
return retval;
|
||||
}
|
||||
|
||||
|
||||
@ -89,28 +89,36 @@ PriceMV (BasicCell *_cell,
|
||||
PriceCell *cell = (PriceCell *) _cell;
|
||||
struct lconv *lc = gnc_localeconv();
|
||||
char decimal_point;
|
||||
char thousands_sep;
|
||||
|
||||
if (cell->monetary)
|
||||
decimal_point = lc->mon_decimal_point[0];
|
||||
else
|
||||
decimal_point = lc->decimal_point[0];
|
||||
|
||||
if (cell->monetary)
|
||||
thousands_sep = lc->mon_thousands_sep[0];
|
||||
else
|
||||
thousands_sep = lc->thousands_sep[0];
|
||||
|
||||
/* accept the newval string if user action was delete, etc. */
|
||||
if (change != NULL)
|
||||
{
|
||||
int i, count=0;
|
||||
|
||||
for (i=0; 0 != change[i]; i++)
|
||||
for (i = 0; 0 != change[i]; i++)
|
||||
{
|
||||
/* accept only numbers or a decimal point */
|
||||
if (!isdigit(change[i]) && (decimal_point != change[i]))
|
||||
/* accept only numbers or a decimal point or a thousands sep */
|
||||
if (!isdigit(change[i]) &&
|
||||
(decimal_point != change[i]) &&
|
||||
(thousands_sep != change[i]))
|
||||
return NULL;
|
||||
|
||||
if (decimal_point == change[i])
|
||||
count++;
|
||||
}
|
||||
|
||||
for (i=0; 0 != oldval[i]; i++)
|
||||
for (i = 0; 0 != oldval[i]; i++)
|
||||
if (decimal_point == oldval[i])
|
||||
count++;
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user