Quote:
Originally Posted by BaronKrause
Oh man that would've been so cool. I just tested it and it with an Integer set as v{0:d} to create a number that looks like "v2" for instance and it worked, but when I use that field in Calibre Companion's custom naming template, it only shows the number. I'm assuming the custom number formatting is just a change to how that number is displayed locally.
For now it seems i'm sticking with a Version column set to a Long comment like text field, and just type in things like "v2" so that way Calibre Companion will show that at the end of a file name when formatted with " {#version}" at the end of the template (If I were to use v{#version} in CC's text field, if there isn't a version number, it would still show a space followed by a "v" with no number at the end of every file).
Much rather do an Integer (or even floating point, though it would be wasted for this field) but the way its displayed is the most important thing about this one as I really would never need to sort by revisions of various community translated works.
|
Ah, too bad. I don't use Calibre Companion so I didn't know.
One thing you could do that may be easier to use is using a column of type "text, but with a fixed set of permitted values" and use
as values for example
This way you type it only once and the next time you only have to select the value you want.
And this way you can even sort (
even if it's useless!)