I tried running the gs command on Windows box, using gswin64c.exe. I specified -sFONTPATH=C:\WINDOWS\Fonts. Now the file is a lot larger . This also works fine on my K3. Try if it works for you.

It might be interesting to notice that when I didn't specify -sFONTPAPTH in windows, it said that it also replaced Times with Nimbus, but the resulting file didn't show (ğ,ş,İ,) when I opened it in windows (I use Foxit Reader), so I didn't bother testing that on K3.

Regards,
Kai771

this one is more accurate since it has the "İ" in the title. but the same problem is still exist.

When I try to open my test file I noticed that it crashes quickly too. Hence I think it is related with the number of pages ??? (since for large number of pages it acts normally)

EDIT: I confirmed that it is related with the number of pages by just combining this seperate pages into one PDF. (in this case it displays correctly)

Yeah, because it embeded the real TimesNewRoman font . The first version embeded NimbusRomNo9L as a substitute.

Btw, this goes without saying, but just in case someone might misunderstand... the TurkishCharacterTest-win.pdf I made using windows out of convenience - it can be as easily created on Linux too, but one would have to point to the dir that contain the needed fonts. It's easier to do so on Windows, because all fonts are (usually) in the C:\WINDOWS\Fonts. If I understood correctly, gs will not look into subfolders, so on Linux you'd have to copy all the fonts you want to use to a single dir. And of course, there's no TimesNewRoman on Linux (usually), so you'd have to copy it there from a Windows box.

On the other hand, on Windows, normal Ghostscript installation won't add gs to the path, so you'll need to specify the full path when invoking the command.

If I understood you correctly, it works for you too if the document has more than 1 page? If so, I'm glad you were able to sort it out.

No, "new" means "other than old", i.e. different from the previous release by new features and bugfixes (see ChangeLog). Support for touch is not amongst the new features of this release. For that you will need to wait a little bit.

If you start kindle pdf viewer with shift p k (kill framework) after a stand-by period "going into screensaver" message pops and it never goes away. I mean the screen saver is never displayed. Though the kindle goes to sleep and you have to wake it to continue reading by slider.

If you start kindle pdf viewer without killing framework, the screen saver is displayed fine.

hello,
I have the same problem but I think screen savers is not really important for kindle! having no screen saver is not harmful for kindle screen pixels. even if it shows the "going into screensaver" message for a long time it's not an issue. am I right?

hello,
I have the same problem but I think screen savers is not really important for kindle! having no screen saver is not harmful for kindle screen pixels. even if it shows the "going into screensaver" message for a long time it's not an issue. am I right?

Because the native framework is in charge of the screen saver, so if you killed it on start, you wont get any screen saver anymore.

Screen saver is just cosmetic I think. So not showing it won't do any harm to the screen.

Not having screensaver image is a feature, not a bug, because it allows you to see what was the previous battery state _before_ waking up the Kindle and then compare with the current state and analyze (mentally) battery's performance. (Or you can remember to press Alt-. to do this automatically and then open the file kindlepdfviewer/batlog.txt in KPV to see the actual data)