[konsole] [Bug 364992] [Feature request] Add an option to disable the embedded "drawLineChar" mechanism

https://bugs.kde.org/show_bug.cgi?id=364992 --- Comment #4 from Yi Yang --- It's amazing to see some code written 11 years ago which fixes a bug reported 13 years ago can still work. However, as I have argued, the available fonts have changed, and the available screen

[konsole] [Bug 349350] Some monospaced fonts missing in the fonts menu

https://bugs.kde.org/show_bug.cgi?id=349350 --- Comment #3 from Yi Yang --- Also, Konsole is actually sophisticated enough to handle double width characters. No reason to keep the users from actually using such a font. -- You are receiving this mail because: You are

[konsole] [Bug 349350] Some monospaced fonts missing in the fonts menu

https://bugs.kde.org/show_bug.cgi?id=349350 Yi Yang changed: What|Removed |Added CC||ahyan...@gmail.com --- Comment

[konsole] [Bug 364992] [Feature request] Add an option to disable the embedded "drawLineChar" mechanism

https://bugs.kde.org/show_bug.cgi?id=364992 --- Comment #2 from Yi Yang --- Created attachment 99796 --> https://bugs.kde.org/attachment.cgi?id=99796=edit Screenshot showcasing worst-case scenario for the built-in line drawing mechanism The command was echo -e '╫\033[01m╫'

[konsole] [Bug 364992] [Feature request] Add an option to disable the embedded "drawLineChar" mechanism

https://bugs.kde.org/show_bug.cgi?id=364992 --- Comment #1 from Yi Yang --- This should be fairly easy to implement: In TerminalDisplay.cpp, method TerminalDisplay::drawCharacters, there is a if-clause calling isLineCharString(text) to decide whether to draw something with

[konsole] [Bug 364992] New: [Feature request] Add an option to disable the embedded "drawLineChar" mechanism

https://bugs.kde.org/show_bug.cgi?id=364992 Bug ID: 364992 Summary: [Feature request] Add an option to disable the embedded "drawLineChar" mechanism Product: konsole Version: unspecified Platform: Other OS:

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #13 from Yi Yang --- Hi all, I upgraded to Plasma 5.6 today. It seems to be handling hi-res screens in a new way (by handling font DPI better it seems), so that the "scale display" option is no longer needed in most

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #12 from Yi Yang --- Relevant documentations: relevant flags: http://doc.qt.io/qt-5/qt.html QScreen and QPixmap with their new addition in Qt 5.5 or 5.6: http://doc.qt.io/qt-5/qscreen.html

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #11 from Yi Yang --- By reading more documents and doing more experiments, things are now clear. Qt 5.6 introduces a new option, called "High DPI Scaling", which is both controllable form environment variables and

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #8 from Yi Yang --- OK, I digged the source code a bit more. The DPI calculation code at core/utils.cpp line 63-81 returned (93.6, 93.6), while my actual DPI, as reported by Xorg.log, is (187, 189). Apparently

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #7 from Yi Yang --- OK. I tried KDE Plasma 4 + Kdelibs4/Okular. There were no render resolution problem. That said, there were no "scale display" option in systemsettings in this setup. So this might indeed be the

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #6 from Yi Yang --- Every application is, in principle, independent of the desktop environment I use. However, when I'm reporting a bug, I'm trying to include information about my DE. I think this makes sense. In

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #4 from Yi Yang --- Luigi, yes, I am using the Frameworks version of Okular. To be sure this bug is still around I even git pull'ed and compiled it again. So to be precise I'm reporting the newest version of frameworks

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 --- Comment #3 from Yi Yang --- To be honest, your terminology change from KDE 3 to KDE SC 4 to {Insert a myriad names here} 5 is absolutely terrible. I have no idea how to even call it. And, yes, i checked and it is Plasma 5. I

[okular] [Bug 362856] New: [Frameworks] Wrong render resolution, possibly caused by KDE 5 "Scale Display"

https://bugs.kde.org/show_bug.cgi?id=362856 Bug ID: 362856 Summary: [Frameworks] Wrong render resolution, possibly caused by KDE 5 "Scale Display" Product: okular Version: unspecified Platform: Other OS:

[okular] [Bug 359223] [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)

https://bugs.kde.org/show_bug.cgi?id=359223 Yi Yang changed: What|Removed |Added CC||ahyan...@gmail.com --- Comment