Bug report, StarUML v5.1: Markdown code tags leave no proper spacing with normal text around it.

Skip to first unread message

Vasileios Pothos

Jul 30, 2023, 8:17:00 AMJul 30
to StarUML
Issue Title: Markdown code tags leave no proper spacing with normal text around it.
Environment: Windows 10 Home, StarUML v5.1
Action Performed:
1. Select a model/component.
2. In markdown edit window add some normal text including also code tags (inline code blocks) among with the text. Add also multiple spaces between some text and code tags.
3. View the Markdown in preview mode.

Expected Results: The Preview text should be read easily with proper, and as provided, spacing among normal text and code tags.
Actual Results: Normal text and code tags tend to no having spaces, making it really hard to read. Multiple spaces among text and code tags is missed!
I've done three demonstration experiments in the following image. Three lines where I add text and code tags, including different number of spaces among them. In the Preview mode at the bottom of the image, the text and code tags are in most of the cases collapsed together without any space.


Jul 31, 2023, 12:27:06 AMJul 31
to StarUML

It is not a bug. Markdown compiler always converts many spaces (includes a single space) into a just single space. It seems to change consistently to a single space in all the cases you provided.

Is it because of the font? I can see one space before and after `MyFile.cpp`.


2023년 7월 30일 일요일 오후 9시 17분 0초 UTC+9에 vasileio...@gmail.com님이 작성:

Vasileios Pothos

Jul 31, 2023, 2:29:15 AMJul 31
to StarUML

It can be due to the mix of the different fonts. It may indeed be a single space of the normal text space (which is narrow) but this is visually incompatible with the code snippet font and makes the two words "file MyFile.cpp" seems more like merged together and hard to read.

I'd prefer the space to be at least of the font of code snippet - which is wider like in the case of "MyFile.cpp and" in 2nd row (and in this case it seems that the merged spaces rules is not followed). This aids to make easier the distinction on the different texts.

Also I have the impression that spaces in code snippets should not be replaced, as it represent code and may have a purpose when used.

Personally I find this way of implementation hard to read/confusing - that's why I thought it was a bug. But if it's the expected behavior for the S/W, then ok.

Reply all
Reply to author
0 new messages