Bug #21932
closed
Context Menus don't work in Rich Text Editor on other language (Brazilian Portuguese)
Added by Daniel Arndt almost 15 years ago.
Updated about 6 years ago.
Description
When user's default language is not English (is Brazilian Portuguese, on my case), the Context Menu in Rich Text Editor don't work, and the default browser context menu are show.
If the user change your language to English, the context menu on Rich Text Editor works fine.
On tree page navigator panel, the context menu are working fine. This issue is only in the Rich Text Editor.
I have updated the language files, on the "Translation handling" page, and "Update from repository", but the issue isn't solved.
(issue imported from #M13188)
Does it work for you with other non-english languages?
E.g. I know that for me German works...
Since 4.3 I have problems with the german translation too.
Every Label or Tooltip ends if there is an Umlaut. "Tabelle einfügen" is now "Tabelle einf". So the String really stops and is not substituted by cryptic signs etc.
Got this problem in all of my 4.3 Systems (same PHP core, same DB-Server) but only with rtehtmlarea.
I tried to force BE-Charset to UTF-8 but this really messes up everything else...
Never got problems with this in the past, so I wonder if it is a bug?
@ Daniel, Alex: Can you give us more information about your environement?
What is the BE charset?
Does the problem appear only in the context menu or also in the toolbar?
What version of PHP?
The context menu is working in Brazilian when the BE charset is utf-8. So, there must be a problem when the charset is different. Please report the BE charset that you specified, if any.
force BE-Charset UTF-8 solved it.
But the following problem was, that all tt_content contents had broken umlauts when viewing in BE and simply saving it would have written the wrong (cryptic) character into the database... so I had to fix these manually.
Due to my problems (or let's say misconfiguration) with the RTE I switched all my systems to 100% UTF-8. Now everything works perfect for me.
Without the force BE-charset the umlauts in the tooltips (title-attr) and the context menu (right click) were broken.
My former BE-charset was ISO-8859-1 while Database was a terrible mess.
PHP was 5.2.5.
I really think the databese was the troublemaker.
I don't think that the database is the troublke maker. The labels are coming from xml files not from the database. I will look into this issue.
Note that I think that there is an extension on TER that can help you convert content elements to utf-8. But if it is already done or partially done, I guess this is too late for you.
I just tried the RTE with a non-utf-8 BE in French, German and Russian in Firefox 3.6 and IE8, I can't reproduce this issue.
But there were fixes that may affect this that were included in version 1.8.7.
Please confirm that this is fixed in TYPO3 4.3.1.
The xml-file was working correctly since I switched to force-Charset UTF-8 in my old 4.3.0, but suddenly all my database content was wrong in the BE. That's why i thought the database was making trouble because it wasn't returning UTF-8. I just assumed that it was a RTE problem but it really is not when forcing charset to UTF-8.
I just tried it with a non-UTF-8 BE (ISO-8859-1). It works properly!
Typo3 4.3.1 (rtehtmlarea 1.8.7)
This was fixed in TYPO3 4.3.1
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by