Brett on 11 Apr, 2016 02:47 PM
is in Arabic or other RTL format. I currently have it embedded by
default as it's an automatic feature of the preview (only included if
the style is also embedded based on save dialog settings). Are you
finding the output problematic?
Sure, I write my articles in Markdown and export to HTML because
it's easy to just copy and paste the code into a CMS. In a perfect
world I'd just give them the Markdown files and they would export
to whatever they like. Sadly, we are not there yet.
on 28 Dec, 2017 12:34 AM
I believe that there is currently a bug in Marked 2 (2.5.10 930) with disabling this RTL detect feature.
When I turn on the detect checkbox on an open document, it produces no visual change -- nested ltr elements are still being forced rtl. When I then turn the checkbox off again, it seems to strips all 'rtl' class information from the document -- including all of my 'rtl' class tags that were originally injected by my preprocessor. Whether the option is on or off, my document is incorrect when compared to a web preview.
I would love a setting where the Marked 2 RTL-detector can be just completely disabled -- or advice on a workaround. For a temporary workaround I have changed the name of my pre-processor class from 'rtl' to something else -- this seems to prevent Marked 2 from interfering with it -- but that isn't a good long-term solution.
Brett on 28 Dec, 2017 08:58 PM
This is because of a workaround I had to do at one point, as a result
the only difference when exporting without RTL detection is that it
doesn't actually style the RTL, but still applies the classes. Using a
different name in your script is ideal, but I'd consider changing the
class that Marked applies to something more namespaced (eg mk-rtl) to
avoid conflicts. I'll also take a look at disabling the script on export