-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing glyphs (⎛, ⎞, ⎝, ⎠, and ⋅) cause apparent alignment issue in SageMath with unicode_art in Cool Retro Term #88
Comments
Never mind. Got it. |
@rbanffy You could have been right about the fallback font. I just checked Fixedsys Excelsior and the glyphs involved are included in that font even though it has problems. Still strange how I don't have problem with other terminal emulators though. |
Maybe the other terminals just render in grids while KDE4's QTermWidget don't do that. And when you fallback to font with different size (which is probably always the case) the problem naturally arises. |
Found something interesting (we'll have to pass this, maybe, to the QTermWidget team). Note how the parentheses components mismatch below: (added capture, Mac running X server, Linux laptop running Konsole): konsole-misalignment.movIt doesn't happen when Konsole uses the default font. Can you check it with the other fonts you mentioned, @kaimers? |
Reported it at https://bugs.kde.org/show_bug.cgi?id=433604 |
@rbanffy I did tests on QTerminal and KDE 5's Konsole. KDE 5's Konsole: No alignment issue with either IBM 3270 or Fira Code. The behavior in your capture is really weird but I don't think KDE is in charge of QTermWidget, it seems to be maintained by LXQt(https://github.com/lxqt/qtermwidget) |
Problem seen in QTerminal too, which is also based on KDE4 Konsole derived qtermwidget, but not in KDE5 Konsole or Gnome Terminal.
Other font that has this problem are Inconsolata and Ubuntu Mono, but the same problem does not appear with font Andale Mono, Courier, Fira Code or Source Code Pro.
The text was updated successfully, but these errors were encountered: