Sigil on OS 10.9 Mavericks - Page 2

VydorScope · 10-27-2013, 01:22 PM

Yay! Thanks for 0.7.4! Working great here.

GRiker · 10-27-2013, 01:27 PM

Thanks for doing the Mavericks update.

G

NPOratik · 10-28-2013, 01:39 AM

I upgraded my OS to Mavericks, again. Sigil 0.7.4 seems work well. Thanks!!

tmansfield · 11-06-2013, 06:57 PM

Embedded fonts still aren't displaying correctly for me (using 0.7.4 on Mavericks). They were working beautifully with 0.7.4 until the Mavericks upgrade. Exactly what it *will* display in Book View changes every time I reopen the program.

The ability to switch back and forth between Code and Book View is something that I valued in Sigil.

FWIW, I was using @font-face in the css.

ordzo · 11-07-2013, 01:21 PM

Quote:

Originally Posted by tmansfield

Embedded fonts still aren't displaying correctly ...

Yes, embedded fonts are big problem...
I hope this problem is corrected soon...

Quote:

The only workaround I found is to install fonts in Mac OS X, use font-family to display them and embed fonts using @font-face at the end.

This workaround is not working despite I allways use this for embedding fonts...

Toxaris · 11-08-2013, 02:21 AM

It sounds that the old QT bug is back again with regards to embedded fonts.

DiapDealer · 11-08-2013, 09:34 AM

Trusting Book View to properly display embedded fonts 100% of the time has always been a risky proposition at best (although it was thought to have been fixed in Qt5). Longtime users of Sigil learned long ago not to trust everything they see (or don't see) in Book View. Always double-check on a target device (or ADE) if there's any doubts when it comes to rendering (especially with regard to embedded fonts).

FrMartin · 11-13-2013, 09:50 PM

Yeah, I don't understand that "workaround." I mean that's how I embedded the fonts but they still look like random gobblety gook in "book view" in Sigil.

If anyone can figure out a solution for a person who doesn't know QT from Quicktime, I sure could use some help. I had just figured out how to workaround iBook's dislike for embedding fonts (i.e. the com.apple.ibooks.display-options trick) and now I can't view them in Sigil.

Toxaris · 11-14-2013, 03:23 AM

There is nothing you can do about it. It is a bug in Qt (not quicktime), which is the framework used. We can only hope that Nokia will fix it.

mrmikel · 11-14-2013, 06:41 AM

Unless you have a large variety of fonts (see ransom note syndrome), once you have established that the fonts work in a real device you can just continue working with the document. It is not consequential whether or not they show in Sigil, though it sure was nice that they did for a while.

While it is fun to play typographer, the more complex you get, the more likely the document will fail in a different device or when a ereader manufacturer makes a change in hardware or a publisher like Apple or Nook makes a change in what they will accept.

tmansfield · 11-15-2013, 08:43 AM

Having ADE available solves my immediate practical problem to a degree, in that this ADE "book view" refreshes fairly readily after I've made code changes in Sigil. It's just that I would much rather have one program in which I can compose in book view, and then easily switch back and forth between that and code view. (None of the other available options have allowed for the importing of an existing ePub and its subsequent accurate display. They all fail in one way or another. Sigil had been working beautifully, doing exactly what I wanted without complaint, and I miss that.) As things stand, I now have to compose in Sigil code view and then use ADE to monitor the consequent changes.

This is certainly not a significant complaint in the grand scheme of life, and I suppose it just comes down to it being an annoyance whose clunkiness is all the more irritating because it is unnecessary, based solely on my having jumped to Mavericks without having been smart enough to give it several months' worth of debug settling first. Of all the things that the Mavericks update might have broken, this one simply did not occur to me as a possibility. It should have, and I should have left well enough alone.

11-06-2013, 06:57 PM	#19
tmansfield Junior Member Posts: 2 Karma: 10 Join Date: Nov 2013 Device: Mac, iPad	Embedded Fonts Embedded fonts still aren't displaying correctly for me (using 0.7.4 on Mavericks). They were working beautifully with 0.7.4 until the Mavericks upgrade. Exactly what it will display in Book View changes every time I reopen the program. The ability to switch back and forth between Code and Book View is something that I valued in Sigil. FWIW, I was using @font-face in the css.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to put a book on an iPad in OSX 10.9 (Mavericks)?	imrulqays	Apple Devices	7	09-26-2014 12:03 PM
OS X Mavericks is out!	Jessica Lares	Apple Devices	36	11-04-2013 01:06 PM
OSX Mavericks: iBooks now, not iTunes	kyteflyer	Calibre	14	10-28-2013 08:57 AM
iBooks app in latest OS X Mavericks developer preview!	Jessica Lares	Apple Devices	30	10-27-2013 12:39 PM
Western Raine, William MacLeod: Mavericks v1 27 dec 2008	mtravellerh	IMP Books	0	12-27-2008 02:31 PM

10-27-2013, 01:22 PM	#16
VydorScope Wizard Posts: 3,418 Karma: 35207650 Join Date: Jun 2011 Device: iPad	Yay! Thanks for 0.7.4! Working great here.

10-27-2013, 01:27 PM	#17
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	Thanks for doing the Mavericks update. G

10-28-2013, 01:39 AM	#18
NPOratik Junior Member Posts: 3 Karma: 10 Join Date: Oct 2013 Device: iBooks	I upgraded my OS to Mavericks, again. Sigil 0.7.4 seems work well. Thanks!!

11-08-2013, 02:21 AM	#21
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	It sounds that the old QT bug is back again with regards to embedded fonts.

11-08-2013, 09:34 AM	#22
DiapDealer Grand Sorcerer Posts: 28,358 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Trusting Book View to properly display embedded fonts 100% of the time has always been a risky proposition at best (although it was thought to have been fixed in Qt5). Longtime users of Sigil learned long ago not to trust everything they see (or don't see) in Book View. Always double-check on a target device (or ADE) if there's any doubts when it comes to rendering (especially with regard to embedded fonts).

11-13-2013, 09:50 PM	#23
FrMartin Junior Member Posts: 5 Karma: 10 Join Date: Jul 2013 Device: Sigil	Yeah, I don't understand that "workaround." I mean that's how I embedded the fonts but they still look like random gobblety gook in "book view" in Sigil. If anyone can figure out a solution for a person who doesn't know QT from Quicktime, I sure could use some help. I had just figured out how to workaround iBook's dislike for embedding fonts (i.e. the com.apple.ibooks.display-options trick) and now I can't view them in Sigil.

11-14-2013, 03:23 AM	#24
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	There is nothing you can do about it. It is a bug in Qt (not quicktime), which is the framework used. We can only hope that Nokia will fix it.

11-14-2013, 06:41 AM	#25
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	Unless you have a large variety of fonts (see ransom note syndrome), once you have established that the fonts work in a real device you can just continue working with the document. It is not consequential whether or not they show in Sigil, though it sure was nice that they did for a while. While it is fun to play typographer, the more complex you get, the more likely the document will fail in a different device or when a ereader manufacturer makes a change in hardware or a publisher like Apple or Nook makes a change in what they will accept.

11-15-2013, 08:43 AM	#26
tmansfield Junior Member Posts: 2 Karma: 10 Join Date: Nov 2013 Device: Mac, iPad	Having ADE available solves my immediate practical problem to a degree, in that this ADE "book view" refreshes fairly readily after I've made code changes in Sigil. It's just that I would much rather have one program in which I can compose in book view, and then easily switch back and forth between that and code view. (None of the other available options have allowed for the importing of an existing ePub and its subsequent accurate display. They all fail in one way or another. Sigil had been working beautifully, doing exactly what I wanted without complaint, and I miss that.) As things stand, I now have to compose in Sigil code view and then use ADE to monitor the consequent changes. This is certainly not a significant complaint in the grand scheme of life, and I suppose it just comes down to it being an annoyance whose clunkiness is all the more irritating because it is unnecessary, based solely on my having jumped to Mavericks without having been smart enough to give it several months' worth of debug settling first. Of all the things that the Mavericks update might have broken, this one simply did not occur to me as a possibility. It should have, and I should have left well enough alone.