sql-ledger-users

[SL] Translation of Chart of Accounts descriptions

[Bob G. <bo...@rc...>]

I have two users:
  One is English speaking
  Two is German  speaking

Is it possible to have the Chart of Accounts description visible in the
appropriate language for both of these users?

I know that I will have to supply a translation for these descriptions,
but where should this translation go?

Thanks for your hints

Bob G

Re: [SL] Translation of Chart of Accounts descriptions

[Dr E. L. <el...@li...>]

Read the Manual :-)-O

Define two users, select appropriate language, for each.


Though, personally speaking, I find this hard to believe that
one would allow someone not speaking the language of the tax
authority concerned, especially one as aggressive as the IRS,
access to a book keeping system.

greetings, el

on 6/7/07 10:19 AM Bob Gustafson said the following:
> I have two users:
>   One is English speaking
>   Two is German  speaking
> 
> Is it possible to have the Chart of Accounts description visible in the
> appropriate language for both of these users?
> 
> I know that I will have to supply a translation for these descriptions,
> but where should this translation go?
> 
> Thanks for your hints
> 
> Bob G

-- 
Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
PO Box 8421             \     /   Please do NOT email to this address
Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way

Re: [SL] Translation of Chart of Accounts descriptions

[Bob G. <bo...@rc...>]

I have read through the mainual

I do have two users.

The menus down the left are nicely translated appropriately. However
there are other non-translated items that poke through, particularly the
Chart of Accounts data.

I agree that learning German or English would be the better solution,
but that will happen with time. I am looking for a 'quick fix'.

Bob G

On Thu, 2007-06-07 at 11:46 +0100, Dr Eberhard Lisse wrote:
> Read the Manual :-)-O
> 
> Define two users, select appropriate language, for each.
> 
> 
> Though, personally speaking, I find this hard to believe that
> one would allow someone not speaking the language of the tax
> authority concerned, especially one as aggressive as the IRS,
> access to a book keeping system.
> 
> greetings, el
> 
> on 6/7/07 10:19 AM Bob Gustafson said the following:
> > I have two users:
> >   One is English speaking
> >   Two is German  speaking
> > 
> > Is it possible to have the Chart of Accounts description visible in the
> > appropriate language for both of these users?
> > 
> > I know that I will have to supply a translation for these descriptions,
> > but where should this translation go?
> > 
> > Thanks for your hints
> > 
> > Bob G
> 

Re: [SL] Translation of Chart of Accounts descriptions

[Dieter S. <dsi...@sq...>]

On Thu, 7 Jun 2007, Bob Gustafson wrote:

> I have two users:
>  One is English speaking
>  Two is German  speaking
>
> Is it possible to have the Chart of Accounts description visible in the
> appropriate language for both of these users?
>
> I know that I will have to supply a translation for these descriptions,
> but where should this translation go?

For display purposes (reports) you could use the GIFI, that is if you do 
not use the GIFI in lieu of DATEV.

With a bit of coding you could link the chart of accounts to a translation 
and retrieve the description based on the language setting.

Re: [SL] Translation of Chart of Accounts descriptions

[Bob G. <bo...@rc...>]

On Jun 7, 2007, at 09:28, Dieter Simader wrote:

> On Thu, 7 Jun 2007, Bob Gustafson wrote:
>
>> I have two users:
>>  One is English speaking
>>  Two is German  speaking
>>
>> Is it possible to have the Chart of Accounts description visible  
>> in the
>> appropriate language for both of these users?
>>
>> I know that I will have to supply a translation for these  
>> descriptions,
>> but where should this translation go?
>
> For display purposes (reports) you could use the GIFI, that is if  
> you do
> not use the GIFI in lieu of DATEV.
>
> With a bit of coding you could link the chart of accounts to a  
> translation
> and retrieve the description based on the language setting.
>

I am using the German GIFI - that is linked in anyway. I was not sure  
what the DATEV was.

My assumption is that there are normally two Charts of Account, the  
(DATEV - regular ?) and the GIFI. The regular one is mostly visible  
and the GIFI is there to be linked to and would be available for  
outside financial audits, etc.  Is this the way it works?

Maybe doing the DATEV in English and the GIFI in German? Have not  
tried this.


The coding part I can figure out, I was just wondering if there was  
an easier way that was already done. Some hints here would be helpful  
though.


Bob G

Re: [SL] Translation of Chart of Accounts descriptions

[Dieter S. <dsi...@sq...>]

This has been added in the next release, v2.8.7. The translation depends 
on the user's language preference.


On Thu, 7 Jun 2007, Bob Gustafson wrote:

> I have two users:
>  One is English speaking
>  Two is German  speaking
>
> Is it possible to have the Chart of Accounts description visible in the
> appropriate language for both of these users?
>
> I know that I will have to supply a translation for these descriptions,
> but where should this translation go?
>
> Thanks for your hints
>
> Bob G
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] Translation of Chart of Accounts descriptions

[Bob G. <bo...@rc...>]

Fantastic.

On Jul 7, 2007, at 11:17, Dieter Simader wrote:

> This has been added in the next release, v2.8.7. The translation  
> depends
> on the user's language preference.
>
>
> On Thu, 7 Jun 2007, Bob Gustafson wrote:
>
>> I have two users:
>>  One is English speaking
>>  Two is German  speaking
>>
>> Is it possible to have the Chart of Accounts description visible  
>> in the
>> appropriate language for both of these users?
>>
>> I know that I will have to supply a translation for these  
>> descriptions,
>> but where should this translation go?
>>
>> Thanks for your hints
>>
>> Bob G
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users

[SL] System for updating user copies of sql-ledger and retaining user fiddles

[Bob G. <bo...@rc...>]

If you have been tempted to make changes to the sql-ledger code to
respond to local requirements, using svn as your source code control
system offers an 'easy' way to handle your changes and the upgrade to
new versions when they come out.

This piece of the svn handbook outlines the approach:

http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

Re: [SL] System for updating user copies of sql-ledger and retaining user fiddles

[Bob G. <bo...@rc...>]

This is more on the subject of Subversion and sql-ledger

Attached is a script for doing sql-ledger version upgrades and keeping
all the files (with your own tweeks too) under version control.

The script follows the block diagram below:

#  /usr/local/sql-ledger          svnrepos (directories below within
repos)
#  ---------------------          ---------------------------------
#      (STEP1)            import
#  vendor v 2.8.5       ->->->->-> /vendor/sql-ledger/current
#
#                            <-<-< /vendor/sql-ledger/current
#                            v
#      (STEP2)          copy | tag
#                            v
#                            >->-> /vendor/sql-ledger/sql-ledger-2.8.5
#
#                            <-<-< /vendor/sql-ledger/sql-ledger-2.8.5
#                            v
#      (STEP3)          copy | to main
#                            v
#                            >->-> /sql-ledger/
#      (STEP4)
#      rm -rf
#                            <-<-< /sql-ledger/
#                        checkout
# /usr/local/sql-ledger  <-<-|
#         |
#         V
# -------------------
# | external update |  (STEP5)
# |   to v 2.8.6    |
# -------------------
#         |
#         V            (STEP6) Backup and inspect the new 2.8.6 update
#         |
# /usr/local/sql-ledger ->->-> 
#                            v
#       (STEP7)        svn_load_dirs
#                            v
#                            >->-> /vendor/sql-ledger/current
#
#                            <-<-< /vendor/sql-ledger/current
#                            v
#                       copy | tag (done as part of above command
#                            v
#                            >->-> /vendor/sql-ledger/sql-ledger-2.8.6
#
#                            <-<-< /vendor/sql-ledger/sql-ledger-2.8.5
#                            v
#                            <-<-< /vendor/sql-ledger/current
#                            v
#       (STEP8)            merge
#                            v
#                            >->-> /sql-ledger/
#
#       (STEP9)           commit


On Thu, 2007-07-12 at 12:45 -0500, Bob Gustafson wrote:
> If you have been tempted to make changes to the sql-ledger code to
> respond to local requirements, using svn as your source code control
> system offers an 'easy' way to handle your changes and the upgrade to
> new versions when they come out.
> 
> This piece of the svn handbook outlines the approach:
> 
> http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html
> 
> -------------------------------------------------------------------------