search

frappe / erpnext

Free and Open Source Enterprise Resource Planning (ERP)
https://erpnext.com
GNU General Public License v3.0
20.82k stars 7.15k forks source link

Support i18n #127

Closed dploeger closed 12 years ago

dploeger commented 13 years ago

Either I'm simply blind or I cannot find any translations or other i18n issues (like chart of account templates). Please support that.

rmehta commented 12 years ago

Hello,

You are right. No translations at the moment. We are planning to take this up in November. If you have any suggestions, guidelines, pointers, it would be helpful.

dploeger commented 12 years ago

I18N consists of many points, I think. For germany I THINK (because I'm no expert in financial things here) we need the following things:

I don't know about other special things regarding double-entry bookkeeping, that's different in germany, but there seems to be a difference with american account handling and the german one.

I'd be glad to help in translating things, so if you need me, give me a hint.

rmehta commented 12 years ago

Hello Dennis,

Thanks for your interest and comprehensive response!

  1. Python & MVC - You are right, we have not designed this for
    internationalization grounds up - what we plan to do is first up,
    take the low-hanging fruits. We have metadata driven MVC model, so we
    can relatively easily add templates for different languages, that
    will take care of the form labels. For messages, I think gettext
    seems to hard (my inexperience). I am also evaluating putting the
    values in a db table (maybe using sqlite) so what I can ask
    volunteers to just fill in a spreadsheet that i can put into the db...
  2. JS - jquery-i18n does seem a simple enough lib, will surely look
    into this
  3. JS framework - the problem is that we have built a very
    comprehensive js framework, that does a lot of automation around
    forms and stuff and is tightly integrated with the backend. In the
    long run, it might be a better idea to take an existing framework and
    the qxoodoo api is very nice, but its not something we can change in
    the near term.... In fact, I am in middle of a major re-write to the
    js framework to make extensive use of localStorage for storing code
    and models...
  4. Chart of Accounts & VAT forms: Currently we have very limited
    resources, so unless there are a set of customers who are ready to
    use the system. (They are okay with other things) we will put this on
    the hold. The product is more or less very flexible in terms of
    accounting structure so it should not be a big problem to update the
    Chart of Accounts and create those reports.

I will definitely ping you once the template design is ready. You can
help me with the German translation!

best regards, Rushabh

On Oct 10, 2011, at 2:59 PM, Dennis Ploeger wrote:

I18N consists of many points, I think. For germany I THINK (because
I'm no expert in financial things here) we need the following things:

  • Translation. Reading your code I see, that you hardcoded many
    things. For the python part I would suggest using [gettext](http:// docs.python.org/library/gettext.html). For the JS-part I would
    suggest using a better framework (like [qooxdoo](http:// qooxdoo.org/), that supports I18n from the ground up and is very
    pythonesque) or something like [that](http://recursive-design.com/ projects/jquery-i18n/) for jquery.
  • Chart of accounts. Germany heavily uses "SKR03" or "SKR04" as
    their chart of accounts. I can only give you a german site on this
    one, the one of german accounting company [Datev](http:// www.datev.de/inus2/inus? handler=doc&type=0&docnr=0907802&outfmt=view&acc=1) where you can
    download both. Look at other projects embedding that one. I guess,
    that would be nothing more than prepare a csv-import for the chart
    of accounts and provide both SKR03 and SKR04
  • It would be nice to support a report called "UstVA" (badly
    translated to "premature notification of VAT"). That's a form, that
    has to be filled out for the german tax offices. [Here](http:// www.datev.de/portal/ShowContent.do?pid=dpi&cid=174617) is a
    translated version of the german VAT form. I can't seem to find a
    translated one of the UstVA, but [here](http://www.hk24.de/ linkableblob/1507262/.4./data/ Umsatzsteuer_Voranmeldung_2011_ab_Juli- data.pdf;jsessionid=0C92F0196075B7D30AFCD3CB5AB93663.repl1) is a
    german reference and a (probably very badly translated) english
    version [here](http://translate.google.de/translate? hl=de&sl=de&tl=en&u=http%3A%2F%2Fwww.hk24.de%2Flinkableblob% 2F1507262%2F.4.%2Fdata%2FUmsatzsteuer_Voranmeldung_2011_ab_Juli- data.pdf%3Bjsessionid%3D0C92F0196075B7D30AFCD3CB5AB93663.repl1).

I don't know about other special things regarding double-entry
bookkeeping, that's different in germany, but there seems to be a
difference with american account handling and the german one.

I'd be glad to help in translating things, so if you need me, give
me a hint.

Reply to this email directly or view it on GitHub: https://github.com/webnotes/erpnext/issues/127#issuecomment-2344367

ERPNext - World's most affordable ERP - (Rs 299 / $7 per user per month)

Website: https://www.erpnext.com Twitter: @rushabh_mehta

rmehta commented 12 years ago

moved to wiki

dploeger commented 11 years ago

Hi Rushabh!

I'd like to reopen this issue. I saw, that you already have a nice (but incomplete) german translation. What about imports of chart of accounts and the support for SKR03/SKR04? Is that available?

I haven't looked into your report design, but I guess that the german tax report should be fairly easy to implement.

How can I help?

Thanks.

Dennis

rmehta commented 11 years ago

Dennis,

This is a really big issue, will leave it open. Will also be great if you can open specific issues for things like chart of accounts.

There are a couple of ways to make reports - simple ones using queries or you could also generate a report using a python script. Here is an example:

https://github.com/webnotes/erpnext/tree/master/accounts/report/gross_profit

To start a report, set developer_mode = 1 in conf.py and create a new "Report" record from the admin UI. The folder will be created automatically, then you can make the report.

best, Rushabh

On 19-Jun-2013, at 5:54 PM, Dennis Ploeger notifications@github.com wrote:

Hi Rushabh!

I'd like to reopen this issue. I saw, that you already have a nice (but incomplete) german translation. What about imports of chart of accounts and the support for SKR03/SKR04? Is that available?

I haven't looked into your report design, but I guess that the german tax report should be fairly easy to implement.

How can I help?

Thanks.

Dennis

— Reply to this email directly or view it on GitHub.

dploeger commented 11 years ago

Hi Rushabh!

You're right. I've split up the issues:

Support SKR03/SKR04 => https://github.com/webnotes/erpnext/issues/508 Fix german translation => https://github.com/webnotes/erpnext/issues/509 Support "UstVA"-Report => https://github.com/webnotes/erpnext/issues/510

So actually, we could close this issue now and work on the other ones.

Kind regards Dennis

hwinkel commented 10 years ago

When building the feature please consider that you have different languages in one business transaction. Translating the UI for the ERP user is one thing and stick to the users language. But a customer also has a spoken language which can differ from the users language. In OpenERP in example you have translated documents i.e. Invoice and in german Rechung. If a user with the profile language "english" issues a Invoice to a german speaking customer this will be rendered as "Rechnung". The same comes true with Item Descriptions etc.

Is the i18n system prepared for that?