Formatting issuesHow do I update my TeX distribution?What is the use of percent signs (%) at the end of...
GPL code private and stolen
How to develop an internal intuition for note timings?
Searching for a string that contains the file name
Where does the proton come in the reduction of NAD?
Plagiarism of code by other PhD student
The orphan's family
Remove object from array based on array of some property of that object
How will Occam's Razor principle work in Machine learning
How do I enter < and > on a broken keyboard?
How to concatenate two command in shell
An Undercover Army
Why do we see a rainbow of colors reflected off a CD or DVD?
What is the purpose of a disclaimer like "this is not legal advice"?
Why do phishing e-mails use faked e-mail addresses instead of the real one?
Is every open circuit a capacitor?
What is brightness?
Where is this quote about overcoming the impossible said in "Interstellar"?
I've given my players a lot of magic items. Is it reasonable for me to give them harder encounters?
What can I do if someone tampers with my SSH public key?
What kind of inflection is occuring in passive vb + かかった?
Was it really inappropriate to write a pull request for the company I interviewed with?
Is there a math equivalent to the conditional ternary operator?
Where is the fallacy here?
Can a Mexican citizen living in US under DACA drive to Canada?
Formatting issues
How do I update my TeX distribution?What is the use of percent signs (%) at the end of lines?Biblatex 3.3 name formattingCaption formatting with babel Frenchformatting epigrams using csquotesChicago Biblatex: Missing begin{document}Cleveref Appendices Environment. And default formattingFormatting - citetitle - dutch quotation styleBibLatex-Chicago: Formatting Chapter in Book (Citation)Formatting of symbols used as footnote markersbiblatex-chicago editor prefix formattingPolyglossia-Babelshorthands for quotes ignores csquotes formattingFixing formatting of journals with only issue numbers when using period to separate journal volume and issue number in biblatex-chicago
0
With the following code:
RequirePackage[
english,
ngerman]{babel}
RequirePackage[
autostyle = true,
babel,
german = quotes]{csquotes}
RequirePackage[
authordate,
bibencoding = auto,
strict,
backend = biber,
natbib
]{biblatex-chicago}
DeclareCaseLangs*{german}
bibliography{./_assets/bibliography.bib}
defbibheading{head}{chapter{Literaturverzeichnis}}
AtBeginBibliography{defUrlFont{scriptsizett}}
how do I get rid of the first part here before 2000?
babel csquotes biblatex-chicago german
asked 14 hours ago
JackJack
1
New contributor
Jack 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 |
0
With the following code:
RequirePackage[
english,
ngerman]{babel}
RequirePackage[
autostyle = true,
babel,
german = quotes]{csquotes}
RequirePackage[
authordate,
bibencoding = auto,
strict,
backend = biber,
natbib
]{biblatex-chicago}
DeclareCaseLangs*{german}
bibliography{./_assets/bibliography.bib}
defbibheading{head}{chapter{Literaturverzeichnis}}
AtBeginBibliography{defUrlFont{scriptsizett}}
how do I get rid of the first part here before 2000?
babel csquotes biblatex-chicago german
asked 14 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
1
Hmmm, sometimes output like that shows if the name format inbiblatexis not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts withdocumentclassand has abegin{document}...end{document}environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).
– moewe
10 hours ago
1
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (.aux,.bbl,.bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the.logfile of the last LaTeX run as well as the.blgfile (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).
– moewe
10 hours ago
DeclareCaseLangs*{german}looks quite dangerous. It enablesMakeSentenceCase*for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. WithDeclareCaseLangs*{german}title = {Ein kurzer Titel},will come out incorrectly as Ein kurzer titel.
– moewe
4 hours ago
add a comment |
0
0
0
With the following code:
RequirePackage[
english,
ngerman]{babel}
RequirePackage[
autostyle = true,
babel,
german = quotes]{csquotes}
RequirePackage[
authordate,
bibencoding = auto,
strict,
backend = biber,
natbib
]{biblatex-chicago}
DeclareCaseLangs*{german}
bibliography{./_assets/bibliography.bib}
defbibheading{head}{chapter{Literaturverzeichnis}}
AtBeginBibliography{defUrlFont{scriptsizett}}
how do I get rid of the first part here before 2000?
babel csquotes biblatex-chicago german
asked 14 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
With the following code:
RequirePackage[
english,
ngerman]{babel}
RequirePackage[
autostyle = true,
babel,
german = quotes]{csquotes}
RequirePackage[
authordate,
bibencoding = auto,
strict,
backend = biber,
natbib
]{biblatex-chicago}
DeclareCaseLangs*{german}
bibliography{./_assets/bibliography.bib}
defbibheading{head}{chapter{Literaturverzeichnis}}
AtBeginBibliography{defUrlFont{scriptsizett}}
how do I get rid of the first part here before 2000?
babel csquotes biblatex-chicago german
babel csquotes biblatex-chicago german
asked 14 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 14 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 14 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 14 hours ago
JackJack
1
asked 14 hours ago
JackJack
1
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
1
Hmmm, sometimes output like that shows if the name format inbiblatexis not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts withdocumentclassand has abegin{document}...end{document}environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).
– moewe
10 hours ago
1
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (.aux,.bbl,.bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the.logfile of the last LaTeX run as well as the.blgfile (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).
– moewe
10 hours ago
DeclareCaseLangs*{german}looks quite dangerous. It enablesMakeSentenceCase*for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. WithDeclareCaseLangs*{german}title = {Ein kurzer Titel},will come out incorrectly as Ein kurzer titel.
– moewe
4 hours ago
add a comment |
3
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
1
Hmmm, sometimes output like that shows if the name format inbiblatexis not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts withdocumentclassand has abegin{document}...end{document}environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).
– moewe
10 hours ago
1
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (.aux,.bbl,.bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the.logfile of the last LaTeX run as well as the.blgfile (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).
– moewe
10 hours ago
DeclareCaseLangs*{german}looks quite dangerous. It enablesMakeSentenceCase*for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. WithDeclareCaseLangs*{german}title = {Ein kurzer Titel},will come out incorrectly as Ein kurzer titel.
– moewe
4 hours ago
3
3
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
1
1
Hmmm, sometimes output like that shows if the name format in
biblatex is not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts with documentclass and has a begin{document}...end{document} environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).– moewe
10 hours ago
Hmmm, sometimes output like that shows if the name format in
biblatex is not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts with documentclass and has a begin{document}...end{document} environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).– moewe
10 hours ago
1
1
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (
.aux, .bbl, .bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the .log file of the last LaTeX run as well as the .blg file (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).– moewe
10 hours ago
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (
.aux, .bbl, .bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the .log file of the last LaTeX run as well as the .blg file (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).– moewe
10 hours ago
DeclareCaseLangs*{german} looks quite dangerous. It enables MakeSentenceCase* for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. With DeclareCaseLangs*{german} title = {Ein kurzer Titel}, will come out incorrectly as Ein kurzer titel.– moewe
4 hours ago
DeclareCaseLangs*{german} looks quite dangerous. It enables MakeSentenceCase* for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. With DeclareCaseLangs*{german} title = {Ein kurzer Titel}, will come out incorrectly as Ein kurzer titel.– moewe
4 hours ago
add a comment |
1 Answer
1
active
oldest
votes
0
I found the culprit:
DeclareNameFormat{sortname}{
iffirstinits
{usebibmacro{name:last-first}{#1}{#4}{#5}{#7}}
{usebibmacro{name:last-first}{#1}{#3}{#5}{#7}}
usebibmacro{name:andothers}
}
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
This is indeed outdated code for olderbiblatexversions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864
– moewe
5 hours ago
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
});
}
});
Jack is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
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%2f478123%2fformatting-issues%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
0
I found the culprit:
DeclareNameFormat{sortname}{
iffirstinits
{usebibmacro{name:last-first}{#1}{#4}{#5}{#7}}
{usebibmacro{name:last-first}{#1}{#3}{#5}{#7}}
usebibmacro{name:andothers}
}
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
This is indeed outdated code for olderbiblatexversions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864
– moewe
5 hours ago
add a comment |
0
I found the culprit:
DeclareNameFormat{sortname}{
iffirstinits
{usebibmacro{name:last-first}{#1}{#4}{#5}{#7}}
{usebibmacro{name:last-first}{#1}{#3}{#5}{#7}}
usebibmacro{name:andothers}
}
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
This is indeed outdated code for olderbiblatexversions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864
– moewe
5 hours ago
add a comment |
0
0
0
I found the culprit:
DeclareNameFormat{sortname}{
iffirstinits
{usebibmacro{name:last-first}{#1}{#4}{#5}{#7}}
{usebibmacro{name:last-first}{#1}{#3}{#5}{#7}}
usebibmacro{name:andothers}
}
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found the culprit:
DeclareNameFormat{sortname}{
iffirstinits
{usebibmacro{name:last-first}{#1}{#4}{#5}{#7}}
{usebibmacro{name:last-first}{#1}{#3}{#5}{#7}}
usebibmacro{name:andothers}
}
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 5 hours ago
JackJack
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 5 hours ago
JackJack
1
answered 5 hours ago
JackJack
1
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
This is indeed outdated code for olderbiblatexversions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864
– moewe
5 hours ago
add a comment |
2
This is indeed outdated code for olderbiblatexversions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864
– moewe
5 hours ago
2
2
This is indeed outdated code for older
biblatex versions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864– moewe
5 hours ago
This is indeed outdated code for older
biblatex versions: tex.stackexchange.com/q/299036/35864. Note that this code could also produce spurious spaces because of unprotected line ends: tex.stackexchange.com/q/7453/35864– moewe
5 hours ago
add a comment |
Jack is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Jack is a new contributor. Be nice, and check out our Code of Conduct.
Jack is a new contributor. Be nice, and check out our Code of Conduct.
Jack 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.
draft saved
draft discarded
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%2f478123%2fformatting-issues%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
3
Welcome to TeX SX! Could you post a small compilable code reproducing the problem?
– Bernard
14 hours ago
1
Hmmm, sometimes output like that shows if the name format in
biblatexis not set up correctly or if some auxiliary files are corrupted. Unfortunately, it is not possible to reproduce the issue with the information shared so far in the question. We would need to see a so-called MWE that starts withdocumentclassand has abegin{document}...end{document}environment (see also tex.meta.stackexchange.com/q/228/35864, tex.meta.stackexchange.com/q/4407/35864).– moewe
10 hours ago
1
Make sure that your package versions are compatible by performing a full system update (if you are using MikTeX update in admin and user mode, tex.stackexchange.com/q/55437/35864). Then delete the temporary files (
.aux,.bbl,.bcf, ...) and run the cycle LaTeX, Biber, LaTeX, LaTeX again. If the issue persists, please update the post with an MWE and include the.logfile of the last LaTeX run as well as the.blgfile (you can upload them to a text-sharing website such as pastebin.com, 0bin.net, ... if they are too long for the question).– moewe
10 hours ago
DeclareCaseLangs*{german}looks quite dangerous. It enablesMakeSentenceCase*for use with German. Which means that German titles will be subjected to English sentence case rules: The very first character is capitalised all other words will be in lower case. That will seriously mess with mandatory capitalisation rules in German and is therefore to be avoided. WithDeclareCaseLangs*{german}title = {Ein kurzer Titel},will come out incorrectly as Ein kurzer titel.– moewe
4 hours ago