Quote:
Originally Posted by chaley
There be both dragons and opportunities here.
<snip>
The reasons for database limitation relate to how metadata is exchanged between these devices and calibre. It goes back and forth several times during the cycle. Changing this to use plugboards both directions would be extremely complex, and isn't something I am willing to attempt.
Comments?
PS: given that I handle the sony driver, I could in fact build plugboard processing into the sony driver's database manipulation code. Two things bother me. The first is that the other DB-driven devices would behave differently, which is probably not a big deal. The second is that it would need to be absolutely right the first time, no corner cases, so that people who do manual management don't lose information.
|
Oh, I never talked about how to implement a scheme like this, it was just an idea I got when I started working with those fields... And how it would fit my way of working
You do raise some major objections, which I never thought off (but then, I've never looked into the code of Calibre...)
But a girl can dream, can't she? Besides, I know from personal experience, that a suggestion can have some far-reaching consequences as it will rattle around inside your brain and maybe trigger a brilliant idea.
Oh, the major problem I saw were circular references...
Create a custom colum "new_title"
{author} - {title}
and then use {#new_title} for your {title}...