09-21-2010, 10:42 AM | #16 | |
Guru
Posts: 610
Karma: 1395952
Join Date: Jul 2008
Location: New York
Device: Oasis 3 & GlowLight 4
|
Quote:
Garamond and E-Ink don't seem to play nice. ArnoPro has a similar (tall serif) look, and it displays well on my Opus, so I'm curious how it would look on a Kindle 3's Pearl screen. |
|
09-21-2010, 10:45 AM | #17 |
Resident Curmudgeon
Posts: 75,851
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Fontin is a rather nice font.
|
09-21-2010, 10:48 AM | #18 | ||||
I'm Super Kindle-icious
Posts: 6,734
Karma: 2434103
Join Date: Apr 2008
Location: Long Drive, Calinadia Candafornia
Device: KDXG, KT, Oasis
|
Quote:
Quote:
Quote:
Quote:
I also saved an original copy of the reader.pref file (renamed reader.pref.original) that I saved in a separate directory on my in case I messed up when editing. I have noticed that after the font change fails and I go back to check the reader.pref file, the lines have been rearranged from the original. Does that matter. |
||||
09-21-2010, 11:21 AM | #19 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@daffy4u: Yeah, that usually means that the Reader booklet was somehow still open. Staying only on the Home screen usually takes care of that, that's weird... AFAICT, it shouldn't change a thing, but on which FW version are you? I only tried this on 3.0.2.
@all: Fonts without/with crappy TrueType hinting instructions may look way fuzzier than they did on the K2. |
09-21-2010, 11:24 AM | #20 |
plus ça change
Posts: 101
Karma: 32134
Join Date: Dec 2009
Location: France
Device: Kindle PW2, Voyage
|
Seriously... I've just tried Garamond Pro and Minion Pro (two of my favourites) on my K3, but they both look terrible, except on the two largest point settings. But then they're too big for me.
Curious to hear how Arno Pro works out for you. veezh |
09-21-2010, 11:24 AM | #21 | |
I'm Super Kindle-icious
Posts: 6,734
Karma: 2434103
Join Date: Apr 2008
Location: Long Drive, Calinadia Candafornia
Device: KDXG, KT, Oasis
|
Quote:
I'm going to hold off until the regular font hack is ready. Thanks for trying to help me. |
|
09-21-2010, 11:47 AM | #22 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@daffy4u: The only other thing I can think of is notepad++ putting crap in the file... Like converting UNIX line-endings to DOS or MAC line endings, which would explain why it upsets the Reader.
Last edited by NiLuJe; 09-21-2010 at 11:56 AM. |
09-21-2010, 12:17 PM | #23 | |
I'm Super Kindle-icious
Posts: 6,734
Karma: 2434103
Join Date: Apr 2008
Location: Long Drive, Calinadia Candafornia
Device: KDXG, KT, Oasis
|
Quote:
Maybe someone could make a quickie YouTube video walking through the steps. I swear this was the last time trying this. (I probably will try again but not today) |
|
09-21-2010, 04:39 PM | #24 |
Member
Posts: 24
Karma: 22
Join Date: Apr 2010
Location: New York
Device: Kindle 3
|
Making the changes in notepad.exe will definitely not work. When you press "Enter" in notepad, or in many other windows tools, it will insert two characters, a Carriage Return <CR>, as well as a Line Feed <LF>.
If you're unfamiliar with this, think about a real-life typewriter. A <CR> simply returns the carriage to the beginning of the line (the one you've presumably already typed on), and a <LF> will simply move down a line (you'll still be in the same column). When in a Windows program like notepad, the return key will actually insert both of these characters automatically, one to bring you to the next line, and one to bring you to the beginning of that line. In *nix based systems, the standard is to use a single character to denote a newline. I believe it is a <CR>, but I'm sure someone will correct me if I'm wrong. This means if you try to open a Windows-based text file on a *nix-based system, it will see extra characters it is not expecting (In this case the <LF>). I'm sure there's a setting in Notepad++ to preserve the line endings on the original file, what this will do is look at the file and look at the very first line ending. If it is a <CR><LF> then it will say "ok, any time the user presses return, I'll insert both". If it sees only a single <CR> then it will know that when you press return, it will insert just a single <CR>. If you want to be absolutely sure the line endings are not your culprit, you should open the file in NP++. Make the edit you want, and then on the menu, select Edit->EOL Conversion->UNIX Format. If this option is greyed out, then it means the file is already UNIX line endings, and you have some other problem. As a side note, has anyone found a suitable font for the Kindle with all of it's hinting/rendering uniqueness? I don't mind the default condensed font terribly, but find it less readable than opening up a p-book. I'm not a typographer, so I don't know the traditional paperback book font. Garamond perhaps? |
09-21-2010, 04:45 PM | #25 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Yep, it's a single LF (\n) for UNIX line endings . There's even a weirder setting for legacy Mac OS systems.
|
09-21-2010, 04:56 PM | #26 |
Member
Posts: 10
Karma: 10
Join Date: Aug 2010
Device: none
|
TextPad is a Unix aware text editor. They have a 14 day free trial period. http://www.textpad.com/
EditPad Lite is another one and it's free. http://www.editpadlite.com/ * EditPad reads and writes UNIX (LF only) and Mac (CR only) text files (in addition to DOS/Windows CR+LF files, of course) |
09-21-2010, 05:34 PM | #27 | |
mrkrgnao
Posts: 241
Karma: 237248
Join Date: May 2010
Device: PRS650, K3 Wireless, Galaxy S3, iPad 3.
|
Quote:
Using a Garamond type font at the moment. I think I'll stick with it. It's the second one I tried: the first had characters that were too slender and the 'f's and 'j's didn't have ornate enough 'tails' to be legible at a glance. Switched to a bolder Garamond (don't remember exactly which one I chose), and it's great at only one size larger than I had the K3 default font. Great readability, and looks just like typography from a novel . |
|
09-21-2010, 06:13 PM | #28 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Currently debugging the full Fonts hack, and, yeah, good hinting instructions change *everything*!. Droid Serif is now sharp as hell, where it was completely horrible on the K2!
Last edited by NiLuJe; 10-11-2010 at 11:07 PM. |
09-21-2010, 07:56 PM | #29 |
Zealot
Posts: 109
Karma: 128
Join Date: Aug 2009
Location: Simi Valley, CA
Device: Kobo Libra Colour & Kindle Oasis
|
That's good to hear NiLuJe... after seeing the posts here about the fonts looking pretty bad, I decided not to change the fonts since I'm pretty happy with the default sans serif. Maybe I'll be tempted to try it out after the full hack is released and I hear some results.
Thanks again for all the work you do! I tried to throw some more Karma your way, but it told me I had to spread it around before I could give you more! =) |
09-21-2010, 08:23 PM | #30 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
And here we go, the full hack is out! .
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Changing Font Family | thymaster | Sony Reader | 6 | 09-19-2010 01:10 AM |
Troubleshooting Font size changing | Kumabjorn | Amazon Kindle | 1 | 07-23-2010 12:49 AM |
DR1000 Changing Font-Size | ThR | iRex | 6 | 06-21-2010 06:29 AM |
Changing device's font | Jim77 | Sony Reader | 6 | 12-29-2009 11:45 AM |
Font changing sizes... | rixte | Bookeen | 5 | 12-19-2007 05:58 PM |