View Single Post
Old 12-05-2022, 04:55 PM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Therein lies the rub. There is no standard.

Calibre appears to be using stuff from an old Google Code page (https://github.com/kovidgoyal/calibr...e.py#L126-L201).

What you see in Nickel barely has any bearing on this, though, as it's just the Kobo driver poking at the Nickel db to update the metadata fields based on the metadata in the Calibre db (which is something entirely different than how a file itself might embed metadata).

Nowadays, the most common metadata format in use is probably the ComicRack one, but apparently we're in XKCD #927 territory (c.f., https://github.com/anansi-project/rfcs).

Last edited by NiLuJe; 12-05-2022 at 04:57 PM.
NiLuJe is offline   Reply With Quote