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
TCC 2024 proceedings are published in November (example: Part II) and December (example: Part I). In current crypto.bib, all of them are listed as in December. The conference itself is fully inside December, but #3 suggests that the date should be the publication date. The suggested change is to use nov # "~/~" # dec, as is the usual case for multi-month publications (e.g., TCC 2023).
The text was updated successfully, but these errors were encountered:
I think cryptobib uses the month field for all conferences as the exact dates for the conference (e.g. dec # "~2--6," for TCC), not the dates when the proceedings where published. In the abbreviated version this just appears as "dec". TCC 2023 was held nov # "~29~--~" # dec # "~2,", and thus appears in the abbreviated version as nov # "~/~" # dec.
TCC 2024 proceedings are published in November (example: Part II) and December (example: Part I). In current
crypto.bib
, all of them are listed as in December. The conference itself is fully inside December, but #3 suggests that the date should be the publication date. The suggested change is to usenov # "~/~" # dec
, as is the usual case for multi-month publications (e.g., TCC 2023).The text was updated successfully, but these errors were encountered: