# Bug OP-3 - [WYSIWYG] Use Rails I18n Translations instead of tinyMCE translations.

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-3

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date | 2012-10-11 –  |
| Priority | Medium |
| Module |  |
| Target versions |  |
| Observed in versions |  |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

tinyMCE stores its translations in multiple files (2 per theme and 2 for each plugin), which is hard to administrate.  
For translations within the openproject-tinymce-plugin (and -theme) I suggest to [export the given Rails translations to javascript.](https://github.com/fnando/i18n-js) This allows us to only manage one translations file.

TODO: Ask Martin how he handles translations in his timelines code.