Incompatibility between kvoptions and babelWrite a class with language dependent stringsIncompatibility...
Why is stat::st_size 0 for devices but at the same time lseek defines the device size correctly?
Instead of Universal Basic Income, why not Universal Basic NEEDS?
Rejected in 4th interview round citing insufficient years of experience
Why do Australian milk farmers need to protest supermarkets' milk price?
How to get the name of the database a stored procedure is executed in within that stored procedure while it's executing?
Is having access to past exams cheating and, if yes, could it be proven just by a good grade?
How to deal with taxi scam when on vacation?
Possible Leak In Concrete
The use of "touch" and "touch on" in context
Life insurance that covers only simultaneous/dual deaths
What is the greatest age difference between a married couple in Tanach?
What are the possible solutions of the given equation?
RegionDifference for Cylinder and Cuboid
Where is the 1/8 CR apprentice in Volo's Guide to Monsters?
Sword in the Stone story where the sword was held in place by electromagnets
Is it possible that AIC = BIC?
Theorems like the Lovász Local Lemma?
Bastion server: use TCP forwarding VS placing private key on server
How Did the Space Junk Stay in Orbit in Wall-E?
How do I hide Chekhov's Gun?
Can hydraulic brake levers get hot when brakes overheat?
How to make healing in an exploration game interesting
Bash replace string at multiple places in a file from command line
Meaning of "SEVERA INDEOVI VAS" from 3rd Century slab
Incompatibility between kvoptions and babel
Write a class with language dependent stringsIncompatibility between nobreakdash and babelUsing Babel inside my own package produces option-clash errorusepackage[english,ngerman,hebrew]{babel}: No file HE8pplx.fd. on input line <number> (with custom .cls)Incompatibility between package [francais]{babel} and refcheckIncompatibility between french babel and fnpct multfootnotePackage babel errorBeamer - maketitle two languagePossible incompatibility between babel, listings and arsclassicaIncompatibility between babel-french and tasks
I'm using kvoptions in my document class and it's worked nicely so far, but after a major rewrite I started getting strange errors that I was able to trace back to the babel package.
MWE:
%% myclass.cls
NeedsTeXFormat{LaTeX2e}[2018/04/01]
ProvidesClass{myclass}
RequirePackage[patch]{kvoptions}
DeclareStringOption{title}
ProcessKeyvalOptions*
LoadClass{article}
RequirePackage[english]{babel}
endinput
documentclass[title={Here be dragons}]{myclass}
begin{document}
Lorem Ipsum
end{document}
An excerpt from the log (paths omitted for brevity):
babel.sty:460: LaTeX Error: Missing begin{document}. [ {}}]
babel.sty:460: Too many }'s. [ {}}]
babel.sty:475: LaTeX Error: Missing begin{document}. [ ifin@edefbbl@tempc{bbl@tempb}fi}]
Without the kvoptions patch, the errors are getting worse:
babel.sty:339: LaTeX Error: Missing begin{document}. [ProcessOptions*]
babel.sty:339: You can't use `macro parameter character #' in horizontal mode. [ProcessOptions*]
TeX STOPPED: File ended while scanning use of reserved@{##1,##2reserved@b }def reserved@b ##1,reserved@b ##2reserved@b
TeX reports the error was in file:3
myclass.cls:13: LaTeX Error: Unknown option `english' for package `babel'. []
Analysis: The problem is that I have used spaces (and braces) in the global option (title) and this option is obviously passed on to babel. Without the spaces, the errors don't occur.
Question: Can I prevent document class options from being used as global options by packages? Or is there some work-around akin to hypersetup{} for me to use instead of options? I could live with that.
babel documentclass-writing options kvoptions
add a comment |
I'm using kvoptions in my document class and it's worked nicely so far, but after a major rewrite I started getting strange errors that I was able to trace back to the babel package.
MWE:
%% myclass.cls
NeedsTeXFormat{LaTeX2e}[2018/04/01]
ProvidesClass{myclass}
RequirePackage[patch]{kvoptions}
DeclareStringOption{title}
ProcessKeyvalOptions*
LoadClass{article}
RequirePackage[english]{babel}
endinput
documentclass[title={Here be dragons}]{myclass}
begin{document}
Lorem Ipsum
end{document}
An excerpt from the log (paths omitted for brevity):
babel.sty:460: LaTeX Error: Missing begin{document}. [ {}}]
babel.sty:460: Too many }'s. [ {}}]
babel.sty:475: LaTeX Error: Missing begin{document}. [ ifin@edefbbl@tempc{bbl@tempb}fi}]
Without the kvoptions patch, the errors are getting worse:
babel.sty:339: LaTeX Error: Missing begin{document}. [ProcessOptions*]
babel.sty:339: You can't use `macro parameter character #' in horizontal mode. [ProcessOptions*]
TeX STOPPED: File ended while scanning use of reserved@{##1,##2reserved@b }def reserved@b ##1,reserved@b ##2reserved@b
TeX reports the error was in file:3
myclass.cls:13: LaTeX Error: Unknown option `english' for package `babel'. []
Analysis: The problem is that I have used spaces (and braces) in the global option (title) and this option is obviously passed on to babel. Without the spaces, the errors don't occur.
Question: Can I prevent document class options from being used as global options by packages? Or is there some work-around akin to hypersetup{} for me to use instead of options? I could live with that.
babel documentclass-writing options kvoptions
add a comment |
I'm using kvoptions in my document class and it's worked nicely so far, but after a major rewrite I started getting strange errors that I was able to trace back to the babel package.
MWE:
%% myclass.cls
NeedsTeXFormat{LaTeX2e}[2018/04/01]
ProvidesClass{myclass}
RequirePackage[patch]{kvoptions}
DeclareStringOption{title}
ProcessKeyvalOptions*
LoadClass{article}
RequirePackage[english]{babel}
endinput
documentclass[title={Here be dragons}]{myclass}
begin{document}
Lorem Ipsum
end{document}
An excerpt from the log (paths omitted for brevity):
babel.sty:460: LaTeX Error: Missing begin{document}. [ {}}]
babel.sty:460: Too many }'s. [ {}}]
babel.sty:475: LaTeX Error: Missing begin{document}. [ ifin@edefbbl@tempc{bbl@tempb}fi}]
Without the kvoptions patch, the errors are getting worse:
babel.sty:339: LaTeX Error: Missing begin{document}. [ProcessOptions*]
babel.sty:339: You can't use `macro parameter character #' in horizontal mode. [ProcessOptions*]
TeX STOPPED: File ended while scanning use of reserved@{##1,##2reserved@b }def reserved@b ##1,reserved@b ##2reserved@b
TeX reports the error was in file:3
myclass.cls:13: LaTeX Error: Unknown option `english' for package `babel'. []
Analysis: The problem is that I have used spaces (and braces) in the global option (title) and this option is obviously passed on to babel. Without the spaces, the errors don't occur.
Question: Can I prevent document class options from being used as global options by packages? Or is there some work-around akin to hypersetup{} for me to use instead of options? I could live with that.
babel documentclass-writing options kvoptions
I'm using kvoptions in my document class and it's worked nicely so far, but after a major rewrite I started getting strange errors that I was able to trace back to the babel package.
MWE:
%% myclass.cls
NeedsTeXFormat{LaTeX2e}[2018/04/01]
ProvidesClass{myclass}
RequirePackage[patch]{kvoptions}
DeclareStringOption{title}
ProcessKeyvalOptions*
LoadClass{article}
RequirePackage[english]{babel}
endinput
documentclass[title={Here be dragons}]{myclass}
begin{document}
Lorem Ipsum
end{document}
An excerpt from the log (paths omitted for brevity):
babel.sty:460: LaTeX Error: Missing begin{document}. [ {}}]
babel.sty:460: Too many }'s. [ {}}]
babel.sty:475: LaTeX Error: Missing begin{document}. [ ifin@edefbbl@tempc{bbl@tempb}fi}]
Without the kvoptions patch, the errors are getting worse:
babel.sty:339: LaTeX Error: Missing begin{document}. [ProcessOptions*]
babel.sty:339: You can't use `macro parameter character #' in horizontal mode. [ProcessOptions*]
TeX STOPPED: File ended while scanning use of reserved@{##1,##2reserved@b }def reserved@b ##1,reserved@b ##2reserved@b
TeX reports the error was in file:3
myclass.cls:13: LaTeX Error: Unknown option `english' for package `babel'. []
Analysis: The problem is that I have used spaces (and braces) in the global option (title) and this option is obviously passed on to babel. Without the spaces, the errors don't occur.
Question: Can I prevent document class options from being used as global options by packages? Or is there some work-around akin to hypersetup{} for me to use instead of options? I could live with that.
babel documentclass-writing options kvoptions
babel documentclass-writing options kvoptions
asked 8 mins ago
vbwxvbwx
1405
1405
add a comment |
add a comment |
0
active
oldest
votes
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%2f479552%2fincompatibility-between-kvoptions-and-babel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f479552%2fincompatibility-between-kvoptions-and-babel%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