Skip to content

Conversation

@nrueh
Copy link
Contributor

@nrueh nrueh commented Apr 15, 2025

No description provided.

@nrueh nrueh requested a review from tortinator April 15, 2025 13:52
Copy link
Contributor

@tortinator tortinator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @nrueh , are you sure? I guess without it LaTeX will throw an error, or ..?

Look (we have a few exceptions...):

torsten@re ~/tex/bibliography (master) > grep doi krr.bib | grep _
  doi = {10.1007/978-3-642-40564-8_3},
  doi = {10.1007/978-3-662-54580-5\_6},
  doi = {10.1007/978-3-031-74209-5\_6},
  doi = {10.1007/978-3-319-67531-2\_6},
  doi = {10.1007/978-3-540-24662-6_13},
  doi = {10.1007/978-3-031-21541-4\_9},
  url = {https://doi.org/10.1007/978-3-031-21541-4\_9}
  doi = {10.1007/978-3-031-74209-5\_2},
  doi = {10.1007/978-3-319-11558-0_12},
  doi = {10.1007/978-3-319-63121-9\_11},
  doi = {10.1007/978-3-031-74209-5\_23},
  doi = {10.1007/978-3-030-20528-7\_12},
  doi = {10.1007/978-3-031-15707-3\_10},
  doi = {10.1007/978-3-030-19570-0\_34},
  doi = {10.1007/978-3-030-20528-7\_19},
  doi = {10.1007/978-94-009-5203-4_4},
  doi = {10.1007/978-3-319-61660-5\_27},
  doi = {10.1007/978-3-319-46520-3\_8},
  doi = {10.1007/978-3-642-18638-7\_6},
  doi = {10.1007/978-3-540-27775-0\_6},
  doi = {10.1007/978-3-319-23264-5\_28},
  doi = {10.1007/978-3-642-20895-9\_37},
  doi = {10.1007/3-540-16492-8\_119},
  doi = {10.1007/978-3-642-20895-9\_41},
  doi = {10.1007/978-3-642-02846-5\_22},
  doi = {10.1007/3-540-60437-5\_10},
  doi = {10.1007/978-3-031-21541-4_4},
  doi = {10.1007/978-3-031-15707-3\_31},
  doi = {10.1007/978-3-319-28228-2\_2},
  doi = {10.1007/3-540-60630-0\_5},
  doi = {10.1007/978-3-642-04238-6_14},
  doi = {10.1007/978-3-319-61033-7\_6},
  doi = {10.1007/978-3-642-41524-1\_20},
  doi = {10.1007/978-3-642-15025-8\_24},
  doi = {10.1007/11867340\_20},
  doi = {10.1007/978-3-031-04580-6_3},
  doi = {10.1007/978-3-642-15297-9\_13},
  doi = {10.1007/3-540-45241-9_12},
  doi = {10.1007/978-3-540-24609-1\_18},
  doi = {10.1007/978-3-540-30227-8\_15},
  doi = {10.1007/978-3-540-89982-2\_46},
  doi = {10.1007/978-3-031-21541-4_2},
  doi = {10.1007/3-540-49481-2\_30},
  doi = {10.1007/3-540-49201-1\_21},
  doi = {10.1007/978-3-031-74209-5\_5},
  doi = {10.1007/978-3-030-69322-0\_16},
  doi = {10.1007/978-3-031-24841-2\_15},
  doi = {10.1007/3-540-60915-6\_6},
  doi = {10.1007/3-540-63104-6\_19},
  doi = {10.1007/978-3-642-36279-8_10},

@nrueh
Copy link
Contributor Author

nrueh commented Apr 16, 2025

Hi @nrueh , are you sure? I guess without it LaTeX will throw an error, or ..?

Look (we have a few exceptions...):

torsten@re ~/tex/bibliography (master) > grep doi krr.bib | grep _
  doi = {10.1007/978-3-642-40564-8_3},
  doi = {10.1007/978-3-662-54580-5\_6},
  doi = {10.1007/978-3-031-74209-5\_6},
  doi = {10.1007/978-3-319-67531-2\_6},
  doi = {10.1007/978-3-540-24662-6_13},
  doi = {10.1007/978-3-031-21541-4\_9},
  url = {https://doi.org/10.1007/978-3-031-21541-4\_9}
  doi = {10.1007/978-3-031-74209-5\_2},
  doi = {10.1007/978-3-319-11558-0_12},
  doi = {10.1007/978-3-319-63121-9\_11},
  doi = {10.1007/978-3-031-74209-5\_23},
  doi = {10.1007/978-3-030-20528-7\_12},
  doi = {10.1007/978-3-031-15707-3\_10},
  doi = {10.1007/978-3-030-19570-0\_34},
  doi = {10.1007/978-3-030-20528-7\_19},
  doi = {10.1007/978-94-009-5203-4_4},
  doi = {10.1007/978-3-319-61660-5\_27},
  doi = {10.1007/978-3-319-46520-3\_8},
  doi = {10.1007/978-3-642-18638-7\_6},
  doi = {10.1007/978-3-540-27775-0\_6},
  doi = {10.1007/978-3-319-23264-5\_28},
  doi = {10.1007/978-3-642-20895-9\_37},
  doi = {10.1007/3-540-16492-8\_119},
  doi = {10.1007/978-3-642-20895-9\_41},
  doi = {10.1007/978-3-642-02846-5\_22},
  doi = {10.1007/3-540-60437-5\_10},
  doi = {10.1007/978-3-031-21541-4_4},
  doi = {10.1007/978-3-031-15707-3\_31},
  doi = {10.1007/978-3-319-28228-2\_2},
  doi = {10.1007/3-540-60630-0\_5},
  doi = {10.1007/978-3-642-04238-6_14},
  doi = {10.1007/978-3-319-61033-7\_6},
  doi = {10.1007/978-3-642-41524-1\_20},
  doi = {10.1007/978-3-642-15025-8\_24},
  doi = {10.1007/11867340\_20},
  doi = {10.1007/978-3-031-04580-6_3},
  doi = {10.1007/978-3-642-15297-9\_13},
  doi = {10.1007/3-540-45241-9_12},
  doi = {10.1007/978-3-540-24609-1\_18},
  doi = {10.1007/978-3-540-30227-8\_15},
  doi = {10.1007/978-3-540-89982-2\_46},
  doi = {10.1007/978-3-031-21541-4_2},
  doi = {10.1007/3-540-49481-2\_30},
  doi = {10.1007/3-540-49201-1\_21},
  doi = {10.1007/978-3-031-74209-5\_5},
  doi = {10.1007/978-3-030-69322-0\_16},
  doi = {10.1007/978-3-031-24841-2\_15},
  doi = {10.1007/3-540-60915-6\_6},
  doi = {10.1007/3-540-63104-6\_19},
  doi = {10.1007/978-3-642-36279-8_10},

Richard asked me to remove the backslash because it appeared in the compiled version.
Without the backslash it compiled without errors.

@nrueh
Copy link
Contributor Author

nrueh commented Apr 16, 2025

If you look at the references of our coom paper the backslash appears in multiple DOIs...
I don't know if this is only with the tlp style or a general thing.

https://arxiv.org/pdf/2504.00013

A. Falkner, A. Ryabokon, G. Schenner, and K. Shchekotykhin. OOASP: connecting object-oriented
and logic programming. In F. Calimeri, G. Ianni, and M. Truszczy´nski, editors, Proceedings of
the Thirteenth International Conference on Logic Programming and Nonmonotonic Reasoning
(LPNMR’15), volume 9345 of Lecture Notes in Artificial Intelligence, pages 332–345. Springer-
Verlag, 2015. doi: 10.1007/978-3-319-23264-5\_28.
S. Hahn, O. Sabuncu, T. Schaub, and T. Stolzmann. clingraph: ASP-based visualization. In
G. Gottlob, D. Inclezan, and M. Maratea, editors, Proceedings of the Sixteenth International
Conference on Logic Programming and Nonmonotonic Reasoning (LPNMR’22), volume 13416
of Lecture Notes in Artificial Intelligence, pages 401–414. Springer-Verlag, 2022. doi: 10.1007/
978-3-031-15707-3\_31.

@tortinator
Copy link
Contributor

Hola @jorgefandinno and @rkaminsk, what is your opinion on it?

@rkaminsk
Copy link
Contributor

Ideally, there should be no backslash for escaping _ in urls. As far as I remember, there are some styles that only work correctly when the underscore is escaped and some that do not work correctly when the underscore is escaped. There might be no perfect solution.

@jorgefandinno
Copy link
Contributor

@nrueh Can you give a link to the repository of the paper? What bst file are you using?

@rkaminsk Do you remember which formats did require backslash?

@nrueh
Copy link
Contributor Author

nrueh commented Apr 17, 2025

@jorgefandinno This is the repo https://github.com/krr-up/coom-paper

It uses the new TLP style (https://github.com/krr-up/latex-class-tlp).
There is a bst file in this repo but we are just using the following (@tortinator ?)

\bibliographystyle{plainnat} % {acmtrans}
\bibliography{./include/bibliography/krr,./local,./include/bibliography/procs}
``

@rkaminsk
Copy link
Contributor

rkaminsk commented Apr 17, 2025

@rkaminsk Do you remember which formats did require backslash?

I think it was the tlp_new.cls style that was causing issues. But then I had so many issues with this broken style.

EDIT: ignore the comment as nico investigated closer.

@jorgefandinno
Copy link
Contributor

@jorgefandinno This is the repo https://github.com/krr-up/coom-paper

It uses the new TLP style (https://github.com/krr-up/latex-class-tlp). There is a bst file in this repo but we are just using the following (@tortinator ?)

\bibliographystyle{plainnat} % {acmtrans}
\bibliography{./include/bibliography/krr,./local,./include/bibliography/procs}
``

Why are you using plainnat instead of tlplike?

@nrueh
Copy link
Contributor Author

nrueh commented Apr 17, 2025

@jorgefandinno This is the repo https://github.com/krr-up/coom-paper
It uses the new TLP style (https://github.com/krr-up/latex-class-tlp). There is a bst file in this repo but we are just using the following (@tortinator ?)

\bibliographystyle{plainnat} % {acmtrans}
\bibliography{./include/bibliography/krr,./local,./include/bibliography/procs}
``

Why are you using plainnat instead of tlplike?

I am not sure, I think @tortinator added the style

@nrueh
Copy link
Contributor Author

nrueh commented Apr 17, 2025

I checked with some other papers of mine:

  • EPTCS works with or without backslash (but removes the backslash in the compiled PDF)
  • CEURART works without backslash (shows backslash in PDF)
  • LLNCS does not work without backslash

@nrueh
Copy link
Contributor Author

nrueh commented Apr 17, 2025

@jorgefandinno This is the repo https://github.com/krr-up/coom-paper
It uses the new TLP style (https://github.com/krr-up/latex-class-tlp). There is a bst file in this repo but we are just using the following (@tortinator ?)

\bibliographystyle{plainnat} % {acmtrans}
\bibliography{./include/bibliography/krr,./local,./include/bibliography/procs}
``

Why are you using plainnat instead of tlplike?

I am not sure, I think @tortinator added the style

Actually I am not able to compile the paper with the tlplike style...but I am not sure why

@jorgefandinno
Copy link
Contributor

jorgefandinno commented Apr 17, 2025

  • LLNCS does not work without backslash

This is strange. I tried, and it works both ways for me, but it shows backslashes. Try to download the last version.
I also tried:

  • AAAI and TPLP, they do not show dois and they do not care
  • ECAI, shows backslashes

@nrueh
Copy link
Contributor Author

nrueh commented Apr 17, 2025

  • LLNCS does not work without backslash

This is strange. I tried, and it works both ways for me, but it shows backslashes. Try to download the last version. I also tried:

Hm, let me check again. The repo is 2-3 years old so maybe the style got updated in the meantime...

@rkaminsk
Copy link
Contributor

Updating styles we commonly use and checking whether they work without backslashes is a good idea. It makes sense that publishers update their styles because dois are used more and more widely.

If it works without backslashes for the major styles we are using, then we can drop the backslash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants