Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
Support-em-code-tags.patch | Support em/code tags Some appstream-data packages add <em> and </em> or <code> and </code> to the files. Not all package manager can handle that. An example would be pamac from Manjaro |
=?utf-8?q?Philip_M=C3=BCller?= <philm@manjaro.org> | no | debian | https://github.com/hughsie/appstream-glib/pull/403 | 2021-06-14 |
Properly-initialize-AsNodeToXmlHelper.patch | Properly initialize AsNodeToXmlHelper | "Jan Alexander Steffens (heftig)" <jan.steffens@gmail.com> | yes | debian upstream | https://github.com/hughsie/appstream-glib/pull/446 | 2022-07-15 |
trivial-Turn-is_-em-code-_text-fields-into-bitfields.patch | trivial: Turn is_{em,code}_text fields into bitfields | "Jan Alexander Steffens (heftig)" <jan.steffens@gmail.com> | no | debian | https://github.com/hughsie/appstream-glib/pull/446 | 2022-07-15 |
Improve-handling-of-em-and-code-tags.patch | Improve handling of <em> and <code> tags This is still not great code but at least somewhat an improvement. Tests were expanded to showcase the new behavior. I think, ideally, we would append opening/closing tags to the ancestor `p` or `li` node's cdata as soon as we encounter the start/end of an `em` or `code` element. This would then also handle empty elements correctly. |
"Jan Alexander Steffens (heftig)" <jan.steffens@gmail.com> | no | debian | https://github.com/hughsie/appstream-glib/pull/446 | 2022-07-15 |