Feature #12295

Multilanguage support for custom fields

Added by Daniel Felix almost 5 years ago. Updated about 1 year ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:I18n
Target version:-
Resolution:Duplicate

Description

Hi there,

it would be great to have some multilanguage support for custom field through.

Currently, if I'm using one redmine installation for my product which has 3 countrys with 3 different support-hotlines, I need to define my custom fields in 3 languages and associate them to three single projects.

If I could have the abbility to translate every custom field, it would be possible to create one project, with each custom field as single defined field with different translations, which would be identified by the userpreferences.

If no translation is found, the server should take the english translation (for example if french isn't defined, just take english).
The other option would be to define the custom field name as default translation, and add different translations per language.

Just one example.
Custom field: Customer (free text, used as default if no other language translation is found.
Translation for this field:
EN: Customer
DE: Kunde
FR: NIL

If some customer selects the new ticket field and has the preference de, he just sees "Kunde". If he selects new ticket with fr as prefrence, he get's the default - nontranslated custom field name - "Customer".

In my opinion, this would be very helpful to create a realy full l18n support in Redmine!

What do you think about this?


Related issues

Duplicates Redmine - Feature #3972: Translation for field values New 2009-10-05
Duplicated by Redmine - Feature #1631: Translation of Custom Fields Closed 2008-07-13

History

#1 Updated by fangzheng (方正) almost 5 years ago

+1

although not all project creators would like to translate every custom field. :)

#2 Updated by Artur M over 4 years ago

fangzheng (方正) wrote:

+1

although not all project creators would like to translate every custom field. :)

Most Redmine administrators need to translate custom fields.

#3 Updated by billy chou over 4 years ago

Artur M wrote:

fangzheng (方正) wrote:

+1

although not all project creators would like to translate every custom field. :)

Most Redmine administrators need to translate custom fields.

+1

#4 Updated by Maxim Krušina almost 4 years ago

+1

#5 Updated by Thomas Bieth over 3 years ago

I am facing same issue on our instance. We are working with an offshoring development / coding team and clients are located in Germany. Not all clients do like or understand English in Germany.
Coders and internal staff can handle English but translation would be smart and helpful.

#6 Updated by Toshi MARUYAMA almost 3 years ago

  • Related to deleted (Feature #3972: Translation for field values)

#7 Updated by Toshi MARUYAMA almost 3 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Duplicate of #3972.

#8 Updated by Toshi MARUYAMA almost 3 years ago

#10 Updated by Toshi MARUYAMA over 1 year ago

  • Duplicated by Feature #1631: Translation of Custom Fields added

#11 Updated by Anton Hedström about 1 year ago

+1

Also available in: Atom PDF