-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bidi not supported in Squire editor #1158
Comments
There are several options:
A more important part is the CSS However, when writing a plain text message, instead of HTML, the above mentioned options are useless. So, when thinking about that. Would the following on the <div class="squire-wysiwyg" dir="auto" style="unicode-bidi: plaintext"> |
Finally, it doesn't solve the issue because there are instances where users need to specify the text direction manually. For example, a user might write a Persian paragraph that begins with an English word and want to set RTL direction. An example of such a sentence is: I want to specify the RTL direction for this sentence, but since it starts with an English word, browsers automatically align it to the LTR direction, that's not good. Therefore, I want to specify the text direction for certain paragraphs. Additionally, there are many cases where the target webmail doesn't support automatic text direction detection, and we must manually specify the direction in HTML tags. For example, some legacy email services lack automatic text direction detection, resulting in wrong text direction. |
Good examples!
|
Sounds good, thank you. When do you think this feature will be added to Squire? |
I appreciate you taking the time to add this feature, but unfortunately, it is not functioning properly. Hence, I sent the required changes as a PR #1200. |
Hello
As you mentioned in #630, would you please add the new version of CKEditor (CKEditor 5) to Snappymail?
The bidi buttons are needed for RTL based languages such as Persian, Hebrew and Arabic, but this is not supported in Squire editor.
I'm also trying to do this and if I succeed, I will send these changes as a PR.
The text was updated successfully, but these errors were encountered: