View Single Post
Old 09-25-2014, 02:02 PM   #24
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,467
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by chaley View Post
I am looking for some way to deal with the word wrapping issue. One thing I am considering is turning all the dots into spaces so Android would have somewhere to wrap other than in the middle of the word. Unfortunately there are two problems:
1) A.B would become the same as A B. I suspect that CC would fall over dead if this happened.
2) I would need to process the tags in book details so that A.B actually searched for A B if clicked.
Quote:
Originally Posted by kaufman View Post
Is it possible that your solution for the second part will also be applicable to the first one?

I have to tell you that as soon as I read the first quote I started a little timer in my head for how long before you posted that you had figured out a way to do it.
I have thought about this all day and don't have any reasonable solution.

Calibre ensures that there are no duplicate items (tags or otherwise) in a field for a book. As soon as one changes the value for a tag that guarantee is out the window, which means that CC would need to be prepared to find multiple items with the same value. Today it isn't prepared to do that. Of course I could use some kind of disambiguation such as adding the primary DB key to the item, but that is a) very ugly and b) hard to read. I have up-to-now rejected the idea. The base item value (the tag) is a better solution than that. Other disambiguation schemes have similar problems, changing the value of the item in question.

And in any event, I have already exceeded the time I am willing to spend on this feature, so it is staying like it is.
chaley is offline   Reply With Quote