Skip to content

Translation tools #210

@Altizo

Description

@Altizo

Hi, I am one of the members of the Russian-speaking ERPNext community.
We wanted to implement ERPNext in several enterprises and help in setting up and modifying ERPNext for the realities of doing business in Russia.

At the moment, the translation of ERPNext is terrible. Guided by the documentation, we have translated and verified over 300 translations on the translate.erpnext.com website. But when we started to deal with the translation update mechanism, we saw your discussion on this topic on github.

The README.md in the frappe and erpnext repositories provides a link to the translation tool translate.erpnext.com, although the documentation docs.erpnext.com/docs/user/manual/en/translations has a link to translatev2.erpnext.com.

When authorizing at translatev2.erpnext.com using registration data from translate.erpnext.com, it turns out to be logged in, but there are problems with rights when verifying translations.

We have some questions:

  1. Could you tell us how to translate ERPNext at the moment?
  2. What translation tool should be used in the future?
  3. Can we somehow help in the development or translation of documentation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions