Closed kfnks closed 5 months ago
@kfnks Thank you for submitting the request. Please submit the conference ingestion material two weeks prior to the desired publication date.
This looks great, thanks!
@mjpost @anthology-assist Thank you!
@mjpost @anthology-assist I am experiencing an error with a particular paper pdf (372_Paper.pdf) and cannot compile book.pdf. To my memory, it was working before but at a some time point it started causing the error. As far as I see, the paper pdf has no problem when I open it with macOS preview.app. If I remove the paper 372 from the order file, I can compile book.pdf properly. Do you have any workaround with this issue?
$ make shipout
quietly running pdflatex book.tex ...
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=pdflatex)
\write18 enabled.
entering extended mode
Syntax Error: Couldn't read xref table
Syntax Warning: PDF file is damaged - attempting to reconstruct xref table...
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't read xref table
pdflatex failed on book.tex; see book.log for details
make[1]: *** [book.idx] Error 1
make[1]: *** Deleting file `book.idx'
make: *** [shipout] Error 2
$ tail book.log
(pdftex.def) Requested size: 597.50682pt x 845.04504pt.
File: final/368/368_Paper.pdf Graphic file (type pdf)
<use final/368/368_Paper.pdf, page 9>
Package pdftex.def Info: final/368/368_Paper.pdf , page9 used on input line 144
.
(pdftex.def) Requested size: 597.50682pt x 845.04504pt.
[174 <./final/368/368_Paper.pdf>]
!pdfTeX error: pdflatex (file ./final/372/372_Paper.pdf): xpdf: reading PDF ima
ge failed
==> Fatal error occurred, no output PDF file produced!
Sorry, I have no insights into this process. Are you using aclpub2? You might file an issue there: https://github.com/rycolab/aclpub2/issues
@mjpost Thank you for your reply. I am using the proceedings/Makefile in the zip file generated by START with the environment variable ACLPUB=../ . I believe I'm using aclpub, not aclpub2.
I could bypass the error by exporting another PDF file from the problematic PDF file.
Hi @kfnks and @mjpost , appreciate your work on this! Do you know if there's any recent update regarding AACL ingestion?
I believe we are waiting for the material from @kfnks.
@mjpost @flipz357 Sorry for leaving you suspended. Currently another pub chair is handling data finalization. Please wait for a while.
Any updates?
We are still handling copyright transfer issues. Sorry for this trouble.
@mjpost @flipz357 We have decided to send only the data of copyright-confirmed volumes. Please download the zip file from here.
It lacks the data of ijcnlp-aacl demo, eval4nlp, sealp, and socialnlp. The data of those volumes will be shared later.
Thank you for your help. We wish your nice holidays.
@kfnks Existing volumes have been ingested: https://github.com/acl-org/acl-anthology/pull/3003
Please let me know once the missing volumes are uploaded.
@anthology-assist Thank you for your help. Please ingest the data of copyright-confirmed demo volume (2023.ijcnlp.demo), too.
Also, in accordance with the description in the anthology, we also share the data of the remaining three workshops., although their copyright transfers have not been obtained yet.
For both current and legacy events, it is good practice for the organizers to attempt to obtain copyright transfers for their materials, but we will ingest materials even if no copyright transfers are on file.
Thank you again for your patience.
@anthology-assist Please find the attached files of confirmed copyright transfer signatures for SEALP and SocialNLP. copyright-signatures_sealp.txt copyright-signatures_socialnlp.txt
@anthology-assist Here is the last agreement signatures file for Eval4NLP. copyright-signatures_eval4nlp.txt
@anthology-assist @mjpost Thank you for your kind help. If there is any action that I am expected to take, please let me know.
@kfnks All volumes and workshops have been ingested except for workshop eval4nlp, please look at the preview in #3003 and let me know if anything's wrong.
eval4nlp ingestion material doesn't follow aclpub2 format, specifically the papers.yaml
file. Requirements see https://github.com/rycolab/aclpub2 . Could you update the file?
@anthology-assist Thank you for the preview. Unfortunately, we have found that there was an error in the message from the general chair. Could you please replace the relevant PDF files with those in this zip file ? The others look great.
As for eval4nlp, we are waiting for the feedback from the workshop organizers. Many thanks.
@mjpost Imo this issue is not yet fully solved. Eval4NLP 2023 has not yet been integrated. We collected copyright from the attendents as request about a month ago and sent them to the responsible person at AACL. I think what was left do was some bug about the proceedings compilation that is probably now fixed too.
Linking @danieldeutsch here, since he may know more about this.
The papers.yml
file that was generated by aclpub2 did not match the format specified in the aclpub2 repository, even though I successfully used it to compile the Eval4NLP proceedings. Lun-Wei from AACL asked me to update the papers.yml
and I did my best to change it to match the format in the repository. I sent Lun-Wei the updated proceedings and papers.yml
file on January 21 but did not hear back.
Hi @anthology-assist,
I noticed that the page for the FinNLP workshop (https://aclanthology.org/volumes/2023.finnlp-1/) was mixed with the other workshop. Some papers in FinNLP were removed, and some papers from the other workshop were listed on the page.
Additionally, the page of the Fifth FinNLP disappeared. It was done this Oct. (https://github.com/acl-org/acl-anthology/issues/2460).
Please let me know if I need to prepare documents for solving this issue.
Thanks, I reverted this in #3072.
It appears that FinNLP met twice in 2023: once with IJCAI (non-Anthology), and once with IJCNLP-AACL.
@anthology-assist can you please re-ingest FinNLP, as a second volume, with volume ID "2"? Then re-link it to IJCNLP.
@anthology-assist Here is the updated papers.yml from @danieldeutsch . Does this work? https://www.dropbox.com/scl/fi/wu74zqzgdp34p0ifreznd/papers.yml?rlkey=uqtttxtbnuzrl4tl1jlwfqjs1&dl=0
As for FinNLP, our first delivery data on Dec. 23 wrongly duplicated .bib and .pdf from ArfOfSafety in finnlp/proceedings/cdrom/{bib,pdf}. Sorry for this trouble.
@anthology-assist is there any update on the Eval4NLP@AACL ingestion, or can we somehow provide more information?
This is closed, so let's create a new issue for Eval4NLP? That will help it avoid getting lost.
General information about this request
Venue Identifier
ijcnlp, aacl
Volume Title
Proceedings of the 13th International Joint Conference on Natural Language Processing and the 3rd Conference of the Asia-Pacific Chapter of the Association for Computational Linguistics
Venue Name (only if you are submitting a new venue)
No response
Venue Website (only if you are submitting a new venue)
No response
Date of Publication
2023-11-1
Supporting Information
This event will include following volumes ({volume identifier}; {volume name}) .
2788, #2789 and #2790 are new venue submissions.
If I should make a separated issue for each volume, please let me know.
Thank you for your help!