Editor.js: Support for i18n

Created on 30 Apr 2019 · 15Comments · Source: codex-team/editor.js

I'm trying to translate the editor tooltips and names to Portuguese, but the docs don't specify a way to do that, and in fact, it doesn't seem possible at the moment.

Can this be done?

important

Source

matheusgrieger

👍3

Most helpful comment

@matheusgrieger for now you can specify the title and icon with the toolbox property of Editor Config like this:

 const editor = new EditorJS({
  tools: {
    image: {
      class: ImageTool,
      toolbox: {
        icon: '<svg>my icon code</svg>',
        title: 'My Tool Title'
      }
    }
  }
});

We will describe this moment at the docs more carefully. Also, we will think about full localisation of all UI texts.

neSpecc on 8 May 2019

🎉7

All 15 comments

Is it, you'll have to write the code for it 💃

realmike33 on 4 May 2019

Is that a "not available, needs contribution"? 😆

I'll see what I can do to help and add this feature.

matheusgrieger on 6 May 2019

@matheusgrieger for now you can specify the title and icon with the toolbox property of Editor Config like this:

 const editor = new EditorJS({
  tools: {
    image: {
      class: ImageTool,
      toolbox: {
        icon: '<svg>my icon code</svg>',
        title: 'My Tool Title'
      }
    }
  }
});

We will describe this moment at the docs more carefully. Also, we will think about full localisation of all UI texts.

neSpecc on 8 May 2019

🎉7

Is someone in charge of i18n for editor.js ?

There is some hardcoded value: https://github.com/codex-team/editor.js/blob/3382da100076b997946523c1587d26dff7159ea3/src/components/modules/toolbar/index.ts#L127

So it's impossible to translate.

lionxvibe on 26 Dec 2019

👍1

@neSpecc

We will describe this moment at the docs more carefully. Also, we will think about full localisation of all UI texts.

Any progress here? I like this editor and want to integrate it into a VueJS application but I need the editor to be translated to german.

Worst case scenario would be to "translate" everything manually using

tools: {
  image: {
    class: ImageTool,
    toolbox: {
      title: '<<<TRANSLATION>>>'
    }
  },
  ...
}

even though, documentation is sparse when it comes to details about where to retrieve reference to be used in e.g. class: ImageTool from. I need some sort of import statement.

t-itzel on 21 Jan 2020

@t-itzel estimated 1-2 months. If you can contribute, it would be great and we would release it faster.

neSpecc on 21 Jan 2020

@t-itzel estimated 1-2 months. If you can contribute, it would be great and we would release it faster.

alright, thanks. Sorry but I can't manage to contribute right now.

t-itzel on 26 Jan 2020

How is the translation process going?
I would like to know if this support already exists, or if you are still planning to have it inserted in the next updates?
When released, I will be on hand to help with the translation into my language (PT-BR).
Thanks.

blindibrasil on 3 Apr 2020

👍1

@neSpecc anything I could do to help with the i18n?

glauberm on 10 Apr 2020

@glauberm This task turned out to be more complex architecturally, so I've started experimenting with it by myself. If you have a desire, we can suggest you participate in other issues. Or at least in translation, when the API will be released.

neSpecc on 19 Apr 2020

@neSpecc Thanks, I'll do that

glauberm on 20 Apr 2020

Will be shipped with 2.18 release

neSpecc on 22 Apr 2020

@neSpecc Great news! I will try to help too. We just need the general guidelines on how the plugins should behave.

Also there are many small notifications to take in account (ex: the image plugin).