[packagekit] RFC: Markup format

Sebastian Heinlein glatzor at ubuntu.com
Wed Dec 17 14:55:48 PST 2008

Am Mittwoch, den 17.12.2008, 16:23 +0000 schrieb Richard Hughes:
> At the moment we expect the backend to send the daemon "raw text" and
> for the front-end to do something sensible which involves munging
> character sequences without breaking things. There's no encoding
> specified, nor is it common between gpk-application, gpk-update-viewer,
> or KPackageKit. It sucks.
> One place where we might want a little bit more cleverness is for the
> update or package descriptions. These sometimes need bold text, links,
> or bulletted lists. Example screenshot attached.
> Now, I think it's pretty insane for the engine or backend to try to
> parse the update data into some sort of XML, but I do think we can be a
> little clever and at least provide a way for the text to look pretty for
> the end users.

I am against using a special markup. Most frontends use pango and so
pango markup seems to be the natural choice to me.


Why should the frontend/client convert markdown to pango markup?



More information about the PackageKit mailing list