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
I have a question regarding the \setcopyright{cc} option:
My university is now part of ACM Open Program. The documentation mentions, beside the nonacm and acmengage conditions, that \setcopyright{cc} is applicable in these cases:
or for the authors that meet any
of the following requirements: (a)~part of the ACM Open Program;
(b)~publishing in a Gold Open Access publication;
(c)~paying the Open Access APC;
(d)~part of the Google publishing agreement.
However, the cc parameter leads to a warning in the document if neither nonacm nor acmengage is set.
I was wondering whether this is intentional, i.e., the CC copyright is typeset by ACM instead of authors in the four cases mentioned above, or whether the warning needs an update for the four new cases where CC is applicable.
Thank you for your work!
The text was updated successfully, but these errors were encountered:
I just came here to ask exactly the same thing; we're also publishing Creative Commons-licensed papers via ACM Open. I've lately taken to modifying acmart.cls locally to delete the lines that generate the warning, since otherwise the Creative Commons support seems really nice. Can we just remove the warning?
I have a question regarding the
\setcopyright{cc}
option:My university is now part of ACM Open Program. The documentation mentions, beside the
nonacm
andacmengage
conditions, that\setcopyright{cc}
is applicable in these cases:However, the
cc
parameter leads to a warning in the document if neithernonacm
noracmengage
is set.I was wondering whether this is intentional, i.e., the CC copyright is typeset by ACM instead of authors in the four cases mentioned above, or whether the warning needs an update for the four new cases where CC is applicable.
Thank you for your work!
The text was updated successfully, but these errors were encountered: