Yeap, it's not a typo. I just got an 1.0.1 firmware update instead of the 1.0.4 (see the screenshot). I have kept my Whispernet off for the past week or so in order NOT to update my firmware. But it seemed that the update still managed to sneak in during the limited time while I was downloading new books. Maybe 1.0.4 isn't really ready for the prime time so they pushed 1.0.1 instead?

On a separate note, now that the firmware update's out, I was wondering if anyone found ways to make customary firmwares. Of all the possible enhancements, I really really want unicode support so that I can read non-roman mobi books. :help:

I also got 1.0.1 just today. But reading in one of the forums a poster said that he turned his whispernet on, placed his kindle in sleep mode, and within 10 minutes his Kindle started updating. I did this and that's exactly what happened. I now show 1.0.4 on my Kindle.

Kevin

Kevin, nice avatar. I am a trekkie and do read a lot of Star Trek books.

I turned the wireless on and then went into the menu and selected update, worked fine

I still have 1.0 and my "Update Your Kindle" is grayed out. :(

According to the instructs that came with the online version of the patch, the "update" button is grayed out until there is an update present for it to do. Present meaning downloaded to your kindle already. So, you won't be able to press that button until your turn comes up for them to ship the patch down to you. But maybe you already knew all that.......

Kevin, nice avatar. I am a trekkie and do read a lot of Star Trek books.

I like to consider myself a trekker, rather than a trekkie. I've been to a Star Trek Convention, but I did not dress up as a Klingon....:D

I too read the books, especially the Original series and the Next Gen.

Kevin

Currently, I am reading The Sky's the Limit and A Good Day to Die. I do have Before Dishonor partially read in pBook and also Forged in Fire undread in pBook as well. I'm also rereading Enterprise: the First Adventure as well. Plus, I have all of the SCE series as eBooks and most (if not all) of the CoE as well.

Hey, let's not forget Star Trek: Titan. Gotta give a shout-out to Captain Riker of the U.S.S. Titan. I'm reading book one, Taking Wing, and it's really great. But some people complain that it has too much focus on character and not enough action.

Which, by the way, is the reason I enjoy it so much. :)

I'm more of a TNG fan myself, so it's good to see Riker in action with his own command. Finally.

All four ST: Titan books are available in ebook format.

Just checked mine same here 1.01 What gives?

Hey, let's not forget Star Trek: Titan. Gotta give a shout-out to Captain Riker of the U.S.S. Titan. I'm reading book one, Taking Wing, and it's really great. But some people complain that it has too much focus on character and not enough action.

Which, by the way, is the reason I enjoy it so much. :)

I'm more of a TNG fan myself, so it's good to see Riker in action with his own command. Finally.

All four ST: Titan books are available in ebook format.
They have to start off giving more character info but as they move on that get s less. I did purchase Titan #4 Sword of Damocles from Fictionwise when they had it as a 100% micropay rebate and I really liked that one. #3 was good, not great. The weakest so far (IMHO). Too much Troy and her headaches.

They have to start off giving more character info but as they move on that get s less. I did purchase Titan #4 Sword of Damocles from Fictionwise when they had it as a 100% micropay rebate and I really liked that one. #3 was good, not great. The weakest so far (IMHO). Too much Troy and her headaches.

Yeah, I do get tired of Troy. I like the Riker and Tuvok characters, but Troy can drag on a bit. But I am liking the series so far.

Ok, back to topic, I didn't mean to hijack the thread. Sorry! :)

Troy is not bad overall. It's just when she has these problems with her empathy that it can be annoying. But in #4 she is not a problem at all.

I heard not everyone gets the update at the sames times

Just checked mine same here 1.01 What gives?

I downloaded and read the Trek book that was available on this sight. Music of the Spheres.........one of the worst Trek books I've ever read. No wonder it was never published.

Kevin

I got 1.0.1 just now. Waited a few minutes and the update your kindle menu item became available again. It's updating again now.

Maybe 1.0.1 is a fix to the updating code necessary to get 1.0.4?

Maybe this thread could be retitled?

1.0.1 to 1.0.4 to Star Trek Love

:)

1.0.4 was installed yesterday. All is well.

1.0.1 installed just a bit ago. no new manual. while hustling for a camera for the funnyyupdate screen, it rebooted. rats.

then put it to sleep, and it did it again, 1.0.4 downloaded, got some okay pix. nothing stunning, but the messages are neat, and the strange icons down the right side of the screen are intriguing - hidden mode?

exreader

You can find a Unicode Glyphs test file for Kindle at http://www.freekindlebooks.org under "Unicode". Simple answer is that Kindle doesn't seem to support much other than a few DOS dingbats above U+0250 "Latin" and even then Kindle leaves off the diacriticals on many of the high latin letters. I have Kindle version 1.0 -- does anyone know how the versions have changed and why?

You can find a Unicode Glyphs test file for Kindle at http://www.freekindlebooks.org under "Unicode". Simple answer is that Kindle doesn't seem to support much other than a few DOS dingbats above U+0250 "Latin" and even then Kindle leaves off the diacriticals on many of the high latin letters. I have Kindle version 1.0 -- does anyone know how the versions have changed and why?

Thanks for the link. I will update the 'special characters' in the MR wiki based on this data. There are discussions of all the Unicode and other formats beginning with a discussion of 'characters' on the wiki. There is also a discussion of 'fonts'. Hopefully this will help in your quest.

Dale

I tried you test on a PC running Mobipocket Reader and found that it supported practically everything. I do not have a Kindle to test this with. Can you capture some pages and display what you see on the device? On the PC I would expect it would depend on the fonts you have loaded.

Is it true that 7E looks like an ndash rather than a ~?
Did you intend to leave out U+00AD from you list?

On a PC I get Greek, Armenian, Coptic, Hebrew, some but not all Arabic, Syriac, Thaana and NKo

All of the Canadian and beyond are poorly formatted.

Beginning at U+2580 the graphics characters are spotty but it is likely the font set.

Dale

Can you capture some pages and display what you see on the device? I enclose screenshots from a Kindle (smallest font size). The first is the first page, the 2nd contains U+0250 and the rest contain the only characters defined above this page. I have version 1.0.4.

With FBReader which Unicode Glyphs get displayed depends on the selected font. I assume the same would be true on a Cybook Gen3.

On the iLiad, Greek looks ok and Cyrillic has only a few missing glyphs (e.g. U+04FA to FF), but coverage above Armenian (above U+0589) is hit and miss.

I enclose screenshots from a Kindle (smallest font size). The first is the first page, the 2nd contains U+0250 and the rest contain the only characters defined above this page. I have version 1.0.4.

That is not very good coverage. I have updated the special character data on the wiki site to reflect your observations. In a few cases I see the wrong characters are sometimes displayed and I did not include those. The special character page uses decimal numbers while your page uses hex numbers.

Note that the really interesting glyphs from a eBook perspective are in the range of 200C hex to 2044 but your original sample did not include these. On my decimal page these are the ones from 8204-8260. They have things like curley quotes, emdashes, etc. You might want to try those ranges and see what you get.

Dale

Note that the really interesting glyphs from a eBook perspective are in the range of 200C hex to 2044 Unfortunately, this range is in the part of the document that is corrupted. I enclose screenshots of all the remaining pages that seem to have defined special characters on them (some are named differently, and some display the wrong character).

I'm curious. Have you tried other versions of Mobipocket Reader? (That's what the Kindle is, basically.)

Do they exhibit the same mistakes?

What Glyphs Kindle supports or not is not a "mistake" it is a design decision. Now we may disagree with Amazon about their design decisions -- I would have been much happier if Kindle also had at least support for Greek and Hebrew. Re the test file you can find it at freekindlebooks.org under "Unicode" and if you open it in a recent version of Windows using Mobipocker Reader you will find that Windows implements virtually all the 60,000 or so Unicode Glyphs. So the fact that Kindle only implements about 250 of these is a Kindle design decision. Actually, I take back what I said before about this not being "a mistake". Kindle actually implements a bunch of the high latin Glyphs which are suppose to have diacriticals or marks by leaving off those diacriticals and marks. Now THAT *IS* a mistake! You can choose to implement or not implement a Glyph, but implementing it *incorrectly* -- now that is a very bad idea!

What Glyphs Kindle supports or not is not a "mistake" it is a design decision. Now we may disagree with Amazon about their design decisions -- I would have been much happier if Kindle also had at least support for Greek and Hebrew. Re the test file you can find it at freekindlebooks.org under "Unicode" and if you open it in a recent version of Windows using Mobipocker Reader you will find that Windows implements virtually all the 60,000 or so Unicode Glyphs. So the fact that Kindle only implements about 250 of these is a Kindle design decision. Actually, I take back what I said before about this not being "a mistake". Kindle actually implements a bunch of the high latin Glyphs which are suppose to have diacriticals or marks by leaving off those diacriticals and marks. Now THAT *IS* a mistake! You can choose to implement or not implement a Glyph, but implementing it *incorrectly* -- now that is a very bad idea!

Thanks. I didn't know that.

What Glyphs Kindle supports or not is not a "mistake" it is a design decision. Another way of saying this is that the Kindle only supports the Caecilia font, for example here is this font's General Punctuation (http://www.myfonts.com/fonts/linotype/pmn-caecilia/55-roman/win-ttf/165326/charmap.html?vid=165326&cpselect=UNI40) coverage.

Unfortunately, this range is in the part of the document that is corrupted. I enclose screenshots of all the remaining pages that seem to have defined special characters on them (some are named differently, and some display the wrong character).

They certainly get a lot of them wrong. I am surprised. It looks like PMN Caecilia has the critical ones for eBook use but they must be in the corrupt part of the document. Of course it is pretty easy to make a new document from an HTML page using Mobipocket creator. There are a bunch of good html pages at http://webdesign.about.com/library/bl_htmlcodes.htm
or you can use the ones in our wiki as a starting point. start with characters to see what it there.

Dale

I'm not sure what you guys mean by the document being "corrupted" but I can download it and open it under Windows Vista Mobipocket Reader and I assure you that there the document is not corrupted and correctly displays all the Glyphs that Microsoft has implemented which is virtually all 60,000+ Unicode Glyphs. The only "corruption" I see in the document there is that I did not bother to left-justified the Canadians because there are so darned many of them that I just decided to "pack them it". They are all there they are just not left-justified. So, I would claim that if this document looks "corrupted" to you on some other reader, then it is not a document problem, but rather demonstrates that the reader you are looking at, Kindle or whatever, doesn't bother to implement all the Unicode Glyph points or implements them incorrectly. Which would be a "design shortcoming" or maybe if you like a "corruption" on the part of the reader, but not a "corruption of the document."

???

Sorry -- I think I just figured out what you guys are talking about: namely the Kindle doc in question is from Wikipedia "List of Unicode" editing out the table formatting which Kindle doesn't support. And that wikipedia document is incomplete -- it doesn't give the names of all the unicode glyphs nor representations thereof. So I guess you meant "corropt" in the sense of being an incomplete listing of all the Unicode Glyphs, which is a true statement.

Okay, I've put up a "new and improved and incredibly crude" Unicode test file up at http://www.freekindlebooks.org in the Unicode section that includes all 64,000 unicode test points so that you can test what upper puncs etc Kindle supports. Cheers! -- Jim

I've taken the previous Unicode test file back down off the freekindlebooks site because my Kindle REALLY doesn't like some Unicode test point somewhere around decimal 500 -- IE Kindle dies a horrible death where it will not thereafter successfully open ANY book until you do a hard reset by sticking a sharp object into it! Ouch! So, this being very scary I don't think y'all want to be testing Kindle with this file. I can read it fine from Mobipocket Reader so I know its a "valid" file -- its just that some Unicode test point is causing Kindle to die a horrible death. If anyone else has tried this on their Kindle the way to recover is to power down, take off the back cover and stick an unbent paper clip into the "Reset" hole. *Sigh* Not Fun.