Fontspec loads letter sizes, but not the letter shapesLuaLaTeX protrusion problem with Negative valueHow do I use TrueType Fonts with PDFTeX using otftotfm?fontspec for small caps and nocommon ligatures (actually, rawfeatures works, but not ligatures=NoCommon)How to suppress a “Rare” ligature that pre-empts a “Common” ligature for the same character pair?Scale font sizes – match text font (Comfortaa) and math fontTraining Tesseract with generated LaTeX files
Why are trash cans referred to as "zafacón" in Puerto Rico?
A word that means "blending into a community too much"
Getting UPS Power from One Room to Another
How to safely destroy (a large quantity of) valid checks?
Warning about needing "authorization" when booking ticket
Print lines between start & end pattern, but if end pattern does not exist, don't print
Longest bridge/tunnel that can be cycled over/through?
What is the color of artificial intelligence?
Why can my keyboard only digest 6 keypresses at a time?
Fermat's statement about the ancients: How serious was he?
Live action TV show where High school Kids go into the virtual world and have to clear levels
I have a problematic assistant manager, but I can't fire him
Is using 'echo' to display attacker-controlled data on the terminal dangerous?
Align equations within one column
How did old MS-DOS games utilize various graphic cards?
Teaching a class likely meant to inflate the GPA of student athletes
60s or 70s novel about Empire of Man making 1st contact with 1st discovered alien race
How is the excise border managed in Ireland?
What aircraft was used as Air Force One for the flight between Southampton and Shannon?
Active low-pass filters --- good to what frequencies?
Fixing obscure 8080 emulator bug?
Is it possible to fly backward if you have a 'really strong' headwind?
How to hide rifle during medieval town entrance inspection?
A map of non-pathological topology?
Fontspec loads letter sizes, but not the letter shapes
LuaLaTeX protrusion problem with Negative valueHow do I use TrueType Fonts with PDFTeX using otftotfm?fontspec for small caps and nocommon ligatures (actually, rawfeatures works, but not ligatures=NoCommon)How to suppress a “Rare” ligature that pre-empts a “Common” ligature for the same character pair?Scale font sizes – match text font (Comfortaa) and math fontTraining Tesseract with generated LaTeX files
I'm trying to use the fontspec package to use the P22 Hopper Edward font.
In all other software, this looks wonderful:
But while LaTeX throws no errors, the font looks wrong: the letter shapes aren't being used, but the letter sizes do seem to be.
MWE used to create this image:
documentclassarticle
usepackagefontspec
setmainfontHopper.ttf[Path=./fonts/,Ligatures=TeX]
begindocument
This text looks very weird and wrong. I don't understand why.
LARGE When it's large, it looks even worse.
enddocument
Strangely enough, this doesn't happen with any other TTF file I've tried.
EDIT: Here's what pdffonts reports:
name type encoding emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
P22HopperEdward CID TrueType Identity-H no no yes 13 0
fontspec truetype
asked May 31 at 23:41
DraconisDraconis
4189
|
show 2 more comments
I'm trying to use the fontspec package to use the P22 Hopper Edward font.
In all other software, this looks wonderful:
But while LaTeX throws no errors, the font looks wrong: the letter shapes aren't being used, but the letter sizes do seem to be.
MWE used to create this image:
documentclassarticle
usepackagefontspec
setmainfontHopper.ttf[Path=./fonts/,Ligatures=TeX]
begindocument
This text looks very weird and wrong. I don't understand why.
LARGE When it's large, it looks even worse.
enddocument
Strangely enough, this doesn't happen with any other TTF file I've tried.
EDIT: Here's what pdffonts reports:
name type encoding emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
P22HopperEdward CID TrueType Identity-H no no yes 13 0
fontspec truetype
asked May 31 at 23:41
DraconisDraconis
4189
1
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
embnolooks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)
– David Carlisle
Jun 1 at 0:08
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
2
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20
|
show 2 more comments
I'm trying to use the fontspec package to use the P22 Hopper Edward font.
In all other software, this looks wonderful:
But while LaTeX throws no errors, the font looks wrong: the letter shapes aren't being used, but the letter sizes do seem to be.
MWE used to create this image:
documentclassarticle
usepackagefontspec
setmainfontHopper.ttf[Path=./fonts/,Ligatures=TeX]
begindocument
This text looks very weird and wrong. I don't understand why.
LARGE When it's large, it looks even worse.
enddocument
Strangely enough, this doesn't happen with any other TTF file I've tried.
EDIT: Here's what pdffonts reports:
name type encoding emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
P22HopperEdward CID TrueType Identity-H no no yes 13 0
fontspec truetype
asked May 31 at 23:41
DraconisDraconis
4189
I'm trying to use the fontspec package to use the P22 Hopper Edward font.
In all other software, this looks wonderful:
But while LaTeX throws no errors, the font looks wrong: the letter shapes aren't being used, but the letter sizes do seem to be.
MWE used to create this image:
documentclassarticle
usepackagefontspec
setmainfontHopper.ttf[Path=./fonts/,Ligatures=TeX]
begindocument
This text looks very weird and wrong. I don't understand why.
LARGE When it's large, it looks even worse.
enddocument
Strangely enough, this doesn't happen with any other TTF file I've tried.
EDIT: Here's what pdffonts reports:
name type encoding emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
P22HopperEdward CID TrueType Identity-H no no yes 13 0
fontspec truetype
fontspec truetype
asked May 31 at 23:41
DraconisDraconis
4189
asked May 31 at 23:41
DraconisDraconis
4189
edited Jun 1 at 0:05
Draconis
asked May 31 at 23:41
DraconisDraconis
4189
asked May 31 at 23:41
DraconisDraconis
4189
asked May 31 at 23:41
DraconisDraconis
4189
4189
1
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
embnolooks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)
– David Carlisle
Jun 1 at 0:08
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
2
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20
|
show 2 more comments
1
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
embnolooks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)
– David Carlisle
Jun 1 at 0:08
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
2
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20
1
1
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
emb
no looks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)– David Carlisle
Jun 1 at 0:08
emb
no looks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)– David Carlisle
Jun 1 at 0:08
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
2
2
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20
|
show 2 more comments
1 Answer
1
active
oldest
votes
An answer has been found!
The font in question had embedding restrictions in the file, so LuaTeX obediently refused to embed it. Thus, another font was substituted by the viewer.
Fortunately, in this case the publisher does allow embedding. I'm not sure how the copy I was using gained these restrictions, but redownloading the TTF and using that version fixed the problem. Just to confirm, I opened the file I had been using and removed all restrictions manually; sure enough, it started working immediately. (Though of course don't do this if the publisher didn't grant permission!)
EDIT: Even stranger, I examined the original file again. The permissions field had bit 1 set, which is undefined: the spec says that bit should always be left clear. It seems LuaTeX decided this meant "do not embed", even though none of the actual "do not embed" bits were set.
I suppose this is undefined behavior rather than a bug, but either way, it was unexpected.
answered Jun 1 at 0:30
DraconisDraconis
4189
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f493613%2ffontspec-loads-letter-sizes-but-not-the-letter-shapes%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
An answer has been found!
The font in question had embedding restrictions in the file, so LuaTeX obediently refused to embed it. Thus, another font was substituted by the viewer.
Fortunately, in this case the publisher does allow embedding. I'm not sure how the copy I was using gained these restrictions, but redownloading the TTF and using that version fixed the problem. Just to confirm, I opened the file I had been using and removed all restrictions manually; sure enough, it started working immediately. (Though of course don't do this if the publisher didn't grant permission!)
EDIT: Even stranger, I examined the original file again. The permissions field had bit 1 set, which is undefined: the spec says that bit should always be left clear. It seems LuaTeX decided this meant "do not embed", even though none of the actual "do not embed" bits were set.
I suppose this is undefined behavior rather than a bug, but either way, it was unexpected.
answered Jun 1 at 0:30
DraconisDraconis
4189
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
add a comment |
An answer has been found!
The font in question had embedding restrictions in the file, so LuaTeX obediently refused to embed it. Thus, another font was substituted by the viewer.
Fortunately, in this case the publisher does allow embedding. I'm not sure how the copy I was using gained these restrictions, but redownloading the TTF and using that version fixed the problem. Just to confirm, I opened the file I had been using and removed all restrictions manually; sure enough, it started working immediately. (Though of course don't do this if the publisher didn't grant permission!)
EDIT: Even stranger, I examined the original file again. The permissions field had bit 1 set, which is undefined: the spec says that bit should always be left clear. It seems LuaTeX decided this meant "do not embed", even though none of the actual "do not embed" bits were set.
I suppose this is undefined behavior rather than a bug, but either way, it was unexpected.
answered Jun 1 at 0:30
DraconisDraconis
4189
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
add a comment |
An answer has been found!
The font in question had embedding restrictions in the file, so LuaTeX obediently refused to embed it. Thus, another font was substituted by the viewer.
Fortunately, in this case the publisher does allow embedding. I'm not sure how the copy I was using gained these restrictions, but redownloading the TTF and using that version fixed the problem. Just to confirm, I opened the file I had been using and removed all restrictions manually; sure enough, it started working immediately. (Though of course don't do this if the publisher didn't grant permission!)
EDIT: Even stranger, I examined the original file again. The permissions field had bit 1 set, which is undefined: the spec says that bit should always be left clear. It seems LuaTeX decided this meant "do not embed", even though none of the actual "do not embed" bits were set.
I suppose this is undefined behavior rather than a bug, but either way, it was unexpected.
answered Jun 1 at 0:30
DraconisDraconis
4189
An answer has been found!
The font in question had embedding restrictions in the file, so LuaTeX obediently refused to embed it. Thus, another font was substituted by the viewer.
Fortunately, in this case the publisher does allow embedding. I'm not sure how the copy I was using gained these restrictions, but redownloading the TTF and using that version fixed the problem. Just to confirm, I opened the file I had been using and removed all restrictions manually; sure enough, it started working immediately. (Though of course don't do this if the publisher didn't grant permission!)
EDIT: Even stranger, I examined the original file again. The permissions field had bit 1 set, which is undefined: the spec says that bit should always be left clear. It seems LuaTeX decided this meant "do not embed", even though none of the actual "do not embed" bits were set.
I suppose this is undefined behavior rather than a bug, but either way, it was unexpected.
answered Jun 1 at 0:30
DraconisDraconis
4189
edited Jun 3 at 15:54
answered Jun 1 at 0:30
DraconisDraconis
4189
answered Jun 1 at 0:30
DraconisDraconis
4189
answered Jun 1 at 0:30
DraconisDraconis
4189
4189
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
add a comment |
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
This is curious. I’ve licensed many fonts from P22 (using either P22’s own site or MyFonts.com) and never had a problem. Was the restriction on the copy from adobe.com?
– Thérèse
Jun 3 at 16:05
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
@Thérèse I'm unsure, honestly; it was on the copy I had on my hard drive, which I thought I got from adobe.com, but when I redownloaded it the restriction was gone. So I'm not sure where that came from.
– Draconis
Jun 3 at 16:19
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f493613%2ffontspec-loads-letter-sizes-but-not-the-letter-shapes%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
what does pdffonts utility report on the resulting pdf
– David Carlisle
May 31 at 23:47
@DavidCarlisle Added its output to the question.
– Draconis
Jun 1 at 0:06
emb
nolooks a bit suspicious, why isn't it embedded (does the font have embedding licence restrictions?)– David Carlisle
Jun 1 at 0:08
do you get the same with xetex and luatex
– David Carlisle
Jun 1 at 0:16
2
@DavidCarlisle Brilliant! Embedding restrictions were the problem. Strangely enough, the original file downloaded from the publisher allows embedding—the TTF I was using somehow gained additional restrictions along the way. Using the original font again fixed the issue.
– Draconis
Jun 1 at 0:20