Problem with embedded fonts

[charleski]

You left off the closing parenthesis in your @font-face definition, so the css doesn't parse. I noticed that in your post above, but thought you'd just failed to copy it over for the post. Also, you've added numbers to the end of the names of the font files that need to be removed.
So replace your font-face definitions with

@font-face {
  font-family: "Times New Roman";
  font-weight: normal;
  font-style: normal;
  src: url(../Fonts/Times New Roman Regular.ttf);
}

@font-face {
  font-family: "Times New Roman";
  font-weight: bold;
  font-style: normal;
  src: url(../Fonts/Times New Roman Bold.ttf);
}

@font-face {
  font-family: "Times New Roman";
  font-weight: normal;
  font-style: italic;
  src: url(../Fonts/Times New Roman Italic.ttf);
 }

and it works fine.

Use the css attribute text-indent:1 em to indent the first line of a paragraph. Embedding a bunch of non-breaking spaces isn't a good idea.

[James_Wilde]

You're the man, Charleski! Thanks.

I still get some funny results. Stanza has not changed its behaviour. It gives me no italics but shows the pinyin correctly. Adobe works fine with both italics and pinyin. Calibre turns everything into italics, and shows the pinyin correctly, and my Iriver shows both italics and pinyin as it should.

I must have missed the closing bracket once when I copied the @fontface statements, and not noticed it even when Valloric pointed out the small 'f' instead of a capital 'F' in the Fonts path.

I'll have a look at what you mean by the numbers at the end of the names of the font files. Don't know where they came from.

And I noticed the non-breaking spaces and assumed this was added by either calibre or sigil and wondered why ems weren't used, but was more concerned with getting the pinyin and italics showing, so I didn't do anything about that. Now I'll try and learn how to do that, and Zelda's epub of TMOAB should help me there.

Anyway, you've solved my problem for me, and I'm extremely grateful. Now I'll set about including the jpegs in the appropriate place, and I can load my own novel onto my own ebook reader, and maybe even upload it somewhere and see if it wakes any interest.

Thanks again.

[Valloric]

Originally Posted by James_Wilde

And I noticed the non-breaking spaces and assumed this was added by either calibre or sigil and wondered why ems weren't used, but was more concerned with getting the pinyin and italics showing, so I didn't do anything about that.

Just for the record, Sigil does not add nbsps to the start of paragraphs.

[JSWolf]

Stanza does not support embedded fonts. Stanza should be avoided at all costs. Stanza uses a sub-par rendering engine that needs a lot of work to fix it.

[pholy]

Originally Posted by JSWolf

Stanza does not support embedded fonts. Stanza should be avoided at all costs. Stanza uses a sub-par rendering engine that needs a lot of work to fix it.

I thought that was true of all rendering engines. Which is/are acceptable?

Not the embedded fonts part, the sub-par part.

When will we create a suite of conformance tests?

[JSWolf]

Originally Posted by pholy

I thought that was true of all rendering engines. Which is/are acceptable?

Not the embedded fonts part, the sub-par part.

When will we create a suite of conformance tests?

The problem is that the only real test for ePub is not a real test. That would be ePubCheck. Just because it passes does not mean it works and just because it fails doesn't mean it doesn't work.

[James_Wilde]

Originally Posted by JSWolf

Stanza does not support embedded fonts. Stanza should be avoided at all costs. Stanza uses a sub-par rendering engine that needs a lot of work to fix it.

Thanks for the tip, JS. I have quoted the results with Stanza as it was one of the first epub readers for my Mac laptop that I downloaded, and I just haven't bothered to wipe it.

Any suggestions for what might be more appropriate as a tool for testing epub files one creates oneself, apart from Adobe, of course, and the reading part of Calibre. Can't remember whether Sigils divided screen shows exactly what one has ordered, but that might be another one to use.

[jharker]

Originally Posted by JSWolf

Stanza does not support embedded fonts. Stanza should be avoided at all costs. Stanza uses a sub-par rendering engine that needs a lot of work to fix it.

Just out of curiosity, what about Stanza is sub-par?

I actually don't use Stanza very much, but I did notice that it implements hyphenation, which no other e-reader does (as far as I know). So based on that, I thought that they were actually a bit ahead of the competition.

On the other hand, their hyphenation implementation is really quite poor.

[JSWolf]

Originally Posted by James_Wilde

Thanks for the tip, JS. I have quoted the results with Stanza as it was one of the first epub readers for my Mac laptop that I downloaded, and I just haven't bothered to wipe it.

Any suggestions for what might be more appropriate as a tool for testing epub files one creates oneself, apart from Adobe, of course, and the reading part of Calibre. Can't remember whether Sigils divided screen shows exactly what one has ordered, but that might be another one to use.

To be honest, you should be testing your ePub with Adobe Digital Editions. That's what most desktops/laptops and most stand alone readers use.

[JSWolf]

Originally Posted by jharker

Just out of curiosity, what about Stanza is sub-par?

I actually don't use Stanza very much, but I did notice that it implements hyphenation, which no other e-reader does (as far as I know). So based on that, I thought that they were actually a bit ahead of the competition.

On the other hand, their hyphenation implementation is really quite poor.

There are a number of things wrong with Stanza. Font embedding is just one of them. I don't know offhand what the issues are. But they are there.

[Freeshadow]

wasn't lack of support of SVG book covers also one of them?