@TheAwiteb I'd appreciate it if you could take a look and share your thoughts here

✅ Deploy Preview for tabi-demo ready!

Name	Link
🔨 Latest commit	35614b0
🔍 Latest deploy log	https://app.netlify.com/sites/tabi-demo/deploys/6711a7196f5fc70008c4942d
😎 Deploy Preview	https://deploy-preview-412--tabi-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

I agree with code and not pre, because code often contains programming code, which is often LTR and rarely RTL, but pre doesn't have to be LTR

Also, I don't think there is a need for it. There is no need to hard code the direction. You can add a div with the direction you want before the code block.

<div dir="ltr">

```rust
fn main() {
    println!("Hello, World");
}
```\

</div>

Thanks for your thoughts, @TheAwiteb!

I think it makes sense to support the most common use cases, both for RTL and LTR users.

Would it be fair to assume more than half of the time, the author of a page will want LTR code block? The div idea is good, and could be used in case someone needs an RTL code block. In this case, I would keep the "force LTR" in tabi.

To me, forcing code blocks to LTR but not inline code makes sense. Thoughts, @mohammad-amin-khajeh?

The div idea is good, and could be used in case someone needs an RTL code block.

If you force it in CSS I don't think you can make it RTL right? So the div idea won't work

If you force it in CSS I don't think you can make it RTL right? So the div idea won't work

You're right.

I'm thinking of:

• Changing nothing, and users can use the div trick
• Adding a config.toml option to force code blocks to RTL

Would love your thoughts, @TheAwiteb @mohammad-amin-khajeh

Changing nothing, and users can use the div trick

For me, this is better

Adding a config.toml option to force code blocks to RTL

Not all code blocks in a post need to be RTL, it can be both, LTR and RTL

Changing nothing, and users can use the div trick

I feel like this will get repetitive and tedious quickly, because most people I assume(writing in an rtl language that is) would want to have their codeblocks ltr.

I suggest making codeblocks ltr by default, while also having a shortcode that behaves like add_src_to_code_block which makes the codeblock below it rtl in case someone wants that.

How about:

• hierarchy-respecting config to force LTR codeblocks (on by default)
• shortcode to force LTR/RTL content within

shortcode to force LTR/RTL content within

Shortcode looks better, something like this

{% ltr() %}

...

{% end %}

I will add the shortcode.

Would a default LTR codeblock setting make sense / satisfy most users? Again, with the option to unset / override for the whole site/section/specific page.

Essentially, the question is: would most RTL website owners expect their codeblocks to be LTR by default?

I can't speak of everyone here.

But I don't think I personally will ever change it to RTL if it were LTR by default.
Because slashes in urls and hashes and a lot of other common symbols would look messy and all over the place.
Just as you saw in the picture I included in the issue.

So to me it makes total sense if LTR was the default.

would most RTL website owners expect their codeblocks to be LTR by default?

Yes

I will review the PR soon. The shortcode(s) to force LTR/RTL will come in another PR.