[chaley]

Originally Posted by polarwind

Thanks for the reply. From what you write, and if I understand correctly, I must assume that Calibre does NOT store the edited meta tags in an xml file in the media file. In this case it are all CBR files. This means that other Comic Readers won't see the changes at all.

Calibre stores metadata in some book types at various times that depend on the book type: when converted, when exported, when "polished", etc. In addition, some plugins can store metadata inside a book. One that might interest you is [Metadata Writer Plugin] Embed Comic Metadata

If indeed Calibre is storing the new meta tags in it's own database, only for internal use, then there is no point in updating/correcting the meta data this way. unless I am totally misunderstanding the way this works.

To be sure, calibre stores metadata in its own database. What else can it do? However, as noted above, calibre also stores metadata in some book types. In addition, apps like CC and COPS access the calibre database.

the general idea was to correct the meta data (in case the maker from the CBR files was sloppy or incorrect). I have done this before with editing meta data in an pdf file of a non-DMR protected file. So, if I upload a new book in Calibre and see that the publisher, or series are missing, I want to edit this to correct if possible. Next step is to let FBreader connect to the network database, push the download button in FBreader, and see the same meta tags there once the document is downloaded to the device.

Calibre can natively embed metadata in PDF, EPUB, and many other types. You need to add that "embed" step (however it is done for the type in question) to your workflow. In some cases the process is automatic, such as downloading EPUBs using the calibre content server.

wouldn't it be more logical for Calibre to store the edited meta tags in xml? any other suggestons on how I could let other readers use new data entered in calibre?

No. Calibre must store metadata in the book *in the form that book requires*. In some cases this is XML. In many other cases it is not. For example, EPUB wants the metadata in an OPF file.

Note that your problems are being caused by your insistence that the reader app see the metadata. If you use CC as the library organizer as well as the book downloader then the problem goes away. That is how most people use CC.