Originally posted by avis
View Post
Originally posted by xfcemint
View Post
"properly antialiased" that the biggest problem. Wayland scaling solution was design while freetype was blocked by patents from having anti-aliasing. Blur of frational downscaling * Blur of anti-aliasing fonts=too much blur. Yes one or the other equals not jagged fonts.
I never said you need a 300dpi monitor.
Originally posted by avis
View Post
Firefox had in fact implemented the core bit for application fractional scaling under Wayland 19 months ago. Yes the manual setting of firefox scale was hiding under about:config instead of environmental var. The stall was getting agreement on what protocol extension for sending fractional scale information to applications should win for automatic setting of this value.
avis I did say a while back firefox under Wayland had fractional scaling to you and that the hold up was agreement on protocol. Of course firefox still will need the final patch making application fractional scaling controlled by the protocol extension that won.
avis I have a 1080p monitor that due it size has a odd DPI. Guess what there are lots of applications that don't like that monitors DPI value and either don't scale or don't run with X11. So a single monitor setup can be hell. Yes a 1080p monitor that is only 30cm wide. Yes it not technically hidpi and it not technically lowdpi is that nice nasty middle ground. So application side scaling does not always work.
The reality we need both. Integer upscale and down scale to fractional for applications that cannot scale self correctly with the price of some blur. And applications that can be able to scale self.
Issue here X11 dpi work around was only half the fix and Wayland integer up fractional down was also only half the fix.
Comment