Standard ebooks translator field in calibre

[shikamer]

Hi guys,

Can someone please guide me on how to display the standard ebooks metadata on calibre, especially the translator names. I have set up a custom column (translators) and also tried the extended metadata plugin, but I'm unable to see them.

[theducks]

Originally Posted by shikamer

Hi guys,

Can someone please guide me on how to display the standard ebooks metadata on calibre, especially the translator names. I have set up a custom column (translators) and also tried the extended metadata plugin, but I'm unable to see them.

Did you set that column to be shown? Preferences: add your own columns: <tick the boxes for those you want to see>

[shikamer]

Originally Posted by theducks

Did you set that column to be shown? Preferences: add your own columns: <tick the boxes for those you want to see>

Yes, I can see the translators I have added myself but not the ones in the standard ebooks ones.

[BetterRed]

Moderator Notice
Moved to it's own thread - the thread where you posted is a weed bed, where things are apt to get lost or become entangled.

Baseline calibre will not populate custom columns when books are added, nor will a metadata source plugin, has to be done with a user interface plugin.

BR

[shikamer]

Hi, thanks for the tip.

So I asked chatgpt to write one for me and it wrote this script:

from calibre.customize import MetadataReaderPlugin
from lxml import etree
import re

class TranslatorsPlugin(MetadataReaderPlugin):
name = 'Translators Metadata Plugin'
description = 'Extracts translator names from OPF and stores them in #translators'
supported_platforms = ['windows', 'osx', 'linux']
author = 'ChatGPT'
version = (1, 2, 0)
file_types = {'opf'}

def read_metadata(self, stream, metadata):
tree = etree.parse(stream)
translators = []

# Match all meta tags refining any #translator reference (#translator, #translator-1, etc.)
for meta in tree.xpath('//meta[@property="se:name.person.full-name" and starts-with(@refines, "#translator")]'):
if meta.text:
translators.append(meta.text.strip())

# Fallback to generic <meta name="translator">
for meta in tree.xpath('//meta[@name="translator"]'):
if meta.get('content'):
translators.append(meta.get('content').strip())

# Fallback to <dc:contributor opf:role="trl">
for node in tree.xpath('//dc:contributor[@opf:role="trl"]',
namespaces={'dc': 'http://purl.org/dc/elements/1.1/',
'opf': 'http://www.idpf.org/2007/opf'}):
if node.text:
translators.append(node.text.strip())

if translators:
metadata.set('#translators', ', '.join(sorted(set(translators))))

return metadata


In the opf file, the translators are like this:

<dc:contributor id="translator">Gilbert Murray</dc:contributor>
<meta property="file-as" refines="#translator">Murray, Gilbert</meta>
<meta property="se:name.person.full-name" refines="#translator">George Gilbert Aimé Murray</meta>
<meta property="se:url.encyclopedia.wikipedia" refines="#translator">https://en.wikipedia.org/wiki/Gilbert_Murray</meta>
<meta property="se:url.authority.nacoaf" refines="#translator">http://id.loc.gov/authorities/names/n79043229</meta>
<meta property="role" refines="#translator" scheme="marc:relators">ann</meta>
<meta property="role" refines="#translator" scheme="marc:relators">trl</meta>
<meta property="role" refines="#translator" scheme="marc:relators">wpr</meta>

But it's still not working. Can you point me in the right direction?

[JSWolf]

Originally Posted by shikamer

Hi guys,

Can someone please guide me on how to display the standard ebooks metadata on calibre, especially the translator names. I have set up a custom column (translators) and also tried the extended metadata plugin, but I'm unable to see them.

Do you realize how bad the code is that StandardEBooks use is? I would stay away from them. Use the library here at MR.

[PeterT]

Originally Posted by JSWolf

Do you realize how bad the code is that StandardEBooks use is? I would stay away from them. Use the library here at MR.

This is the same as arguing that because program XYZ is written poorly (meaning in a manner YOU wouldn't), one shouldn't use it.

Seeing all that the majority of people CARE about is reading the WORDS in a book, how they are coded to present that is totally irrelevant.

[JSWolf]

Originally Posted by PeterT

This is the same as arguing that because program XYZ is written poorly (meaning in a manner YOU wouldn't), one shouldn't use it.

Seeing all that the majority of people CARE about is reading the WORDS in a book, how they are coded to present that is totally irrelevant.

Most of these eBooks do not need a complex layout. They should work with RMSDK on a Kobo. But they don't because the code is that bad. They don't work on some ePub3 compatible programs because they use code that is not really supported.

[theducks]

Peters argument still holds.
If it WORKS, most don't care if it is ugly or inefficient code.
For what I read, I do not need:
EPUB3
HiRes covers
A High retail price (fiction bits weigh the same as non-fiction bits) Shipping cost should have reduced the production cost while the authors and editor still got paid well. $10 for what was a $5 paperback that had to be shipped and shelved at my local store.

[shikamer]

For those who face the same problem, the author of extended metadata plugin has released a fix here:
https://www.mobileread.com/forums/sh...61#post4543561