#1

Composing overlapping Markdown font directives doesn’t work, resulting in the following (mis)render.

image
image1436×70 11.1 KB

1 Like
#2

Under Windows 10, notably. v0.8.15.

#3

uhm… not sure this is generally agreead upon behaviour.

#4

I am gonna move this to feature requests

#5

https://babelmark.github.io/?text=***cat**+dog*

#6

I’m not sure which programs would interpret this combination as desired

Using underlines and asterisks ought to work

#7

I would find that a more acceptable answer (in general) if the default italic that you get when hitting Control-I wasn’t the single asterisk but the single underline.

By default, it’s choosing a mechanism that is overloaded. One of these behaviors probably needs to change in order to avoid the conflict arising from natural use of the product.

#8

It would be even better if markdown didn’t have syntax clashes.

#9

Whichever approach is used, shouldn’t the editor and the preview be consistent? In the example given, it looks like the editor applies italics whereas the preview does not.

1 Like
#10

iirc the editor and the preview are based on different engines, so potential for discrepancies exists.

That will disappear with wysiwyg

2 Likes
#11

I feel a bit torn about this. I’ll move it back to bug reports.

1 Like