GitLab

REVIEW: 118950

And prepare for 4.14 beta 1

Conflicts:
	VERSION
	active/app/package/metadata.desktop
	core/version.h

BUGS: 334611
REVIEW: 118171
FIXED-IN: 4.13.2

Needs poppler 0.28 that is yet to be released

BUGS: 317891

No other parts which renders PostScript are available at the moment,
and parts which handles them are return "unexpected" resultS (e.g.
katepart: PostScript source code).

Reviewed by: Albert Astal Cid

BUG: 284428
FIXED-IN: 4.13.2

- use proper HTML tags so that it is easy to read complex messages
- remove one unused string
- minor string fixes

- Initialize the kpsewhich QProcess in the fontLocate() method
- Remove the usage of fontProgressDialog and use the warning
  signal to notify the user on the status of font generation.
- The change makes it "easier", in future, to kill the font
  generation when the user opens a new document. Right now it
  is not possible to stop the generation.

Reviewed by: Albert Astal Cid, Fabio d'Urso
(and thanks for the hints!)

If a "fast" sequence of signals is sent to the part, the hiding
animation could lead to a broken resize (as it the new message
is handled during the resize). Remove the animation for now.

Less widgets in generators/core \o/

Those two categories are usually longer messages and more
important, so more fit for a (new) KMessageWidget; simple
notice signals still go to PageViewMessage into PageView.

A more general review of all the messages should be probably
performed in order to assign proper categories to them.

Reviewed by: Albert Astal Cid

Doesn't make any sense, why would we want a "running searches map" if we
always reset the previous one?

BUGS: 334568
FIXED-IN: 4.13.2

Doesn't make any sense, why would we want a "running searches map" if we
always reset the previous one?

BUGS: 334568
FIXED-IN: 4.13.2