Internationalize RichTextArea

[vaadin-bot]

Originally by @magi42

---

The RichTextArea component has many texts, such as the Background, Foreground, Font and Size menus and their items, but they are all in English. It would be nice if it would be possible to localize them.

Probably easiest way would be to add server-side API for providing translations for the texts. The texts are probably not localized in GWT and localizing them in IT Mill Toolkit for every language might be a lot of work.

The buttons "B", "I", "U", etc. can be localized with CSS, but I'm not sure how stabile such localizations are if the order of the buttons in the button background changes in GWT. Hope that they won't change it.

---

Imported from https://dev.vaadin.com/ issue #2189

[vaadin-bot]

Originally by @jojule

---

This will be postponed as it is not critical. We try to get 5.3.0 ready asap and 5.2 is definitely not the correct place for low priority enhantments.

[vaadin-bot]

Originally by @magi42

---

Hopefully a more correct milestone.

[vaadin-bot]

Originally by @jojule

---

yes. Sorry, my mistake.

[vaadin-bot]

Originally by @vaadin-miki

---

Attachment added: 2189-richtextarea_labels.patch (62.8 KiB) proposed solution

[vaadin-bot]

Originally by @vaadin-miki

---

a solution based on String[] (in addition to GWT-based properties) is proposed in the patch; it concerns only the labels and the tooltips (the icons can still be localised GWT-way)

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!