https://bugs.kde.org/show_bug.cgi?id=382526

            Bug ID: 382526
           Summary: Peruse 1.2 & master don't support ACBF metadata, and
                    sometimes crash
           Product: peruse
           Version: master
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: ad...@leinir.dk
          Reporter: b...@ancilla.ca
  Target Milestone: ---

Tested with both Peruse 1.2 and master, with and without baloo enabled.

For test files, I used:
- a CBZ created by hand, with a hand-written ACBF file;
- a CBZ created using perusecreator;
- and the two volumes of Pepper & Carrot that the Peruse commit log says were
used as test cases for ACBF support.

In both versions, ACBF metadata does not appear to be used at all. I can see,
in the terminal, a huge number of logging messages from
AdvancedComicBookFormat, e.g.

```
bool AdvancedComicBookFormat::Sequence::fromXml(QXmlStreamReader*) Created
sequence entry, which places this book as number 2 in the series "Pepper &
Carrot"
bool AdvancedComicBookFormat::Author::fromXml(QXmlStreamReader*) Created author
"David" "Revoy" "" responsible for "Writer" for language ""
bool AdvancedComicBookFormat::BookInfo::fromXml(QXmlStreamReader*) Created book
information for the book with the titles ("Pepper & Carrot - Vol. 2", "Pepper &
Carrot - Tome 2", "Pepper & Carrot - Zväzok č. 2")
```

but this isn't reflected in the UI; "group by author" does nothing, "group by
series" groups by the directory the CBZ files are in, and "group by title"
groups by the file name, the same as for non-ACBF books.

It is especially disheartening that Peruse can't even read ACBF files that it
itself generates.

Peruse master, additionally, sometimes crashes when attempting to display the
info panel for ACBF books. When it doesn't crash, it shows as up "publisher
unknown, author unknown, no description", same as 1.2 and same as non-ACBF
books.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to