View Single Post
Old 01-06-2021, 11:21 AM   #2
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,097
Karma: 92190113
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
I did some limited testing of this and as far as I can tell exact="yes" does nothing, despite being documented in the Amazon Kindle Publishing guidelines.

More details:

I created a short test dictionary using the example of exact="yes" from the Amazon Kindle Publishing Guidelines section 15.4.2 (Exact-match Parameter) and compiled the dictionary using kindlegen 2.9. I then modified the source to remove exact="yes" and compiled it again.

The only differences in the resulting MOBI dictionary files were in metadata that always changes (creation time, modification time, book version, and container ID). There were no differences in the actual content of the file. This indicates that the "exact" attribute is ignored by kindlegen.

I also tried this with Mobipocket Creator 4.2 and had the same result.

Last edited by jhowell; 01-06-2021 at 12:23 PM.
jhowell is offline   Reply With Quote