Just out of curiosity, what happens if you use dconf-editor to got to
org.gnome.desktop.interface and tweak text-scaling-factor and
scaling-factor?
The only good solution to this problem is to make universal
accessibility a design objective. There are so many things that are
accessibility things that get ignored or designed out and they would be
*awesome* for everyone. Text and UI scaling is for low vision, but is
for everyone on highDPI displays. Speech dispatcher and voice
recognition is for blind users, but is for everyone as part of a GPS
navigation system you can use when driving. The bindings that let Orca
work are used for automated testing and could be used for voice
activation of the UI. etc. If it is designed to be inclusive of everyone
then it is better for all of us (which I just typed without noticing at
first is pretty close to the meaning of the word "ubuntu").
Alan.
On 28/04/16 14:10, Stephen M. Webb wrote:
Most desktop apps were designed for last century's hardware and assume a
display with 96 pixels per inch. Today's 4k
displays and pocket computer screens run at about 300 pixels per inch or
better. That means when you open up a legacy
application from last century on your phone or tablet screen, it's going to be
teeny tiny. We're working on trying to
upscale automatically, but (a) upscaling will look less than satisfactory and
won't be pixel-perfect and (2) there isn't
enough screen real estate to show everything when upscaled.
You'll find the legacy apps look OK on a large external monitor with a
traditional legacy pixel density.
The only good solution to this problem is to bring the apps forward to 2016 and
port them to run natively. That's up to
the app developers.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
