Quote:
Originally Posted by Jade Aislin
I looked in the developer's section, but all the posts seemed to be about porting already made dictionaries. I'll have to do a more in depth look.
|
Yes, most of the discussion is about converting existing dictionaries. But, I think there is a pointer somewhere in there to what the source dictionary must look like.
Quote:
That looks like it may work. Although, it would have been nice to put the different columns in the details section. I'm having a little trouble finding the mentioned file, but I will post on that thread.
|
Putting the other column info into the details section was the whole point of this. If you look at the screenshot in the
first beta post, it has the rating, word count (from a custom column), last read (from a custom column filled via the Kobo Utilities plugin) and the tags. These are after the existing comment. I probably should have pointed to this post yesterday as it is the start of the discussion and I have realised I might have missed some instructions from the later post.
I assume for the "mentioned file" you are talking about the file with the template. If so, it is a new file that you create. Where it goes is mentioned in the above post.
Quote:
I'm not sure that would work. Each epub have different tags. From what I know of directories, that would mean there would be multiple copies of the book in the different directories. Or am I wrong?
|
Yes and that's one of the problems with directory structures vs tagging. Some people have no problems with having multiple copies of the book in different places. Others would use a primary tag or genre for the directories. Within the Kobo firmware, you can create collections. A book can be in multiple collections. The calibre driver can create these collections based on one or more columns in your library. But, the collections are single level, not hierarchical.