Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Konversation Konversation
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NetworkNetwork
  • KonversationKonversation
  • Merge requests
  • !63

Support code for monospace formatting

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Friedrich W. H. Kossebau requested to merge work/kossebau/supportmonospacecode into master Dec 16, 2021
  • Overview 2
  • Commits 1
  • Pipelines 10
  • Changes 5

Using <tt> allows to integrate with the existing code in a simple way. MOTD fixed font support uses another approach, but that would mean messing with the <font> tags, not sure if this is worth that?

Long term I hope I can rewrite the QTextDocument generation to not go via HTML, but directly add 'QText*' classes, and then update styling on text sizes changes (or on planned color theme change) via the 'QText*Format' classes. Might happen in the next weeks, or never ;)

Would %M be a good code for monospace? Other ideas?

@argonel @psn @buschinski

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: work/kossebau/supportmonospacecode