View Single Post
Old 02-18-2015, 09:53 AM   #1515
yecam
Enthusiast
yecam began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Feb 2009
Device: BeBook
99 percent working now

@NiLuJe

That little fix corrected the brain fart problem Once I appended .6 to the library name and enabled the personal information option I was able to restart the framework and see my information in the banner at the bottom of the cover page when in sleep mode.

Corrected my original comments in the message as I figured out where I was going astray.

After looking at the source code for cover-extract I figured out why my personal information was being displayed in a very strange format. My personal information consisted of a short message starting with "If found, please return ......" The software in the code first looks for a file named pinfo.png in the cover_cache directory containing the personalized information and if it does not find it looks in the linkss base directory for a file named pinfo_header. If this is not found then the software generates the pinfo.png file by pre-pending the existing personal information with the following text: "If found, please contact:" Imagine my surprise when I started seeing this text repeated twice, once from the software generated logic and once from my original stored data.

The solution for me was to first simplify me stored personal data to just my name, email address and phone number. Then I manually deleted the pinfo.png file from the cover_cache directory and finally I performed a framework restart.

All is well now.

I never did find a file in the linkss base directory named pinfo_header. I believe that the design intention here is for the user to manually create this file if something other than the official KINDLE personal information is desired. Otherwise you get the official Kindle information pre-pended with a hard coded string as I have seen.

If my assumption is correct then we need this little gem documented. I am willing to generate the verbage but would first like to get the design intent confirmed. For me, things are now working but I would not have been able to figure this out without first looking at the source code.

Last edited by yecam; 02-18-2015 at 10:47 AM. Reason: Removed original incorrect information
yecam is offline   Reply With Quote