fontspec changes indentation of biblatex bibliography
MWE:
test.tex:
% !TeX program = xelatex
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}
addbibresource{resources.bib}
begin{document}
cite{Test.2018}
printbibliography
end{document}
resources.bib:
@misc{Test.2018,
author = {{Test}},
year = {2018},
title = {Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.}
}
Adding usepackage{fontspec}
decreases the indentation of the biblatex entries in the bibliography, removing it increases it again. Why?
I came across this problem after trying to break a long url in the bibliography of an article. The decreased indentation changes the breakpoint. Furthermore it makes the url overflow by one stubborn character even though I set biburllcpenalty and biburlucpenalty accordingly. Without using fontspec there is no overflow.
biblatex xetex koma-script fontspec
add a comment |
MWE:
test.tex:
% !TeX program = xelatex
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}
addbibresource{resources.bib}
begin{document}
cite{Test.2018}
printbibliography
end{document}
resources.bib:
@misc{Test.2018,
author = {{Test}},
year = {2018},
title = {Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.}
}
Adding usepackage{fontspec}
decreases the indentation of the biblatex entries in the bibliography, removing it increases it again. Why?
I came across this problem after trying to break a long url in the bibliography of an article. The decreased indentation changes the breakpoint. Furthermore it makes the url overflow by one stubborn character even though I set biburllcpenalty and biburlucpenalty accordingly. Without using fontspec there is no overflow.
biblatex xetex koma-script fontspec
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41
add a comment |
MWE:
test.tex:
% !TeX program = xelatex
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}
addbibresource{resources.bib}
begin{document}
cite{Test.2018}
printbibliography
end{document}
resources.bib:
@misc{Test.2018,
author = {{Test}},
year = {2018},
title = {Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.}
}
Adding usepackage{fontspec}
decreases the indentation of the biblatex entries in the bibliography, removing it increases it again. Why?
I came across this problem after trying to break a long url in the bibliography of an article. The decreased indentation changes the breakpoint. Furthermore it makes the url overflow by one stubborn character even though I set biburllcpenalty and biburlucpenalty accordingly. Without using fontspec there is no overflow.
biblatex xetex koma-script fontspec
MWE:
test.tex:
% !TeX program = xelatex
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}
addbibresource{resources.bib}
begin{document}
cite{Test.2018}
printbibliography
end{document}
resources.bib:
@misc{Test.2018,
author = {{Test}},
year = {2018},
title = {Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.}
}
Adding usepackage{fontspec}
decreases the indentation of the biblatex entries in the bibliography, removing it increases it again. Why?
I came across this problem after trying to break a long url in the bibliography of an article. The decreased indentation changes the breakpoint. Furthermore it makes the url overflow by one stubborn character even though I set biburllcpenalty and biburlucpenalty accordingly. Without using fontspec there is no overflow.
biblatex xetex koma-script fontspec
biblatex xetex koma-script fontspec
edited Dec 16 at 18:12
asked Dec 16 at 0:52
Young Un
905
905
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41
add a comment |
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41
add a comment |
1 Answer
1
active
oldest
votes
Probably someone who knows KOMA-Script better may be able to give a more precise answer. But, as far as I was able to understand, this behavior hangs on how scrartcl
class handles parindent
which is, in turn, used by biblatex to set the bibliography hanging indent.
biblatex uses the length bibhang
on the bibenvironment of the authoryear
style. And it is set in biblatex.def
with:
setlength{bibhang}{ifnumequal{parindent}{0}{1em}{parindent}}
Which will set bibhang
to parindent
but default bibhang
to 1em if parindent
is 0 for some reason, which is not the case here (that is parindent
is not 0, so bibhang
actually receives parindent
).
Now if we build the document below with XeLaTeX:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
typeout{theparindent}
begin{document}
theparindent
end{document}
The PDF will print "12.0pt", but we will find "20.0pt" in the log.
This means that, for some reason, parindent
is 20pt in the preamble, and 12pt in the document. biblatex sets bibhang
in the preamble, thus, in the absence of other intervening packages, takes the value of 20pt.
Now, if we add fontspec
to the document:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
typeout{theparindent}
begin{document}
theparindent
end{document}
We will find "12pt" in both the document and the log. So, if biblatex
is called after fontspec
, it will receive now the value of 12pt.
This doesn't really mean that fontspec
is responsible for this setting on it's own. As far as I grasp, it is more likely bringing some KOMA hook anticipating the setting which would otherwise come "at begin document". For example, if we substitute the call to fontspec
with KOMA's recalctypearea
, we get the same result: 12pt in both the document and the log.
documentclass[paper=A4,fontsize=12pt]{scrartcl}
recalctypearea
typeout{theparindent}
begin{document}
theparindent
end{document}
This explains why, in scrartcl
class, if you load biblatex
after fontspec
you get different bibhang
s. But I cannot really explain why parindent
works the way it does in scrartcl
.
Still, as you probably want fontspec
anyway in your document, this discussion is more of a curiosity. You woudn't want to remove fontspec
just because, by sheer chance (yes, a change in bibhang
may trigger an overfull hbox in you url) it allows for a better line break in a single bib entry. So you'll have to look for some other form to break your entry's url (there are several answers in this site on this subject).
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set thebibhang
in the preamble to avoid having to have the user go throughAtBeginDocument
hooks.
– moewe
Dec 16 at 10:23
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
|
show 1 more 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%2f466036%2ffontspec-changes-indentation-of-biblatex-bibliography%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
Probably someone who knows KOMA-Script better may be able to give a more precise answer. But, as far as I was able to understand, this behavior hangs on how scrartcl
class handles parindent
which is, in turn, used by biblatex to set the bibliography hanging indent.
biblatex uses the length bibhang
on the bibenvironment of the authoryear
style. And it is set in biblatex.def
with:
setlength{bibhang}{ifnumequal{parindent}{0}{1em}{parindent}}
Which will set bibhang
to parindent
but default bibhang
to 1em if parindent
is 0 for some reason, which is not the case here (that is parindent
is not 0, so bibhang
actually receives parindent
).
Now if we build the document below with XeLaTeX:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
typeout{theparindent}
begin{document}
theparindent
end{document}
The PDF will print "12.0pt", but we will find "20.0pt" in the log.
This means that, for some reason, parindent
is 20pt in the preamble, and 12pt in the document. biblatex sets bibhang
in the preamble, thus, in the absence of other intervening packages, takes the value of 20pt.
Now, if we add fontspec
to the document:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
typeout{theparindent}
begin{document}
theparindent
end{document}
We will find "12pt" in both the document and the log. So, if biblatex
is called after fontspec
, it will receive now the value of 12pt.
This doesn't really mean that fontspec
is responsible for this setting on it's own. As far as I grasp, it is more likely bringing some KOMA hook anticipating the setting which would otherwise come "at begin document". For example, if we substitute the call to fontspec
with KOMA's recalctypearea
, we get the same result: 12pt in both the document and the log.
documentclass[paper=A4,fontsize=12pt]{scrartcl}
recalctypearea
typeout{theparindent}
begin{document}
theparindent
end{document}
This explains why, in scrartcl
class, if you load biblatex
after fontspec
you get different bibhang
s. But I cannot really explain why parindent
works the way it does in scrartcl
.
Still, as you probably want fontspec
anyway in your document, this discussion is more of a curiosity. You woudn't want to remove fontspec
just because, by sheer chance (yes, a change in bibhang
may trigger an overfull hbox in you url) it allows for a better line break in a single bib entry. So you'll have to look for some other form to break your entry's url (there are several answers in this site on this subject).
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set thebibhang
in the preamble to avoid having to have the user go throughAtBeginDocument
hooks.
– moewe
Dec 16 at 10:23
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
|
show 1 more comment
Probably someone who knows KOMA-Script better may be able to give a more precise answer. But, as far as I was able to understand, this behavior hangs on how scrartcl
class handles parindent
which is, in turn, used by biblatex to set the bibliography hanging indent.
biblatex uses the length bibhang
on the bibenvironment of the authoryear
style. And it is set in biblatex.def
with:
setlength{bibhang}{ifnumequal{parindent}{0}{1em}{parindent}}
Which will set bibhang
to parindent
but default bibhang
to 1em if parindent
is 0 for some reason, which is not the case here (that is parindent
is not 0, so bibhang
actually receives parindent
).
Now if we build the document below with XeLaTeX:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
typeout{theparindent}
begin{document}
theparindent
end{document}
The PDF will print "12.0pt", but we will find "20.0pt" in the log.
This means that, for some reason, parindent
is 20pt in the preamble, and 12pt in the document. biblatex sets bibhang
in the preamble, thus, in the absence of other intervening packages, takes the value of 20pt.
Now, if we add fontspec
to the document:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
typeout{theparindent}
begin{document}
theparindent
end{document}
We will find "12pt" in both the document and the log. So, if biblatex
is called after fontspec
, it will receive now the value of 12pt.
This doesn't really mean that fontspec
is responsible for this setting on it's own. As far as I grasp, it is more likely bringing some KOMA hook anticipating the setting which would otherwise come "at begin document". For example, if we substitute the call to fontspec
with KOMA's recalctypearea
, we get the same result: 12pt in both the document and the log.
documentclass[paper=A4,fontsize=12pt]{scrartcl}
recalctypearea
typeout{theparindent}
begin{document}
theparindent
end{document}
This explains why, in scrartcl
class, if you load biblatex
after fontspec
you get different bibhang
s. But I cannot really explain why parindent
works the way it does in scrartcl
.
Still, as you probably want fontspec
anyway in your document, this discussion is more of a curiosity. You woudn't want to remove fontspec
just because, by sheer chance (yes, a change in bibhang
may trigger an overfull hbox in you url) it allows for a better line break in a single bib entry. So you'll have to look for some other form to break your entry's url (there are several answers in this site on this subject).
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set thebibhang
in the preamble to avoid having to have the user go throughAtBeginDocument
hooks.
– moewe
Dec 16 at 10:23
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
|
show 1 more comment
Probably someone who knows KOMA-Script better may be able to give a more precise answer. But, as far as I was able to understand, this behavior hangs on how scrartcl
class handles parindent
which is, in turn, used by biblatex to set the bibliography hanging indent.
biblatex uses the length bibhang
on the bibenvironment of the authoryear
style. And it is set in biblatex.def
with:
setlength{bibhang}{ifnumequal{parindent}{0}{1em}{parindent}}
Which will set bibhang
to parindent
but default bibhang
to 1em if parindent
is 0 for some reason, which is not the case here (that is parindent
is not 0, so bibhang
actually receives parindent
).
Now if we build the document below with XeLaTeX:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
typeout{theparindent}
begin{document}
theparindent
end{document}
The PDF will print "12.0pt", but we will find "20.0pt" in the log.
This means that, for some reason, parindent
is 20pt in the preamble, and 12pt in the document. biblatex sets bibhang
in the preamble, thus, in the absence of other intervening packages, takes the value of 20pt.
Now, if we add fontspec
to the document:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
typeout{theparindent}
begin{document}
theparindent
end{document}
We will find "12pt" in both the document and the log. So, if biblatex
is called after fontspec
, it will receive now the value of 12pt.
This doesn't really mean that fontspec
is responsible for this setting on it's own. As far as I grasp, it is more likely bringing some KOMA hook anticipating the setting which would otherwise come "at begin document". For example, if we substitute the call to fontspec
with KOMA's recalctypearea
, we get the same result: 12pt in both the document and the log.
documentclass[paper=A4,fontsize=12pt]{scrartcl}
recalctypearea
typeout{theparindent}
begin{document}
theparindent
end{document}
This explains why, in scrartcl
class, if you load biblatex
after fontspec
you get different bibhang
s. But I cannot really explain why parindent
works the way it does in scrartcl
.
Still, as you probably want fontspec
anyway in your document, this discussion is more of a curiosity. You woudn't want to remove fontspec
just because, by sheer chance (yes, a change in bibhang
may trigger an overfull hbox in you url) it allows for a better line break in a single bib entry. So you'll have to look for some other form to break your entry's url (there are several answers in this site on this subject).
Probably someone who knows KOMA-Script better may be able to give a more precise answer. But, as far as I was able to understand, this behavior hangs on how scrartcl
class handles parindent
which is, in turn, used by biblatex to set the bibliography hanging indent.
biblatex uses the length bibhang
on the bibenvironment of the authoryear
style. And it is set in biblatex.def
with:
setlength{bibhang}{ifnumequal{parindent}{0}{1em}{parindent}}
Which will set bibhang
to parindent
but default bibhang
to 1em if parindent
is 0 for some reason, which is not the case here (that is parindent
is not 0, so bibhang
actually receives parindent
).
Now if we build the document below with XeLaTeX:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
typeout{theparindent}
begin{document}
theparindent
end{document}
The PDF will print "12.0pt", but we will find "20.0pt" in the log.
This means that, for some reason, parindent
is 20pt in the preamble, and 12pt in the document. biblatex sets bibhang
in the preamble, thus, in the absence of other intervening packages, takes the value of 20pt.
Now, if we add fontspec
to the document:
documentclass[paper=A4,fontsize=12pt]{scrartcl}
usepackage{fontspec}
typeout{theparindent}
begin{document}
theparindent
end{document}
We will find "12pt" in both the document and the log. So, if biblatex
is called after fontspec
, it will receive now the value of 12pt.
This doesn't really mean that fontspec
is responsible for this setting on it's own. As far as I grasp, it is more likely bringing some KOMA hook anticipating the setting which would otherwise come "at begin document". For example, if we substitute the call to fontspec
with KOMA's recalctypearea
, we get the same result: 12pt in both the document and the log.
documentclass[paper=A4,fontsize=12pt]{scrartcl}
recalctypearea
typeout{theparindent}
begin{document}
theparindent
end{document}
This explains why, in scrartcl
class, if you load biblatex
after fontspec
you get different bibhang
s. But I cannot really explain why parindent
works the way it does in scrartcl
.
Still, as you probably want fontspec
anyway in your document, this discussion is more of a curiosity. You woudn't want to remove fontspec
just because, by sheer chance (yes, a change in bibhang
may trigger an overfull hbox in you url) it allows for a better line break in a single bib entry. So you'll have to look for some other form to break your entry's url (there are several answers in this site on this subject).
edited Dec 16 at 2:45
answered Dec 16 at 2:28
gusbrs
6,9542840
6,9542840
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set thebibhang
in the preamble to avoid having to have the user go throughAtBeginDocument
hooks.
– moewe
Dec 16 at 10:23
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
|
show 1 more comment
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set thebibhang
in the preamble to avoid having to have the user go throughAtBeginDocument
hooks.
– moewe
Dec 16 at 10:23
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
5
5
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
+1. A very thorough analysis!
– Mico
Dec 16 at 6:23
3
3
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
If biblatex uses parindent in the preamble it is a biblatex error. Packages shouldn't expect font dependant values to be correct there.
– Ulrike Fischer
Dec 16 at 9:30
1
1
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
See github.com/plk/biblatex/issues/848
– moewe
Dec 16 at 10:16
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set the
bibhang
in the preamble to avoid having to have the user go through AtBeginDocument
hooks.– moewe
Dec 16 at 10:23
@UlrikeFischer See link above. Is there any way to delay the expansion here? I don't want to set the
bibhang
in the preamble to avoid having to have the user go through AtBeginDocument
hooks.– moewe
Dec 16 at 10:23
2
2
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
@YoungUn Some, in no particular order, and non exhaustive: tex.stackexchange.com/q/372003/105447 ; tex.stackexchange.com/q/115690/105447 ; tex.stackexchange.com/q/15653/105447 ; tex.stackexchange.com/q/78093/105447 . If those, or other you may find, do not help, I suggest you ask a new question, then adding the example you later added. Here I focused on your question, as initially posed.
– gusbrs
Dec 16 at 17:52
|
show 1 more 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f466036%2ffontspec-changes-indentation-of-biblatex-bibliography%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
Welcome to TeX.SE! I can confirm this with current MiKTeX 2.9 and Windows 8.1. Which tex distribution and OS do you use? Can you add the bibentrx of the article which shows the issue with the url?
– Kurt
Dec 16 at 1:41