View Single Post
Old 09-05-2010, 05:24 PM   #21
KACartlidge
Author
KACartlidge began at the beginning.
 
Posts: 12
Karma: 24
Join Date: Aug 2009
Device: Sony Reader PR505
Thanks for the test files; I'll try them tomorrow on my colleague's K3.

One issue with this though is that you are relying on Calibre to do a conversion.

My original post is dealing with the fact that Amazon state RTF is supported (whether natively or converted as it is sent) and yet the metadata is ignored, at least on files I tried so far. The fact that a third party application can retain the metadata as it creates mobi files ready for the Kindle is not really the issue - you are feeding the Kindle a mobi not an RTF so the result has no bearing on the Kindle's handling of RTF but rather on its handling of Calibre's mobi output.

Could you clarify your comment confirming that the Kindle cannot read RTF and requires a mobi conversion?

It is possible to pass an RTF directly to the Kindle account without converting into any other form. The Kindle sees it and shows it fine (minus metadata). It may well be that upon arrival we have a mobi internally, but the actual file sent to the Kindle is RTF not mobi, there is no Calibre involvement, no conversions. And the Kindle is fine with that (apart from the metadata of course).

Incidentally, directly sending the RTF you gave to the K3 will not help as the \info tag does not contain a \title entry - your Calibre conversion process is probably adding the Title to the mobi metadata.
KACartlidge is offline   Reply With Quote