Git Product home page Git Product logo

acl-style-files's People

Contributors

bethard avatar danielgildea avatar davidweichiang avatar jkkummerfeld avatar kato8966 avatar lsinev avatar mjpost avatar rrgerber avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

acl-style-files's Issues

Bump TeXLive version on Overleaf to 2023

This doesn't belong here, I know, but I noticed that the Overleaf template uses TeXLive 2022, whereas arXiv has (finally) updated to 2023. I think it will save people trouble if we switch to 2023 also.

anthology.bib exceeds the file size limit for overleaf

Hey folks,

Been trying to add the anthology.bib to overleaf through git, upload, and overleaf grabbing it, and it all errors out with that the file is too large - the file size limit seems to be 50 MB. Copying it from the overleaf template doesn't allow refreshing the document.

Not entirely sure what a solution here is but it might be worth reaching out to the overleaf people about it.

Limitation section

Is a limitation section now required? If so, a template without it is misleading

Proposal: Pandoc (Dynamic) LaTex Template for ACL Papers

Hi all,

I wonder if there's a plan to develop a Pandoc LaTex template for ACL papers. Something like this:

pandoc -s --template="acl.latex"\
--citeproc --csl "acl.csl"\
-f markdown\
-t pdf --pdf-engine="xelatex"\
"input.md" -o "output.pdf";

I think this way, i.e. using a dynamic template could be more efficient and effective than using a static one. One can produce the paper based on any format, such as markdown, latex, odt, or docx.

Have to move files before being able to use pdflatex

If a new "user" clones the repo and wants to get started with pdflatex and the acl_latex.tex file it can be a bit confusing. The acl_natbib.bst has to be moved to the root of the repo, or the acl_latex.tex + custom.bib into the latex folder for it to run pdflatex/bibtex successfully. Confusion could be avoided if these are moved in the repo already. Not sure what the preferred location is, I guess everything that is latex in the latex folder?, except if its desirable to prioritize the latex ones, then it might make sense to move the contents of the latex folder to the root.

Making Unicode supported LaTeX template as the default

We have been using PdfLatex compiler/engine as the default, but as we know it isn't Unicode (non-Latin) friendly.
Though the instructions suggest using XeLaTeX, the generated PDF looks different in many ways than PdfLatex's.
For example (left: PdfLatex, right: XeLatex): Look at the nuances in fonts, section headings aren't as bold as PdfTex's in the left. I believe the font weight isn't exactly the same.

Screen Shot 2022-01-04 at 2 55 02 PM

My request/suggestion:
Move towards Unicode supported template as a way of encouraging NLP in non-Latin languages.
Researchers working on non-Latin languages should also be able to paste qualitative examples (without some non-vector images), right? So, how about making Unicode supported template (i.e XeLatex) as the default?

If any one interested in testing unicode support of latex templates, here is a file having UDHR titles in hundreds of languages:
udhr-title.txt

Thanks,

Bad length values lead to ugly misalignment between the columns

I would like to report a quite aesthetically serious issue.

It appears that some length values of the package have not been correctly set, causing ugly misalignment between the two columns. Please see my question on TeX StackExchange for an example of output.

Let me quote a comment from an expert there:

the package does not make \textheight-\topskip a multiple of \baselineskip so every column of just text can not be set without underful box warnings, spaces around section headings are not given enough stretch to compensat a full baselineskip and so on

I have no idea how to fix this but I hope the developer can figure it out.

Best regards.

The style file in .zip file is not same as the file in overleaf or latex subdirectory

In .zip file, it contains the following:
\iffalse \PassOptionsToPackage{ a4paper, top=2.21573cm,left=2.54cm, textheight=24.7cm,textwidth=16.0cm, headheight=0.17573cm,headsep=0cm }{geometry} \fi \PassOptionsToPackage{a4paper,margin=2.5cm}{geometry} \RequirePackage{geometry} \setlength\columnsep{0.6cm} \newlength\titlebox

In overleaf or latex subdirectory, it contains the following:
\iffalse \PassOptionsToPackage{ a4paper, top=2.21573cm,left=2.54cm, textheight=704.60031pt, % 51 * \baselineskip + \topskip textwidth=16.0cm, headheight=0.17573cm,headsep=0cm }{geometry} \fi \PassOptionsToPackage{a4paper,margin=2.5cm,heightrounded=true}{geometry} \RequirePackage{geometry} \setlength\columnsep{0.6cm} \newlength\titlebox \setlength\titlebox{11\baselineskip} % \titlebox should be a multiple of \baselineskip so that

preprint option

I think it would be nice to have a preprint option that is like final except has page numbers.

Expose `if final copy` switch to the user

In some cases, some information in the text should be redacted in the review copy but present in the final copy. It would be nice to have to have a switch you could use in the LaTeX source so you could write both variants without worrying that you will forget to change the redacted text for the camera-ready version. Something like:

The authors asked colleagues from \iffinal{AFFILIATION}{[redacted for review copy]} for review of the results.

It is relevant information in the context of the publication that a human review was done by colleagues of the authors, but revealing the affiliation would compromise the anonymity of the submission.

arXiv.org citations missing info

Expected output:
The ACL formatting requirements give the following example for how to cite an eprint on arXiv:

Mohammad Sadegh Rasooli and Joel R. Tetreault. 2015. Yara parser: A fast and accurate dependency parser. Computing Research Repository, arXiv:1503.06733. Version 2.

Actual output:

The latex template provided in this repo (using the bibtex citation that arXiv provides) gives the following:

Mohammad Sadegh Rasooli and Joel R. Tetreault. 2015. Yara parser: A fast and accurate dependency parser.

It omits the eprint prefix and eprint code.

This seems not good, since the resulting reference has no mention of where the citation is from (without following the hyperlink).


Details:

If one copies the autogenerated bibtex citation from the "Export Bibtex Citation" link on arXiv, one gets the following:

@misc{arxiv.1503.06733,
  doi = {10.48550/ARXIV.1503.06733},
  url = {https://arxiv.org/abs/1503.06733},
  author = {Rasooli, Mohammad Sadegh and Tetreault, Joel},
  title = {Yara Parser: A Fast and Accurate Dependency Parser},
  publisher = {arXiv},
  year = {2015}
}

I notice the bibliography style file acl_natbib.bst has specific code to deal with arXiv references:

"http://arxiv.org/abs/" 'eprinturl := % prefix to make URL from eprint ref
"arXiv:" 'eprintprefix := % text prefix printed before eprint ref; typically "arXiv:"

but, for some reason (I can't grok .bst files well enough to understand why) the output doesn't comply with the recommended format from the formatting requirements. Instead, using the provided latex template and bst file, the resulting PDF output just has the name, date, and hyperlinked title.

Adding a note field to the bibtex entry, like

note = {Computing Research Repository, {arXiv}:1503.06733. Version 2},

would make the output like the recommended, but it seems like the style sheet should do something like this (at least it should include the {arXiv}:1503.06733 part in the output, I think). Is there a reason why the bst style sheet doesn't do something like this by default?

Inconsistency in Arxiv compilation

Not exactly sure about the technical details. We encountered issues with fonts that caused previously unseen overflow when submitting to Arxiv. Maybe it was with caption and abstract fonts. Tax version on overleaf was 2021. I believe this is the version Arxiv runs as well.

Sync with Overleaf

Who maintains the Overleaf version and can keep it in sync with this version? @neubig @bethard @mjpost

The recent changes are not critical, but it would be good to know who to contact when there is a critical change.

Cannot add svg images due to no inkscape

Hello, I would like to insert an SVG image using the following code

\begin{figure}[t]
    \centering
    \includesvg[width=\columnwidth]{figs/prelim.svg}
    \caption{ABC}
    \label{fig:1}
\end{figure}

But the log shows error as following

See the svg package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.257 ...esvg[width=\columnwidth]{figs/prelim.svg}
                                                  
Did you run the export with Inkscape? There's no file
`./svg-inkscape/prelim_svg-tex.pdf'
although `figs/prelim.svg' was found.

It seems that this is because inkscape is not installed. How can I fix this please ? I am using overleaf and not on local tex.

Word equations

  • No mention of Equation formatting (Sec. 3.10 in Word doc).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.