https://bugs.kde.org/show_bug.cgi?id=390307
Friedrich W. H. Kossebau <kosse...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Friedrich W. H. Kossebau <kosse...@kde.org> ---
I have no own experience yet with support of high-dpi devices yet, so can only
do guesses based on docs.
The CSS used for the markdown rendering has all sizes given in pixels, cmp.
https://kevinburke.bitbucket.io/markdowncss/markdown.css
I picked that stylesheet as it seems a good one, and having no designer
education myself, I also do not want to start messing with CSS :)
That CSS is currently hardcoded, but happy to add support to allow people
overwriting that, see https://bugs.kde.org/show_bug.cgi?id=385219
The openSUSE packages are built against Qt WebEngine. That one recommends to
have Qt::AA_EnableHighDpiScaling set in the code, so things are properly scaled
given that web rendering by standards is based on 96 dpi IIRC.
Cmp. http://doc.qt.io/qt-5/qtwebengine-overview.html#high-dpi-support
Kate itself seems to not set that flag in the code yet, grepping the code yield
no hit.
Questions:
a) What do you mean exactly by "system is set to only have forced DPI of 168
while scaling factor is 1." ?
b) Could you try to run Kate with QT_AUTO_SCREEN_SCALE_FACTOR set to TRUE in
the environment and tell if this improved things for you?
E.g. by opening a terminal and starting kate like this
```
export QT_AUTO_SCREEN_SCALE_FACTOR=TRUE
kate
```
Cmp. also http://doc.qt.io/qt-5/highdpi.html
If that improves things for you, it would then make sense to add code to Kate
to set the respective flag directly.
--
You are receiving this mail because:
You are watching all bug changes.
