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

LaTeX doesn't like \tt #257

Closed
richard101696 opened this Issue May 24, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@richard101696

richard101696 commented May 24, 2015

I'm a huge fan of kramdown, but I have a niggle ...

I'm using the Ruby gem for kramdown, 1.7.0. When I use the backtick for URLs, e.g. github.com, this is converted by kramdown to the LaTeX \tt construction, i.e. {\tt github.com}. This construction is deprecated, and I get the message

(scrartcl) You should note, that in 1994 font command \tt' has (scrartcl) been defined for compatiblitiy to Script 2.0 only. (scrartcl) Now, after two decades of LaTeX2e and NFSS2, you (scrartcl) shouldn't use such commands any longer and within (scrartcl) KOMA-Script usage of\tt' is definitely deprecated.
(scrartcl) See fntguide.pdf' for more information about (scrartcl) recommended font commands. (scrartcl) Note also, that KOMA-Script will remove the definition (scrartcl) of\tt' anytime until release of about version 3.20.
(scrartcl) But for now, KOMA-Script will replace deprecated \tt' (scrartcl) by\normalfont \ttfamily ' on input line 453.

Could someone change the gem to use e.g. \texttt instead ?

Best wishes
Richard

@gettalong gettalong self-assigned this May 25, 2015

@gettalong

This comment has been minimized.

Owner

gettalong commented May 25, 2015

Thanks for the issue report! I will change the \tt beforee the next release.

@richard101696

This comment has been minimized.

richard101696 commented Jul 1, 2015

Hello Thomas

Thanks very much for dealing with this so promptly.

Yours
R

✉---------------------
Richard Bland
Schiehallion
Smithy Loan
Dunblane
FK15 0HQ

On 1 Jul 2015, at 07:11, Thomas Leitner notifications@github.com wrote:

Closed #257.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment