-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cite
encodes dash -
strangely in URLs
#5648
Comments
I agree that the current thing doesn't seem necessary -- was it required in some much older versions of tex? I put |
Cite
encodes dash -
strangely in URLs.Cite
encodes dash -
strangely in URLs
Actually it turns out the weird But now GAPDoc 1.6.7 is released, but has not been picked up by the GAP package distro precisely because it breaks the @frankluebeck is this an intentional change? |
The change is due to a bug fix in GAPDoc in this commit. The Of course, you are free to change that generated Bib entry as you like when you copy it into one of your files. |
PS: Just noticed: The output does not look as it should. The
or, as it is easier to implement:
|
The use of
I also wonder why it doesn't just use As it is, I always edit the |
I find the
howpublished
entries in the bibtex produced byCite
on master weird:Why does it "encode" the
-
in the URL as\symbol{45}
?Beyond that, why does it do
with a nested
\texttt
, instead of justActually, taking a step back, I also wonder about the
discretionary
...Here is what my ideal output for
howpublished
would look like:Any objections to that?
Of course right now a lot of this comes down to us calling GAPDoc, and that then does whatever it considers best. But I don't understand why we do it that way -- why not just generate the appropriate BibTeX (etc.) ourselves? Then we have full control over how it looks.
The text was updated successfully, but these errors were encountered: