[grisbi-cvs] grisbi/help/en contents_motif.gif, 1.1, 1.2 grisbi-manuel.html, 1.1, 1.2 Makefile.am, 1.1, 1.2 next_motif.gif, 1.1, 1.2 previous_motif.gif, 1.1, 1.2 quickstart.html, 1.1, 1.2 topic.dat, 1.1, 1.2 translation.html, 1.1, 1.2

Martin Stromberger fabiolla at users.sourceforge.net
Sat Dec 27 18:09:25 CET 2008


Update of /cvsroot/grisbi/grisbi/help/en
In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv30788/help/en

Added Files:
	contents_motif.gif grisbi-manuel.html Makefile.am 
	next_motif.gif previous_motif.gif quickstart.html topic.dat 
	translation.html 
Log Message:
en helpfiles for default help

--- NEW FILE: previous_motif.gif ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: contents_motif.gif ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: topic.dat ---
grisbi-manuel.html User's guide
quickstart.html Getting started
translation.html Translation howto

--- NEW FILE: grisbi-manuel.html ---
<HTML>
<HEAD><TITLE>Grisbi's User Guide</TITLE>

<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-15">
<meta name="generator" content="Bluefish 0.9">
</HEAD>
<BODY BGCOLOR="#ffff99">

<H1 ALIGN=center>Grisbi's User Guide</H1>

<H3 ALIGN=center>Copyright © 2001-2003 Daniel <FONT COLOR=navy>Cartron</FONT></H3>

<H3 ALIGN=center>Last update: 2003-11-06</H3>

First of all, have you subscribed to Grisbi's 
<A HREF="mailto:infos at grisbi.org">infos mailing list</A>?<BR>
<BR>
You will receive only a few messages a year, about 
the new versions and the bugs fixes.<BR>
<BR>
So don't wait, do it just now!<BR>
<BR>

Since the 0.4.1 version, the user guide is no more integrated in the package of Grisbi.
Effectively, its ever-growing weight and its internationalisation obliged us to create
a separate package.

<h1>The Guide Types</h1>

The user guide comes in two types:

<ul>

	<li>a text only type;</li>
	
	<li>an illustrated type, with many screenshots.</li>

</ul>

It is obvious that the second one is more pleasant to use but take also
longer to download. So it's up to you...

<H1>Installing the Guide</H1>

On <a href="http://www.grisbi.org">Grisbi's site</A> you'll find the package you need in the section
<A href="http://www.grisbi.org/download.en.html#doc">Documentation</A> from the
<A href="http://www.grisbi.org/download.en.html">Download</A> page.
For the moment only the French version is available.

Translators welcome! Send a mail to 
<a href="mailto:daniel at grisbi.org?Subject='[grisbi] Translation'&Body='I
can translate the users guide in the following language:'">Daniel</a>
if you want to help Grisbi.

<H2>Installing a Package</H2>

Like the program, the guide is available as Debian or RPM packages.
However there are no specifics packages for other distributions.

Install the package as you use to. The files will be placed in the
/usr/share/gnome/help/grisbi/C directory.

<H2>Installing Manually</H2>

If for any reason you need (or prefer) to process the installation
manually, you must download the manuel-grisbi-xxx-n.n.n.tar.gz archive,
where xxx is the version type (text or illustrated, txt or img respectively)
and n.n.n the version number.

Untar this archive and copy all the  .html and .png files as well as the
topic.dat file in the /usr/share/gnome/help/grisbi/C directory.

</BODY>
</HTML>

--- NEW FILE: Makefile.am ---
## Process this file with automake to produce Makefile.in.

HTML_FILES =			\
	grisbi-manuel.html \
	quickstart.html \
	translation.html

grisbi_helpdir = $(datadir)/doc/grisbi/en

grisbi_help_DATA = \
	topic.dat     \
	contents_motif.gif \
	next_motif.gif \
	previous_motif.gif \
	$(HTML_FILES)

EXTRA_DIST =  $(grisbi_help_DATA)

--- NEW FILE: next_motif.gif ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: quickstart.html ---
<HTML>
<HEAD><TITLE>Grisbi - Getting started</TITLE>

<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-15">
<meta name="generator" content="Bluefish 0.9">
</HEAD>
<BODY BGCOLOR="#ffff99">

<H1 ALIGN=center>Grisbi - Getting started</H1>

<H3 ALIGN=center>Copyright © 2001-2003 Daniel <FONT COLOR=navy>Cartron</FONT></H3>

<H3 ALIGN=center>Last update: 2003-04-02</H3>
First of all, have you subscribed to Grisbi's 
<A HREF="mailto:infos at grisbi.org">infos mailing list</A>?<BR>
<BR>
You will receive only a few messages a year, about 
the new versions and the bugs fixes.<BR>
<BR>
So don't wait, do it just now!<BR>
<BR>

<H1>Chapter&nbsp;1&nbsp;&nbsp;Create an Account File</H1>

<H2>1.1&nbsp;&nbsp;Import QIF files</H2>

We'll suppose you have exported your accounts as QIF files 
with your former accounting program (you need a QIF file for
 each account). Now you can import them in Grisbi:
<UL><LI>click on the menu <I><FONT COLOR=maroon>File/Import/QIF file</FONT></I>;<BR>
<BR>
<LI>select the directory containing the QIF files;<BR>
<BR>
<LI>select them all by clicking on their name. Grisbi must
 import them at once in order to reconstitute the links beetween 
the accounts (notably transfers). Then valid.
As Grisbi asks you to confirm, you still can add an account if you forgot one;<BR>
<BR>
<LI>choose the currency of each account. The default choice is 
Euro but you can create a new currency by clicking the 
<I><FONT COLOR=maroon>New currency</FONT></I> button.</UL>
Grisbi will process your files for a few seconds, and that will be it.<BR>
<BR>

<H2>1.2&nbsp;&nbsp;New Account File</H2>

You don't have any file to import. Click on the menu <I><FONT COLOR=maroon>File/New</FONT></I> 
to create a new accounts file, then on
<I><FONT COLOR=maroon>Account/New</FONT></I> to create the accounts you need.<BR>
<BR>
Now click on the tab <I><FONT COLOR=maroon>Transactions</FONT></I>, then on the left icon 
 <I><FONT COLOR=maroon>Show/mask the form</FONT></I>.<BR>
<BR>
You are ready to enter your transactions.<BR>
<BR>

<H1>Chapter&nbsp;2&nbsp;&nbsp;Grisbi's Tabs</H1>

<H2>2.1&nbsp;&nbsp;Home</H2>

Displays your accounts list, their balance, and the warnings.<BR>
<BR>

<H2>2.2&nbsp;&nbsp;Transactions</H2>

Displays in the right part the transactions of the account you selected in the left part.
Allows you to enter transactions. For this you must first click on the left icon
of the tool bar, or double-click in the first empty line of the transactions list.<BR>
<BR>
The transactions can be displayed with more or less information. Use the icons
with white and blue lines to change the number of information lines displayed.
You can also choose to display or not the reconciliated transactions by clicking on the
R or crossed R icons.<BR>
<BR>
For creating a third part that doesn't exist in your file, just enter
its name in the combo box, and it will be added.<BR>
<BR>
For creating a new category or budgetary-line, do the same but be careful with the syntax: you
must separate the name of the category and the one of the sub-category with:
<UL><LI>a space;<BR>
<BR>
<LI>a colon (:);<BR>
<BR>
<LI>another space,</UL>
or else Grisbi will not understand.<BR>
<BR>
For creating a new financial year click on the menu
<I><FONT COLOR=maroon>Setup/Financial years</FONT></I>.<BR>
<BR>

<H2>2.3&nbsp;&nbsp;Scheduler</H2>

Allows you to schedule repetitive transactions.<BR>
<BR>

<H2>2.4&nbsp;&nbsp;Accounts</H2>

Displays the list of all your accounts and their properties, and
allows you to edit them.<BR>
<BR>

<H2>2.5&nbsp;&nbsp;Third parts</H2>

Displays the list of all the third-parts, the complementary information
about them, and allow you to edit them.
Also displays the transactions sorted by account (you can use the icons for
quickly opening or closing the tree).
Allows you to access a given transaction immediately by double-clicking
on it.<BR>
<BR>

<H2>2.6&nbsp;&nbsp;Categories</H2>

The same as the <I><FONT COLOR=maroon>Third parts</FONT></I> tab, it allows you to classify
your incomes and outgoings.
You can add or edit a category or sub-category, and display the transactions
of one or all categories.<BR>
<BR>

<H2>2.7&nbsp;&nbsp;Budgetary lines</H2>

The same as the former ones, it allows you to manage your budgetary lines.<BR>
<BR>

<H2>2.8&nbsp;&nbsp;Reports</H2>

Allows you to create and display all the reports you need.
Some are already built-in, and you can customize them with a very powerful tool.<BR>
<BR>
For the moment you can't print them (this is planned for the 0.4.3 version).<BR>
<BR>

<H1>Chapter&nbsp;3&nbsp;&nbsp;Grisbi's menus</H1>

The <I><FONT COLOR=maroon>File</FONT></I> and <I><FONT COLOR=maroon>Accounts</FONT></I> menus are
quite intuitive. The <I><FONT COLOR=maroon>Setup</FONT></I> menu allows you to setup Grisbi's 
general behaviour, and is explicit.<BR>
</BODY>
</HTML>

--- NEW FILE: translation.html ---
<HTML>
<HEAD><TITLE>Translating Grisbi</TITLE>

<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-15">
<meta name="generator" content="Bluefish 0.9">
</HEAD>
<BODY BGCOLOR="#ffff99">

<H1 ALIGN=center>Translating Grisbi</H1>

<H3 ALIGN=center>Copyright © 2001-2003 Daniel <FONT COLOR=navy>Cartron</FONT></H3>
<H4 ALIGN=center>English translation: Daniel <FONT COLOR=navy>Cartron</FONT></H4>
<H4 ALIGN=center>Proof reading: Sébastien <FONT COLOR=navy>Blondeel</FONT> AKA SBI</H4>

<H3 ALIGN=center>Last update:  2003-04-02</H3>

Grisbi needs your help for translations. If you can do some translations
in a language not yet implemented, please feel free to send a mail to 
<a href="mailto:daniel at grisbi.org?Subject=[grisbi] Translation&Body="I
 can translate the user's guide in the following language:">Daniel</a>
explaining in which language you can translate.

Then it's really important to subscribe to the <a 
href="mailto:traduction at grisbi.org">translation mailing list</a> 
by sending <a href="mailto:traduction-subscribe at grisbi.org">this mail</a>.

<h1>The files to translate</h1>

There are several kinds of files to translate. We'll check all of them.

All these files will be avaliable on the <a 
href="http://www.grisbi.org">Grisbi's site</a> in the section <a 
href="http://www.grisbi.org/modules.php?name=Downloads">
Download/Translation</a>. However, if you want to work on the latest 
issues of the files, you should ask us for CVS and FTP access.

<h2>The website</h2>

Not the more usefull for the programm but the more usefull for advertising and
finding some help. 

The files to translate are :

<ul>

<LI>grisbi-block-contact-C.txt</LI>
<li>grisbi-contact-C.txt</li>
<li>grisbi-home-C.txt</li>
<li>grisbi-infos-C.txt</li>
<li>grisbi-mainmenu-C.txt</li>
<li>grisbi-mirrors-C.txt</li>
<li>grisbi-title-C.txt</li>
<li>grisbi-version-C.txt</li>

Once the files are translated you have to rename them with your 
<a href="http://www.w3.org/WAI/ER/IG/ert/iso639.htm">2 letter ISO-639 language code</a>
e.g. grisbi-home-en.txt for English or grisbi-home-fr.txt for French.

</ul>

<h2>The programm</h2>

You just have to translate the grisbi.pot file. Then rename it with your 
<a href="http://www.w3.org/WAI/ER/IG/ert/iso639.htm">2 letter ISO-639 language code</a>
and .po, e.g. en.po for English or fr.po for French.


<h2>The help files</h2>

There are three HTML files and a text file: 

<ul>

<li>quickstart.html;</li>
<li>grisbi-manuel.html;</li>
<li>translation.html;</li>
<li>topic.dat.</li>

</ul>

<h2>The user's guide</h2>

The user's guide is made of several .tex files, a Makefile, an image 
directory and a tool directory.

The image directory contains all the screenshots and the icons in two
separate sub-directories. We will soon provide you some scripts to make
the screenshots automatically. We'll also provide you a script that will
warn you as soon as a .po change implies a new screenshot. But for the
moment you'll have to do it by yourself. Sorry for the inconvenience.

The tool directory contains the scripts (mainly in Perl) that will help
you to compile the sources.

The .tex files will be soon connected to the .po files, so you won't
have to translate any text that appears in the GUI.

<h1>How to translate</h1>

We'll give you some advice that you are not abliged to follow. Only the
result matters...

<h2>The website</h2>

As they are HTML files, you can use any editor you want. You can use a
text editor or an editor dedicated to the HTML as Bluefish or Quanta+.

<h2>The program</h2>

The .po file can be translated easily with Kbabel, Emacs, or even some
VI clone... Choose the one you want.

If you are not used to any of these programs, Kbabel will certainly be
the easiest one for you.

<h2>The help files</h2>

As they are HTML and text files, you can use any editor you want for
translating them. Just be careful not to translate the tags, only the
text :-) For the topic.dat you <b>must</b> only translate the second
term of each line (which is the label of the entry in the help menu) but
not the first one (which is the name of the related file).

<h2>The user's guide</h2>

The user's guide is written in LaTeX, including macros which will help
to compile the source in two differents types, text-only or illustrated.
We therefore advise you to keep this format. If you are not used with
LaTeX, you should try Kile, which is a LaTeX-editor dedicated to KDE. If
you really want another file format, let us know, but you'll probably
have difficulties to maintain two differents types at the same time...

<h1>How to verify</h1>

Before commiting your translations it's your duty to control they will work.

<h2>The website</h2>

As the website uses text files with the HTML tags you just have to write
them with an HTML editor and then copy the text part between tne body
and /body tags and it should work. Anyway, if it doesn't, it's easy to
see on the site, so you just have to correct.

<h2>The program</h2>

You should be able to compile the program on your box. If you never do
such a thing don't panic we'll help you. You just have to install the
needed libraries then compile as it's explained in the user's guide.

<h2>The help files</h2>

They are HTML and TXT files, so it's easy to see if they work. And if
you copy them in the right location on your box you can see imediately
if it's correct.

The directory of your language is
/usr/share/gnome/help/grisbi/<i>lang</i> where <i>lang</i> is the 2
letters code for your language.

<h2>The user's guide</h2>


<!-- SBIREM explain hot to compile them -->

If you use the LaTeX files you just have to compile them with the tools
provided, and then control the result either in HTML or PDF format.

<h1>How to commit</h1>

<!-- SBIREM explain how -->

Once you are satisfied, you have to commit your work in order to let the
community use it.

<h2>The website</h2>

The best way is to ask our <a href="mailto:webmestres at grisbi.org">webmasters
</a> to give you an access just for your language, so you can add or 
modify the texts as you want. Send a mail to
<a href="mailto:webmestres at grisbi.org?Subject=[grisbi site]&Body=I would 
like to have an access to the website for publishing texts in the following 
language:">the webmasters</a> to ask for such an access.

<h2>The programm</h2>

This file have to be commited in the code sources, so if you're a lone 
translator, you just can send the .po file to 
<a href="mailto:daniel at grisbi.org?Subject=[grisbi] Translation&Body=You 
will find attached the .po file for the following language:">Daniel</a>
who will commit it for you.

If you work in a team it's more efficient that one of you asks for the
rights to commit the .po and doc files, so you just have to deal with
him (or her) for the commits.

<h2>The help files</h2>

See above.

<h2>The user's guide</h2>

The scripts to publish the guide are in the makefile (make transfer).
You will need the config files, so just ask to <a
href="mailto:daniel at grisbi.org?Subject='[grisbi] Translation'&Body='I
need the config files for committing the user s guide for the following
language:'">Daniel</a> the needed files.

</BODY>
</HTML>



More information about the cvs mailing list