Problem with TL'24

[pauloney]

This is an MWE that works perfectly well in TL'23:

\documentclass{article}
\begin{filecontents*}{\jobname.bib}
@BOOK{Rudin,
    author = {Rudin, W.},
    note = {Also available in Chinese in \textcite{Rudin-chi}},
    pages = {x+342},
    publisher = {McGraw-Hill},
    series = {International Series in Pure and Applied Mathematics},
    title = {Principles of Mathematical Analysis},
    year = {1987},
    langid = {english},
}

@book{Rudin-chi,
     author = {Rudin, W.},
      title = {\textchinese{分析學探源}},
  publisher = {\textchinese{聯經出版事業公司}},
    address = {\textchinese{台北市}},
       note = {English original in \textcite{Rudin}},
       year = {1979},
     langid = {chinese},
}
\end{filecontents*}

\usepackage{polyglossia}
\usepackage{csquotes}
\setmainlanguage{english}
\setotherlanguage{chinese}

\newfontfamily\chinesefont[Script=CJK,Scale=0.9]{Noto Serif CJK JP}

\usepackage[style=authoryear,
            language=auto,
            autolang=other,
            backend=biber]{biblatex}

\addbibresource{\jobname.bib}

\begin{document}
\nocite{*}
\printbibliography
\end{document}

but after I upgraded today to TL'24, I get:

! LaTeX Error: \begin{document} ended by \end{otherlanguage}.

And removing the \textchinese{} commands to use the "langid" field does not help either. Same error occur.

[moewew]

I can't test right now because I'm at the wrong computer, but this could be related to #1350 (unfortunately, the solution for #1348 is far from straightforward, so we haven't come round to releasing the fix yet - we probably should, but I'll be pretty busy over the next weeks and away from the right machines).

[pauloney]

Do you know if the raw-TL'24 (without updates) would be a better option? I am trying to find a temp solution because of a big deadline before classes start ...

…

On Fri, Aug 23, 2024 at 1:51 AM moewew ***@***.***> wrote: I can't test right now because I'm at the wrong computer, but this could be related to #1350 <#1350> (unfortunately, the solution for #1348 <#1348> is far from straightforward, so we haven't come round to releasing the fix yet - we probably should, but I'll be pretty busy over the next weeks and away from the right machines). — Reply to this email directly, view it on GitHub <#1377 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR7WYXFDPKZF7DH5K2ZCETZS3ZXLAVCNFSM6AAAAABM65ZG6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBWGYYTKNRTGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[moewew]

I think, biblatex v3.20 was released shortly after TeX Live 2024, so you might be lucky here. I didn't check that, though.

[pauloney]

YES!!!! It is 3.19, and it works! Many thanks.

…

On Fri, Aug 23, 2024 at 10:17 AM moewew ***@***.***> wrote: I *think*, biblatex v3.20 was released shortly after TeX Live 2024, so you might be lucky here. I didn't check that, though. — Reply to this email directly, view it on GitHub <#1377 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR7WYVLE5KOQJ563PBLGBTZS5VB7AVCNFSM6AAAAABM65ZG6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBXGQ4TONZUGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[moewew]

Turns out it is not exactly the same issue as #1350 since the problem here is not resolved by the fix for that issue.