How does langid field in biblatex differ from language field?
Could someone summarise the differences in the use of the langid
field from language
field in biblatex
? Documentation to Gost
package for bibtex
says that langid
is a synonym of language
but has priority over it.
biblatex bibtex bibliographies
add a comment |
Could someone summarise the differences in the use of the langid
field from language
field in biblatex
? Documentation to Gost
package for bibtex
says that langid
is a synonym of language
but has priority over it.
biblatex bibtex bibliographies
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
Of course the meaning oflangid
in the BibTeX style for GOST has no bearing on the meaning of the field inbiblatex
. Thebiblatex-gost
documentation does not mention anything about thelangid
field being different in meaning to standardbiblatex
.
– moewe
Aug 5 '16 at 6:45
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
@moewe: I am still wondering what happens if bothlanguage
andlangid
are provided or if onlylanguage
or onlylangid
are gived and they bear dofferent values.
– Igor Kotelnikov
Aug 6 '16 at 8:34
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58
add a comment |
Could someone summarise the differences in the use of the langid
field from language
field in biblatex
? Documentation to Gost
package for bibtex
says that langid
is a synonym of language
but has priority over it.
biblatex bibtex bibliographies
Could someone summarise the differences in the use of the langid
field from language
field in biblatex
? Documentation to Gost
package for bibtex
says that langid
is a synonym of language
but has priority over it.
biblatex bibtex bibliographies
biblatex bibtex bibliographies
asked Aug 5 '16 at 4:39
Igor KotelnikovIgor Kotelnikov
7,13964282
7,13964282
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
Of course the meaning oflangid
in the BibTeX style for GOST has no bearing on the meaning of the field inbiblatex
. Thebiblatex-gost
documentation does not mention anything about thelangid
field being different in meaning to standardbiblatex
.
– moewe
Aug 5 '16 at 6:45
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
@moewe: I am still wondering what happens if bothlanguage
andlangid
are provided or if onlylanguage
or onlylangid
are gived and they bear dofferent values.
– Igor Kotelnikov
Aug 6 '16 at 8:34
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58
add a comment |
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
Of course the meaning oflangid
in the BibTeX style for GOST has no bearing on the meaning of the field inbiblatex
. Thebiblatex-gost
documentation does not mention anything about thelangid
field being different in meaning to standardbiblatex
.
– moewe
Aug 5 '16 at 6:45
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
@moewe: I am still wondering what happens if bothlanguage
andlangid
are provided or if onlylanguage
or onlylangid
are gived and they bear dofferent values.
– Igor Kotelnikov
Aug 6 '16 at 8:34
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
Of course the meaning of
langid
in the BibTeX style for GOST has no bearing on the meaning of the field in biblatex
. The biblatex-gost
documentation does not mention anything about the langid
field being different in meaning to standard biblatex
.– moewe
Aug 5 '16 at 6:45
Of course the meaning of
langid
in the BibTeX style for GOST has no bearing on the meaning of the field in biblatex
. The biblatex-gost
documentation does not mention anything about the langid
field being different in meaning to standard biblatex
.– moewe
Aug 5 '16 at 6:45
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
@moewe: I am still wondering what happens if both
language
and langid
are provided or if only language
or onlylangid
are gived and they bear dofferent values.– Igor Kotelnikov
Aug 6 '16 at 8:34
@moewe: I am still wondering what happens if both
language
and langid
are provided or if only language
or onlylangid
are gived and they bear dofferent values.– Igor Kotelnikov
Aug 6 '16 at 8:34
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58
add a comment |
1 Answer
1
active
oldest
votes
We have touched upon this subject before in Can I use a shortened “language” entry (language code) in my .bib file?, but let's make the distinction a bit more specific here.
The biblatex
documentation says (on pp. 25-26)
langid
field (identifier): The language id of the bibliography entry.
The aliashyphenation
is provided for backwards compatibility. The
identifier must be a language name known to thebabel
/polyglossia
packages. This information may be used to switch hyphenation patterns
and localise strings in the bibliography. Note that the language names
are case sensitive. The languages currently supported by this package
are given in table 2. [...]
and (p. 20)
language
list (key): The language(s) of the work. Languages may be
specified literally or as localisation keys. If localisation keys are
used, the prefixlang
is omissible.
That means that the langid
field holds the localisation you want to use for the entry in the bibliography (and citation depending on your language
option setting), it affects hyphenation patterns as well as localisation strings (the exact effect depends on the settings of the language
and autolang
options). Because this is an internal directive for biblatex
the information must be given in a form that TeX understands, you can use babel
/polyglossia
language identifiers and with Biber even BCP47 language codes.
If you want to prepare a multi-language bibliography, it is recommended to provide langid
for all entries. Only with that information can LaTeX properly switch language environments and possibly fonts and encodings to avoid errors or unwanted output.
The language
list on the other hand has no special internal meaning, it just holds the language you want to see printed in the bibliography as the language of the work (in the standard styles the language is printed directly after the title, by default the option clearlang
suppresses output of languages that match the document language). biblatex
offers some localisation support for this ("known" languages are listed in §4.9.2.18 Language Names), so you can either give the language "key" (russian
, langrussian
) in which case biblatex
will translate the field for you, or you can give the content verbatim in case the language is not supported (Klingon
).
As far as biblatex
is concerned the two fields are completely independent. They do not influence each other. And you can have only one of the two fields filled, or both, or none – and the contents of the field need not be equivalent. You can, for example, have
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
Which tells biblatex
(mistakenly) to treat the work as German (new orthography) (langid = {ngerman}
), hyphenation and localisation strings will be changed accordingly (depending on your language
and autolang
options). However, since we have language={french and latin}
"French and Latin" will be printed as the language(s) of the work. It would of course make no sense to give two languages as langid
, but it may very well be that you want to convey the information that a work is bilingual French and Latin.
In
documentclass[ngerman,british]{article}
usepackage{babel}
usepackage{csquotes}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
end{filecontents}
usepackage[backend=biber,style=authoryear,autolang=other]{biblatex}
addbibresource{jobname.bib}
begin{document}
nocite{elk}
printbibliography
end{document}
we thus get
Elk, Anne (2016). A Theory on Brontosauruses. Französisch und Lateinisch. URL: http://www.example.edu/~elk/bronto.pdf.
Note that even though the main language of the document is british
, the information that the work is in French and Latin ("französisch und lateinisch", language={french and latin}
) is printed in German (langid={ngerman}
).
In multilanguage bibliographies the absence oflangid
in entries can produceLaTeX Error: Command ... unavailable in encoding T1
.
– homocomputeris
Oct 17 '18 at 19:48
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%2f323441%2fhow-does-langid-field-in-biblatex-differ-from-language-field%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
We have touched upon this subject before in Can I use a shortened “language” entry (language code) in my .bib file?, but let's make the distinction a bit more specific here.
The biblatex
documentation says (on pp. 25-26)
langid
field (identifier): The language id of the bibliography entry.
The aliashyphenation
is provided for backwards compatibility. The
identifier must be a language name known to thebabel
/polyglossia
packages. This information may be used to switch hyphenation patterns
and localise strings in the bibliography. Note that the language names
are case sensitive. The languages currently supported by this package
are given in table 2. [...]
and (p. 20)
language
list (key): The language(s) of the work. Languages may be
specified literally or as localisation keys. If localisation keys are
used, the prefixlang
is omissible.
That means that the langid
field holds the localisation you want to use for the entry in the bibliography (and citation depending on your language
option setting), it affects hyphenation patterns as well as localisation strings (the exact effect depends on the settings of the language
and autolang
options). Because this is an internal directive for biblatex
the information must be given in a form that TeX understands, you can use babel
/polyglossia
language identifiers and with Biber even BCP47 language codes.
If you want to prepare a multi-language bibliography, it is recommended to provide langid
for all entries. Only with that information can LaTeX properly switch language environments and possibly fonts and encodings to avoid errors or unwanted output.
The language
list on the other hand has no special internal meaning, it just holds the language you want to see printed in the bibliography as the language of the work (in the standard styles the language is printed directly after the title, by default the option clearlang
suppresses output of languages that match the document language). biblatex
offers some localisation support for this ("known" languages are listed in §4.9.2.18 Language Names), so you can either give the language "key" (russian
, langrussian
) in which case biblatex
will translate the field for you, or you can give the content verbatim in case the language is not supported (Klingon
).
As far as biblatex
is concerned the two fields are completely independent. They do not influence each other. And you can have only one of the two fields filled, or both, or none – and the contents of the field need not be equivalent. You can, for example, have
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
Which tells biblatex
(mistakenly) to treat the work as German (new orthography) (langid = {ngerman}
), hyphenation and localisation strings will be changed accordingly (depending on your language
and autolang
options). However, since we have language={french and latin}
"French and Latin" will be printed as the language(s) of the work. It would of course make no sense to give two languages as langid
, but it may very well be that you want to convey the information that a work is bilingual French and Latin.
In
documentclass[ngerman,british]{article}
usepackage{babel}
usepackage{csquotes}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
end{filecontents}
usepackage[backend=biber,style=authoryear,autolang=other]{biblatex}
addbibresource{jobname.bib}
begin{document}
nocite{elk}
printbibliography
end{document}
we thus get
Elk, Anne (2016). A Theory on Brontosauruses. Französisch und Lateinisch. URL: http://www.example.edu/~elk/bronto.pdf.
Note that even though the main language of the document is british
, the information that the work is in French and Latin ("französisch und lateinisch", language={french and latin}
) is printed in German (langid={ngerman}
).
In multilanguage bibliographies the absence oflangid
in entries can produceLaTeX Error: Command ... unavailable in encoding T1
.
– homocomputeris
Oct 17 '18 at 19:48
add a comment |
We have touched upon this subject before in Can I use a shortened “language” entry (language code) in my .bib file?, but let's make the distinction a bit more specific here.
The biblatex
documentation says (on pp. 25-26)
langid
field (identifier): The language id of the bibliography entry.
The aliashyphenation
is provided for backwards compatibility. The
identifier must be a language name known to thebabel
/polyglossia
packages. This information may be used to switch hyphenation patterns
and localise strings in the bibliography. Note that the language names
are case sensitive. The languages currently supported by this package
are given in table 2. [...]
and (p. 20)
language
list (key): The language(s) of the work. Languages may be
specified literally or as localisation keys. If localisation keys are
used, the prefixlang
is omissible.
That means that the langid
field holds the localisation you want to use for the entry in the bibliography (and citation depending on your language
option setting), it affects hyphenation patterns as well as localisation strings (the exact effect depends on the settings of the language
and autolang
options). Because this is an internal directive for biblatex
the information must be given in a form that TeX understands, you can use babel
/polyglossia
language identifiers and with Biber even BCP47 language codes.
If you want to prepare a multi-language bibliography, it is recommended to provide langid
for all entries. Only with that information can LaTeX properly switch language environments and possibly fonts and encodings to avoid errors or unwanted output.
The language
list on the other hand has no special internal meaning, it just holds the language you want to see printed in the bibliography as the language of the work (in the standard styles the language is printed directly after the title, by default the option clearlang
suppresses output of languages that match the document language). biblatex
offers some localisation support for this ("known" languages are listed in §4.9.2.18 Language Names), so you can either give the language "key" (russian
, langrussian
) in which case biblatex
will translate the field for you, or you can give the content verbatim in case the language is not supported (Klingon
).
As far as biblatex
is concerned the two fields are completely independent. They do not influence each other. And you can have only one of the two fields filled, or both, or none – and the contents of the field need not be equivalent. You can, for example, have
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
Which tells biblatex
(mistakenly) to treat the work as German (new orthography) (langid = {ngerman}
), hyphenation and localisation strings will be changed accordingly (depending on your language
and autolang
options). However, since we have language={french and latin}
"French and Latin" will be printed as the language(s) of the work. It would of course make no sense to give two languages as langid
, but it may very well be that you want to convey the information that a work is bilingual French and Latin.
In
documentclass[ngerman,british]{article}
usepackage{babel}
usepackage{csquotes}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
end{filecontents}
usepackage[backend=biber,style=authoryear,autolang=other]{biblatex}
addbibresource{jobname.bib}
begin{document}
nocite{elk}
printbibliography
end{document}
we thus get
Elk, Anne (2016). A Theory on Brontosauruses. Französisch und Lateinisch. URL: http://www.example.edu/~elk/bronto.pdf.
Note that even though the main language of the document is british
, the information that the work is in French and Latin ("französisch und lateinisch", language={french and latin}
) is printed in German (langid={ngerman}
).
In multilanguage bibliographies the absence oflangid
in entries can produceLaTeX Error: Command ... unavailable in encoding T1
.
– homocomputeris
Oct 17 '18 at 19:48
add a comment |
We have touched upon this subject before in Can I use a shortened “language” entry (language code) in my .bib file?, but let's make the distinction a bit more specific here.
The biblatex
documentation says (on pp. 25-26)
langid
field (identifier): The language id of the bibliography entry.
The aliashyphenation
is provided for backwards compatibility. The
identifier must be a language name known to thebabel
/polyglossia
packages. This information may be used to switch hyphenation patterns
and localise strings in the bibliography. Note that the language names
are case sensitive. The languages currently supported by this package
are given in table 2. [...]
and (p. 20)
language
list (key): The language(s) of the work. Languages may be
specified literally or as localisation keys. If localisation keys are
used, the prefixlang
is omissible.
That means that the langid
field holds the localisation you want to use for the entry in the bibliography (and citation depending on your language
option setting), it affects hyphenation patterns as well as localisation strings (the exact effect depends on the settings of the language
and autolang
options). Because this is an internal directive for biblatex
the information must be given in a form that TeX understands, you can use babel
/polyglossia
language identifiers and with Biber even BCP47 language codes.
If you want to prepare a multi-language bibliography, it is recommended to provide langid
for all entries. Only with that information can LaTeX properly switch language environments and possibly fonts and encodings to avoid errors or unwanted output.
The language
list on the other hand has no special internal meaning, it just holds the language you want to see printed in the bibliography as the language of the work (in the standard styles the language is printed directly after the title, by default the option clearlang
suppresses output of languages that match the document language). biblatex
offers some localisation support for this ("known" languages are listed in §4.9.2.18 Language Names), so you can either give the language "key" (russian
, langrussian
) in which case biblatex
will translate the field for you, or you can give the content verbatim in case the language is not supported (Klingon
).
As far as biblatex
is concerned the two fields are completely independent. They do not influence each other. And you can have only one of the two fields filled, or both, or none – and the contents of the field need not be equivalent. You can, for example, have
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
Which tells biblatex
(mistakenly) to treat the work as German (new orthography) (langid = {ngerman}
), hyphenation and localisation strings will be changed accordingly (depending on your language
and autolang
options). However, since we have language={french and latin}
"French and Latin" will be printed as the language(s) of the work. It would of course make no sense to give two languages as langid
, but it may very well be that you want to convey the information that a work is bilingual French and Latin.
In
documentclass[ngerman,british]{article}
usepackage{babel}
usepackage{csquotes}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
end{filecontents}
usepackage[backend=biber,style=authoryear,autolang=other]{biblatex}
addbibresource{jobname.bib}
begin{document}
nocite{elk}
printbibliography
end{document}
we thus get
Elk, Anne (2016). A Theory on Brontosauruses. Französisch und Lateinisch. URL: http://www.example.edu/~elk/bronto.pdf.
Note that even though the main language of the document is british
, the information that the work is in French and Latin ("französisch und lateinisch", language={french and latin}
) is printed in German (langid={ngerman}
).
We have touched upon this subject before in Can I use a shortened “language” entry (language code) in my .bib file?, but let's make the distinction a bit more specific here.
The biblatex
documentation says (on pp. 25-26)
langid
field (identifier): The language id of the bibliography entry.
The aliashyphenation
is provided for backwards compatibility. The
identifier must be a language name known to thebabel
/polyglossia
packages. This information may be used to switch hyphenation patterns
and localise strings in the bibliography. Note that the language names
are case sensitive. The languages currently supported by this package
are given in table 2. [...]
and (p. 20)
language
list (key): The language(s) of the work. Languages may be
specified literally or as localisation keys. If localisation keys are
used, the prefixlang
is omissible.
That means that the langid
field holds the localisation you want to use for the entry in the bibliography (and citation depending on your language
option setting), it affects hyphenation patterns as well as localisation strings (the exact effect depends on the settings of the language
and autolang
options). Because this is an internal directive for biblatex
the information must be given in a form that TeX understands, you can use babel
/polyglossia
language identifiers and with Biber even BCP47 language codes.
If you want to prepare a multi-language bibliography, it is recommended to provide langid
for all entries. Only with that information can LaTeX properly switch language environments and possibly fonts and encodings to avoid errors or unwanted output.
The language
list on the other hand has no special internal meaning, it just holds the language you want to see printed in the bibliography as the language of the work (in the standard styles the language is printed directly after the title, by default the option clearlang
suppresses output of languages that match the document language). biblatex
offers some localisation support for this ("known" languages are listed in §4.9.2.18 Language Names), so you can either give the language "key" (russian
, langrussian
) in which case biblatex
will translate the field for you, or you can give the content verbatim in case the language is not supported (Klingon
).
As far as biblatex
is concerned the two fields are completely independent. They do not influence each other. And you can have only one of the two fields filled, or both, or none – and the contents of the field need not be equivalent. You can, for example, have
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
Which tells biblatex
(mistakenly) to treat the work as German (new orthography) (langid = {ngerman}
), hyphenation and localisation strings will be changed accordingly (depending on your language
and autolang
options). However, since we have language={french and latin}
"French and Latin" will be printed as the language(s) of the work. It would of course make no sense to give two languages as langid
, but it may very well be that you want to convey the information that a work is bilingual French and Latin.
In
documentclass[ngerman,british]{article}
usepackage{babel}
usepackage{csquotes}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@online{elk,
author = {Anne Elk},
title = {A Theory on Brontosauruses},
url = {http://www.example.edu/~elk/bronto.pdf},
date = {2016-01-01},
language = {french and latin},
langid = {ngerman},
}
end{filecontents}
usepackage[backend=biber,style=authoryear,autolang=other]{biblatex}
addbibresource{jobname.bib}
begin{document}
nocite{elk}
printbibliography
end{document}
we thus get
Elk, Anne (2016). A Theory on Brontosauruses. Französisch und Lateinisch. URL: http://www.example.edu/~elk/bronto.pdf.
Note that even though the main language of the document is british
, the information that the work is in French and Latin ("französisch und lateinisch", language={french and latin}
) is printed in German (langid={ngerman}
).
edited 22 mins ago
answered Aug 6 '16 at 13:57
moewemoewe
92k10115348
92k10115348
In multilanguage bibliographies the absence oflangid
in entries can produceLaTeX Error: Command ... unavailable in encoding T1
.
– homocomputeris
Oct 17 '18 at 19:48
add a comment |
In multilanguage bibliographies the absence oflangid
in entries can produceLaTeX Error: Command ... unavailable in encoding T1
.
– homocomputeris
Oct 17 '18 at 19:48
In multilanguage bibliographies the absence of
langid
in entries can produce LaTeX Error: Command ... unavailable in encoding T1
.– homocomputeris
Oct 17 '18 at 19:48
In multilanguage bibliographies the absence of
langid
in entries can produce LaTeX Error: Command ... unavailable in encoding T1
.– homocomputeris
Oct 17 '18 at 19:48
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%2f323441%2fhow-does-langid-field-in-biblatex-differ-from-language-field%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
The difference is explained in the answer to Can I use a shortened “language” entry (language code) in my .bib file? So while the titles do not suggest it, your question is pretty much a duplicate. Is there anything you are missing in the answer there?
– moewe
Aug 5 '16 at 6:31
Of course the meaning of
langid
in the BibTeX style for GOST has no bearing on the meaning of the field inbiblatex
. Thebiblatex-gost
documentation does not mention anything about thelangid
field being different in meaning to standardbiblatex
.– moewe
Aug 5 '16 at 6:45
Does the question linked above answer your question? I'm very much tempted to vote to close your question as a duplicate.
– moewe
Aug 6 '16 at 6:57
@moewe: I am still wondering what happens if both
language
andlangid
are provided or if onlylanguage
or onlylangid
are gived and they bear dofferent values.– Igor Kotelnikov
Aug 6 '16 at 8:34
OK, I have tried to make this more explicit in my answer below, please comment if you have any more questions or if you can think of any improvement.
– moewe
Aug 6 '16 at 13:58