libappstream-glib/as-node.c | 36 36 + 0 - 0 !
libappstream-glib/as-self-test.c | 16 16 + 0 - 0 !
2 files changed, 52 insertions(+)

 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

libappstream-glib/as-node.c | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 properly initialize asnodetoxmlhelper

Bug: https://github.com/hughsie/appstream-glib/issues/445

libappstream-glib/as-node.c | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 trivial: turn is_{em,code}_text fields into bitfields

libappstream-glib/as-node.c | 108 64 + 44 - 0 !
libappstream-glib/as-self-test.c | 39 37 + 2 - 0 !
2 files changed, 101 insertions(+), 46 deletions(-)

 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.