Various typesetting quirks for certain combinations of formatting elements in Markdown comments #1282
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#1282
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Certain combinations of formatting elements, in display of existing issues, lead to unappealing typesetting, as managed by style definitions.
Environment
codeberg.org
, at time of posting.The issue relates to typographic display. Included at the end of the post is a sequence of screen captures intended to show system settings that may affect such display.
Details
A few quirks of formatting style were noticed when reviewing a post recently submitted to the issue tracker.
They include the following, as may be seen in the below screen capture (see highlighted area):
Appendix
See below for screen captures representing relevant display settings.
Thanks for providing details for each step.
I don't think this is an issue. It is normal, and in most places, you will see some space in it.
Valid point
Valid point
Now, onto the actual bits: we are using the https://github.com/noties/Markwon library for rendering Markdown. We have extended it a bit to add a few GitNex related features. However, these basic fixes should be done upstream.
I'm also not sure if the library is maintained anymore; the last release was in 2021.
Does the library support custom styling? Could you render in a web display pane, first converting to a representation in HTML?
Nextcloud Notes is an example of an Android application under active development that displays Markdown text. Recent versions even have a WYSIYG editor.
The first issue looks quite awkward to me, and not as formatting to which I am accustomed.
Various typesetting quirks appear for certain cominations of formatting elementsto Various typesetting quirks for certain combinations of formatting elements in Markdown commentsNextcloud Notes is using the same library with modified tooling, and they have their own set of UI nitpicks.
To each their own; to me, these are not issues, just UI nitpicks, and I am personally fine with them.
However, to accommodate/fix these, I would advise opening an issue on the upstream project for the fixes.
Library examples: https://noties.io/Markwon/#supported-markdown-features
The screenshots for Markwon show code spans formatted with background highlighting, making the excessive white space seem more natural. Most of the space is within the highlighted box, and therefore the space between its edges and the surrounding text is quite minimal.
Could I also mention inline code in headings being paragraph-sized? Example: https://codeberg.org/foxy/visimp. Are links not automatically detected if MD link syntax is not used on purpose?
#1342 will address most of the UI MD issues.
@foxy I did not really understand your request or issue. Can you please add screenshots maybe to clarify it?
If needed please open a new issue.
Here it is: inline code + h1.
I am assuming hello and world should be the same size.
Yes, it should be.
This is also fixed in the PR I mentioned above. All these issues related to MD are fixed in it.