Bug 446870 - Incorrect formatting of index when a list item begins with inline code.
Summary: Incorrect formatting of index when a list item begins with inline code.
Status: CONFIRMED
Alias: None
Product: okular
Classification: Applications
Component: markdown backend (show other bugs)
Version: 21.12.0
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-12 09:12 UTC by Kishore Gopalakrishnan
Modified: 2021-12-12 11:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Markdown file to reproduce the bug (238 bytes, text/markdown)
2021-12-12 09:12 UTC, Kishore Gopalakrishnan 		Details
Screenshot of the way okular renders it (39.80 KB, image/png)
2021-12-12 09:13 UTC, Kishore Gopalakrishnan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kishore Gopalakrishnan 2021-12-12 09:12:56 UTC 
Created attachment 144475 [details]
Markdown file to reproduce the bug

SUMMARY
If a list item begins with inline code, okular incorrectly prints the list index in monospace

STEPS TO REPRODUCE
1. Open the attached file in Okular.

OBSERVED RESULT
The list index '3' in the attached file is printed in monospace, and looks different from the other list indices (attached screenshot)

EXPECTED RESULT
All the list indices should be formatted the same way. This can be seen by pasting the content of the attached file on https://dillinger.io/

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 21.5 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics

ADDITIONAL INFORMATION
Comment 1 Kishore Gopalakrishnan 2021-12-12 09:13:29 UTC 
Created attachment 144476 [details]
Screenshot of the way okular renders it
Comment 2 Albert Astals Cid 2021-12-12 11:24:07 UTC 
Qt bug https://bugreports.qt.io/browse/QTBUG-99148