View Single Post
Old 05-25-2012, 12:25 PM   #2
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,094
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by hd_cal_dave View Post
As I understand it, the Calibre pubdate field (or any date based field) cannot handle books created BC. I have a number of ancient texts and would like to track this year.

So I have added a "First Published Year" field to my library and will have it hold a simple integer where negative numbers mean B.C. This is working well, but I see that each custom column has a "formatter" associated with it for pretty printing the value.

Doesn't anyone know the Python I'd have to create to turn my year number into something nice (for example):

-999 -> "1000 BC"

234 -> "234 AD"

I'd like to still sort on the internal integer value however.
as long as you do an ASCII sort with Leading Zero's one or the other will sort

The issue with BC is it an Ascending value the more it gets away from the Year 1.
The problem is the BC value sorts next to AD
0234AD
0234BC
1000AD
1000BC


You really need to use Signed numbers (forget about the AD/BC)

Maybe a Export template could made to drop the - Sign and ad the BC suffix
theducks is offline   Reply With Quote