Are there cases where fontenc + luatex (or xetex) cause problems?
According to the luatex docs, you shouldn't use fontenc with luatex. People swear up and down that fontenc is incompatible, but I haven't been able to find an example where loading the package causes problems.
(I'm curious about this because it can be easier to load the same base set of packages for pdftex/luatex/xetex, and add fontspec only when handling the latter two.)
I know fontenc is not the right way to deal with fonts in luatex or xelatex, but I'm specifically looking for cases where it's detrimental to load the fontenc package. Do you know of any?
fonts xetex luatex
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
According to the luatex docs, you shouldn't use fontenc with luatex. People swear up and down that fontenc is incompatible, but I haven't been able to find an example where loading the package causes problems.
(I'm curious about this because it can be easier to load the same base set of packages for pdftex/luatex/xetex, and add fontspec only when handling the latter two.)
I know fontenc is not the right way to deal with fonts in luatex or xelatex, but I'm specifically looking for cases where it's detrimental to load the fontenc package. Do you know of any?
fonts xetex luatex
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago
add a comment |
According to the luatex docs, you shouldn't use fontenc with luatex. People swear up and down that fontenc is incompatible, but I haven't been able to find an example where loading the package causes problems.
(I'm curious about this because it can be easier to load the same base set of packages for pdftex/luatex/xetex, and add fontspec only when handling the latter two.)
I know fontenc is not the right way to deal with fonts in luatex or xelatex, but I'm specifically looking for cases where it's detrimental to load the fontenc package. Do you know of any?
fonts xetex luatex
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
According to the luatex docs, you shouldn't use fontenc with luatex. People swear up and down that fontenc is incompatible, but I haven't been able to find an example where loading the package causes problems.
(I'm curious about this because it can be easier to load the same base set of packages for pdftex/luatex/xetex, and add fontspec only when handling the latter two.)
I know fontenc is not the right way to deal with fonts in luatex or xelatex, but I'm specifically looking for cases where it's detrimental to load the fontenc package. Do you know of any?
fonts xetex luatex
fonts xetex luatex
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
karldwkarldw
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
karldwkarldw
161
asked 4 hours ago
karldwkarldw
161
161
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
karldw is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago
add a comment |
1
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago
1
1
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago
add a comment |
1 Answer
1
active
oldest
votes
It can cause problems if you load both fontspec and fontenc together. Here is an example that loads the legacy Utopia font, which is T1-encoded, but then also tries to load a modern Unicode font through Babel.
documentclass[varwidth, preview]{standalone}
usepackage[spanish]{babel}
% Due to a bug in Babel 3.22, we must override the OpenType
% language and script features for Japanese, and several other
% languages.
babelprovide[language=Japanese, script=Kana]{japanese}
% Implicitly causes babel to load fontspec:
babelfont[japanese]{rm}{Noto Sans CJK JP}
% Implicitly loads fontenc with [T1]:
usepackage[poorman]{fourier}
begin{document}
¿Es foreignlanguage{japanese}{日本} Utopía?
end{document}
Permuting the order in which you load packages can give you many different bugs.
To fix this, load luainputenc, which, despite the misleading name, also allows switching between Unicode and legacy encodings on output:
documentclass[varwidth, preview]{standalone}
usepackage[T1]{fontenc}
usepackage{textcomp}
usepackage[utf8]{luainputenc} % Needed to mix NFSS and Unicode
usepackage[spanish]{babel}
usepackage[no-math]{fontspec}
defaultfontfeatures{ Scale = MatchUppercase }
newfontfamilyjapanesefont{Noto Serif CJK JP}[
Language = Japanese,
Script = Kana ]
newcommandtextjapanese[1]{{japanesefont #1}}
usepackage[poorman]{fourier}
begin{document}
¿Es textjapanese{日本} Utopía?
end{document}
In particular, one problem with the first sample is that loading fontenc without luainputenc sets all non-ASCII characters inactive.
answered 3 hours ago
DavislorDavislor
5,2121125
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
});
}
});
karldw is a new contributor. Be nice, and check out our Code of Conduct.
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%2f470976%2fare-there-cases-where-fontenc-luatex-or-xetex-cause-problems%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
It can cause problems if you load both fontspec and fontenc together. Here is an example that loads the legacy Utopia font, which is T1-encoded, but then also tries to load a modern Unicode font through Babel.
documentclass[varwidth, preview]{standalone}
usepackage[spanish]{babel}
% Due to a bug in Babel 3.22, we must override the OpenType
% language and script features for Japanese, and several other
% languages.
babelprovide[language=Japanese, script=Kana]{japanese}
% Implicitly causes babel to load fontspec:
babelfont[japanese]{rm}{Noto Sans CJK JP}
% Implicitly loads fontenc with [T1]:
usepackage[poorman]{fourier}
begin{document}
¿Es foreignlanguage{japanese}{日本} Utopía?
end{document}
Permuting the order in which you load packages can give you many different bugs.
To fix this, load luainputenc, which, despite the misleading name, also allows switching between Unicode and legacy encodings on output:
documentclass[varwidth, preview]{standalone}
usepackage[T1]{fontenc}
usepackage{textcomp}
usepackage[utf8]{luainputenc} % Needed to mix NFSS and Unicode
usepackage[spanish]{babel}
usepackage[no-math]{fontspec}
defaultfontfeatures{ Scale = MatchUppercase }
newfontfamilyjapanesefont{Noto Serif CJK JP}[
Language = Japanese,
Script = Kana ]
newcommandtextjapanese[1]{{japanesefont #1}}
usepackage[poorman]{fourier}
begin{document}
¿Es textjapanese{日本} Utopía?
end{document}
In particular, one problem with the first sample is that loading fontenc without luainputenc sets all non-ASCII characters inactive.
answered 3 hours ago
DavislorDavislor
5,2121125
add a comment |
It can cause problems if you load both fontspec and fontenc together. Here is an example that loads the legacy Utopia font, which is T1-encoded, but then also tries to load a modern Unicode font through Babel.
documentclass[varwidth, preview]{standalone}
usepackage[spanish]{babel}
% Due to a bug in Babel 3.22, we must override the OpenType
% language and script features for Japanese, and several other
% languages.
babelprovide[language=Japanese, script=Kana]{japanese}
% Implicitly causes babel to load fontspec:
babelfont[japanese]{rm}{Noto Sans CJK JP}
% Implicitly loads fontenc with [T1]:
usepackage[poorman]{fourier}
begin{document}
¿Es foreignlanguage{japanese}{日本} Utopía?
end{document}
Permuting the order in which you load packages can give you many different bugs.
To fix this, load luainputenc, which, despite the misleading name, also allows switching between Unicode and legacy encodings on output:
documentclass[varwidth, preview]{standalone}
usepackage[T1]{fontenc}
usepackage{textcomp}
usepackage[utf8]{luainputenc} % Needed to mix NFSS and Unicode
usepackage[spanish]{babel}
usepackage[no-math]{fontspec}
defaultfontfeatures{ Scale = MatchUppercase }
newfontfamilyjapanesefont{Noto Serif CJK JP}[
Language = Japanese,
Script = Kana ]
newcommandtextjapanese[1]{{japanesefont #1}}
usepackage[poorman]{fourier}
begin{document}
¿Es textjapanese{日本} Utopía?
end{document}
In particular, one problem with the first sample is that loading fontenc without luainputenc sets all non-ASCII characters inactive.
answered 3 hours ago
DavislorDavislor
5,2121125
add a comment |
It can cause problems if you load both fontspec and fontenc together. Here is an example that loads the legacy Utopia font, which is T1-encoded, but then also tries to load a modern Unicode font through Babel.
documentclass[varwidth, preview]{standalone}
usepackage[spanish]{babel}
% Due to a bug in Babel 3.22, we must override the OpenType
% language and script features for Japanese, and several other
% languages.
babelprovide[language=Japanese, script=Kana]{japanese}
% Implicitly causes babel to load fontspec:
babelfont[japanese]{rm}{Noto Sans CJK JP}
% Implicitly loads fontenc with [T1]:
usepackage[poorman]{fourier}
begin{document}
¿Es foreignlanguage{japanese}{日本} Utopía?
end{document}
Permuting the order in which you load packages can give you many different bugs.
To fix this, load luainputenc, which, despite the misleading name, also allows switching between Unicode and legacy encodings on output:
documentclass[varwidth, preview]{standalone}
usepackage[T1]{fontenc}
usepackage{textcomp}
usepackage[utf8]{luainputenc} % Needed to mix NFSS and Unicode
usepackage[spanish]{babel}
usepackage[no-math]{fontspec}
defaultfontfeatures{ Scale = MatchUppercase }
newfontfamilyjapanesefont{Noto Serif CJK JP}[
Language = Japanese,
Script = Kana ]
newcommandtextjapanese[1]{{japanesefont #1}}
usepackage[poorman]{fourier}
begin{document}
¿Es textjapanese{日本} Utopía?
end{document}
In particular, one problem with the first sample is that loading fontenc without luainputenc sets all non-ASCII characters inactive.
answered 3 hours ago
DavislorDavislor
5,2121125
It can cause problems if you load both fontspec and fontenc together. Here is an example that loads the legacy Utopia font, which is T1-encoded, but then also tries to load a modern Unicode font through Babel.
documentclass[varwidth, preview]{standalone}
usepackage[spanish]{babel}
% Due to a bug in Babel 3.22, we must override the OpenType
% language and script features for Japanese, and several other
% languages.
babelprovide[language=Japanese, script=Kana]{japanese}
% Implicitly causes babel to load fontspec:
babelfont[japanese]{rm}{Noto Sans CJK JP}
% Implicitly loads fontenc with [T1]:
usepackage[poorman]{fourier}
begin{document}
¿Es foreignlanguage{japanese}{日本} Utopía?
end{document}
Permuting the order in which you load packages can give you many different bugs.
To fix this, load luainputenc, which, despite the misleading name, also allows switching between Unicode and legacy encodings on output:
documentclass[varwidth, preview]{standalone}
usepackage[T1]{fontenc}
usepackage{textcomp}
usepackage[utf8]{luainputenc} % Needed to mix NFSS and Unicode
usepackage[spanish]{babel}
usepackage[no-math]{fontspec}
defaultfontfeatures{ Scale = MatchUppercase }
newfontfamilyjapanesefont{Noto Serif CJK JP}[
Language = Japanese,
Script = Kana ]
newcommandtextjapanese[1]{{japanesefont #1}}
usepackage[poorman]{fourier}
begin{document}
¿Es textjapanese{日本} Utopía?
end{document}
In particular, one problem with the first sample is that loading fontenc without luainputenc sets all non-ASCII characters inactive.
answered 3 hours ago
DavislorDavislor
5,2121125
edited 3 hours ago
answered 3 hours ago
DavislorDavislor
5,2121125
answered 3 hours ago
DavislorDavislor
5,2121125
answered 3 hours ago
DavislorDavislor
5,2121125
5,2121125
add a comment |
add a comment |
karldw is a new contributor. Be nice, and check out our Code of Conduct.
karldw is a new contributor. Be nice, and check out our Code of Conduct.
karldw is a new contributor. Be nice, and check out our Code of Conduct.
karldw is a new contributor. Be nice, and check out our Code of Conduct.
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%2f470976%2fare-there-cases-where-fontenc-luatex-or-xetex-cause-problems%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
Great first question! I learned some new things by researching the answer. Thanks.
– Davislor
3 hours ago