Recommended way to handle RTL mixed with LTR languages

Support
21

We will get this sorted can you post a copy of a long post with that issue so we can have a look

22

Its not a long post.

its a topic with thousands of posts. here

3 Likes
23

Iā€™m wondering if the bottleneck is Discourse generating the directional instructions or the browser interpreting them and rendering the display.

Have you compared the efficiency using different browsers?

24

The topic that you linked to seems to be loading correctly for me. I am using a fairly powerful computer, so that could be the difference. There is a small change that could be made to the code that Iā€™m sure would improve performance, but we would loose support for Internet Explorer.

What browser and operating system are you using?

I am surprised that the number of posts in a topic is making a difference. Iā€™ll look into that.

1 Like
25

Iā€™m on Ubuntu 16.04 and I tested with Mozilla and Chrome

I also tested with my cellphone now. However surprisingly, the topic opened normally. Now what could be the problem? :thinking:

1 Like
26

What version? You mean not Edge, so IE11 only? That could be an acceptable tradeoff for many audiences.

27

Thereā€™s no support for dir="auto" in IE11 or Edge.

1 Like
28

Wow thatā€™s really weird:

https://www.w3.org/International/tests/repo/results/the-dir-attribute-auto

29

Yes, I was surprised, so I tested it with BrowserStack as well. There is another approach we could take with this to make it more efficient, but we need to be sure thereā€™s a problem first.

31

After installing discourse from Docker, what settings should I change to reach this?

32

I think these two :
https://your.domain/admin/site_settings/category/all_results?filter=default%20locale
https://your.domain/admin/site_settings/category/all_results?filter=mixed%20text

then wrapping your text with:

<div dir="rtl">
ā€¦
</div>

or

<div dir="ltr">
ā€¦
</div>

works

2 Likes