moewew
commented
1 month ago Thanks for catching that. I pushed https://github.com/plk/biblatex/commit/cd38ac9bcca03a9c60e1bfc1c2bddfd74891df2e 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 https://github.com/plk/biblatex/commit/895095929bf6d760ed501ed66edff96f0f88cab8#diff-7a310f17be14555280c15848ec66a41079361c6e091089e54918f0b87dd68360R2586,
relatedtype = {translationas}has been calledrelatedtype = {translatedas}in the documentation in two locations even before the proper documentation fortranslationaswas introduced in 50062d846d308c75757ed5be27f4f9e30d996563:https://github.com/plk/biblatex/blob/895095929bf6d760ed501ed66edff96f0f88cab8/doc/latex/biblatex/biblatex.tex#L2583-L2588
https://github.com/plk/biblatex/blob/895095929bf6d760ed501ed66edff96f0f88cab8/doc/latex/biblatex/biblatex.tex#L5464
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
translatedascompiles without error (presumably as intended). I am now wondering if this is only something that needs to be fixed in the documentation or iftranslationaswas indeed calledtranslatedasbefore and there are other places where corrections need to be made.