Saw a closed issue regarding RTL support. Thought the 6.x-2.0* branch had fixed this. Not sure if is same problem or not (I'm very new to Drupal).

When I go to translate a node, I first switch my Windows Vista language/keyboard to Hebrew, click Add Translation, then start typing. I see Hebrew characters that type RTL even though they are left aligned. Choosing right alignment from FCKeditor menu causes a weird behavior with the cursor. I can preview the translation fine. After a Save, I get nothing but question marks like this: ?????? both on the home page and when I come back to edit the translation. The Source button also displays ???????

Am I missing a configuration somewhere? Is this a bug? or a user error on my part (if so can you educate me)?

Thanks

Comments

besjon’s picture

besjon commented
Title: FCKeditor mangles Hebrew » Drupal install doesn't check database for UTF-8 support
Project: FCKeditor - WYSIWYG HTML editor » Drupal core
Version: 6.x-2.0-alpha5 » 6.x-dev
Component: Code » install system
Category: bug » feature

Ok, this turned out to be a problem with the encoding on the database tables. I had installed Drupal from Fantastico - which apparently is known to occasionally?/always? create the MySQL database with latin1 encoding.

I saw some SQL scripts that could have changed the charset/collation across all the tables, but decided to do a clean reinstall. I first created an empty database and made sure the MySQL charset was set to "UTF-8 Unicode (utf8)" and the MySQL connection collation was set to "utf8_unicode_ci". After manually installing Drupal - Hebrew translations worked.

It would be really great if during the Drupal installation, Drupal could detect the charset/encoding on the database and provide a warning as necessary. For example,

"The Drupal installation has detected your database is using the Latin-1 character set and not using UTF-8 for storage. This will prevent you from using non-latin characters (for example, Arabic, Hebrew, Japanese, etc...). If all the content on your entire site will always be in latin characters, then you do not need to do anything. However, to support non-latin characters, you must first convert your database.

Do you want to convert your database now to UTF-8 and support alternate languages such as Arabic, Hebrew, Japanese, etc... or would you like to keep the existing settings and proceed?"

I've changed the Category on this entry from Bug to Feature request and changed the Project from FCKeditor to Drupal

multiplextor’s picture

multiplextor commented
Status: Active » Closed (won't fix)

Closed. The reason: expired.