You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The related entry feature is enabled by default by the package option \opt{related} from \secref{use:opt:pre:gen}. The related information entry data from the related entries is included via a \cmd{usebibmacro\{related\}} call. Standard styles call this macro towards the end of each driver. Style authors should ensure the existence of (or take note of existing) localization strings which are useful as values for the \bibfield{relatedtype} field, such as \texttt{translationof} or perhaps \texttt{translatedas}. They can then define macros and/or formats with the name \texttt{related:\prm{relatedtype}} which will be used to format the data. The package \path{biblatex.def} contains macros and formats for some common relation types which can be used as templates. In particular, the \cmd{entrydata*} command is essential in such macros in order to make the data of the related entries available. Examples of entries using this feature can be found in the \sty{biblatex} distribution examples file \path{biblatex-examples.bib}. There are some specific formatting macros for this feature which control delimiters and separators in related entry information, see \secref{aut:fmt:fmt}.
Using translatedas compiles without error (presumably as intended). I am now wondering if this is only something that needs to be fixed in the documentation or if translationas was indeed called translatedas before and there are other places where corrections need to be made.
The text was updated successfully, but these errors were encountered:
moewew
added a commit
to moewew/biblatex
that referenced
this issue
May 24, 2024
Thanks for catching that. I pushed cd38ac9 to change the docs to refer only to translationas. I guess translationas sounds more clunky (at least it does to me, but then I'm not a native English speaker) than translatedas, case in point:
But since we have all the setup for translationas we should probably stick with that.
You can use arbitrarily named relatedtypes, but if you use a type for which there exists a bibstring you get localised output etc. So there is no issue with translatedas working (or not working) as it does at the moment. But we should probably only advertise translationas in the docs.
Perhaps this is merely a documentation issue, but it appears that since 8950959#diff-7a310f17be14555280c15848ec66a41079361c6e091089e54918f0b87dd68360R2586,
relatedtype = {translationas}
has been calledrelatedtype = {translatedas}
in the documentation in two locations even before the proper documentation fortranslationas
was introduced in 50062d846d308c75757ed5be27f4f9e30d996563:biblatex/doc/latex/biblatex/biblatex.tex
Lines 2583 to 2588 in 8950959
biblatex/doc/latex/biblatex/biblatex.tex
Line 5464 in 8950959
These are still present today:
https://github.com/plk/biblatex/blob/ac2456c2492861451547659702ae4a72264e4997/doc/latex/biblatex/biblatex.tex#L3460-L3465
https://github.com/plk/biblatex/blob/ac2456c2492861451547659702ae4a72264e4997/doc/latex/biblatex/biblatex.tex#L8112
Using
translatedas
compiles without error (presumably as intended). I am now wondering if this is only something that needs to be fixed in the documentation or iftranslationas
was indeed calledtranslatedas
before and there are other places where corrections need to be made.The text was updated successfully, but these errors were encountered: