View Single Post
Old 06-30-2014, 10:01 AM   #850
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,816
Karma: 6000000
Join Date: Nov 2009
Device: many
Hi tkeo,

Quote:
Originally Posted by tkeo View Post
Your are quite right. Retrieval of original idrefs causes much complication of the code; however, I'd like to keep it in KindleUnpack, in order to reconstruct the source more precisely.
In addition, to get cover page creation condition needs skelid in RESC and part in k8proc.
But why keep it? The idrefs are just temporary tags and they are truly meaningless in that they convey no information other than uniqueness. They don't help make reconstructing the source more precisely since any unique id work to do that. You can not use them to deduce anything new that we actually need.

That means the code that tries to generate uniqueness of idrefs is just a source of potential problems, and adds code complications and code size for no true added benefit. Please remove it unless you can demonstrate that using the idrefs actually improves functionality in some way. For the cover, you can parse the idref and then let opf give it our own unique idref with no extra code.

Thanks,

KevinH

Last edited by KevinH; 06-30-2014 at 10:20 AM.
KevinH is offline   Reply With Quote