In D25339#665351, @xuetianweng wrote:

... or you could give me some hint on that?

Too bad I can't; it's been no more than a month since I began my study into KDE applications. I'd love to test out if someone provides a genius solution, though.

I second the as-an-option proposal. Hey, why not automatically increase the line height when CJK characters are detected?

In D25339#663322, @rjvbb wrote:

but that's hardly the domain of application for a text editing framework.

lg is, in fact, the ISO standard[1]. However, log_10 is the least ambigious. The length looks fine. We have a x*10^y after all.

Use this as parent of QShortcut

Thanks :D see you at libksane!

So I tested this, great improvements regarding line height can be seen:

Of course it's possible, by using <sub>:

No, I do not have commit rights. I actually changed the email on bugzilla recently (but not on phabricator as it seemed impossible to do so w/o sysadmin's manual intervention), so to avoid confusion, it's fkfd@macaw.me. The name should be "Frederick Yin". Thanks!

GNOME calculator: https://upload.wikimedia.org/wikipedia/commons/4/40/GNOME_Calculator_3.14.90.png

I would set the shortcut directly to the button with setShortcut(...)

Unified changes

@sars As you said, I assigned ctrl+p and ctrl+s to preview and scan respectively in libksane along with tooltips (i18n will need to catch up with this, I think). I used QShortcut; poke me if there's a better way. The snippet looks like this:

I have obtained the source of libksane and located the strings. Should I try binding Ctrl+C to the button? If I did, how do I include the fresh build of libksane in (also freshly built) skanlite?

Some janitor work from a minor annoyance tracing back to 2017.

• Remove confusing comments and unnecessary KIO::StatJob

Cool, got it. Will revise that tomorrow.

All unit tests (i.e. one) passed, and I have tested this on all save-as cases I can think of. Thank you for reviewing this patch!