Skip to content
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

error producing pdf #3

Closed
VP59m opened this issue Jan 21, 2019 · 2 comments
Closed

error producing pdf #3

VP59m opened this issue Jan 21, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@VP59m
Copy link

VP59m commented Jan 21, 2019

Hi all! I followed step by step the amazing wiki but shell returns this error
Error producing PDF. ! Missing \endcsname inserted. <to be read again> \TU\textasciitilde l.86 \usetikzlibrary{\textasciitilde{}}
Any ideas?
cheers Igor

periodicpoint added a commit that referenced this issue Jan 21, 2019
Fix bug #3 by removing every tilde from the metadata and settings (YAML) files.

Cause
The error is caused by the ASCII tilde symbol  “~” in the settings or metadata files.

Fix
Remove every occurrence of “~” in the settings and metadata files.

Explanation
In the general  YAML treats tildes as NULL.
The error message: „Error producing PDF. ! Missing \endcsname inserted. <to be read again> \TU\textasciitilde l.86 \usetikzlibrary{\textasciitilde{}}“ is caused by the existence of the tilde symbol „~“ in the metadata or settings (YAML) file, because pandoc translates occurrences of “~” into “\textasciitilde{}”. The LaTeX compiler (XeTeX) do not like “\textasciitilde{}” inside of “\usepackage{}” or “\usetikzlibrary{}”.

Thanks to @VP59m how reported this bug.
periodicpoint added a commit that referenced this issue Jan 21, 2019
Fix bug #3 by removing every tilde from the metadata and settings (YAML) files.

Cause
The error is caused by the ASCII tilde symbol  “~” in the settings or metadata files. Here most likely at line 269 at “usetikzlibrary:“.

Fix
Remove every occurrence of “~” in the settings and metadata files.

Explanation
In the general  YAML treats tildes as NULL.
The error message: „Error producing PDF. ! Missing \endcsname inserted. <to be read again> \TU\textasciitilde l.86 \usetikzlibrary{\textasciitilde{}}“ is caused by the existence of the tilde symbol „~“ in the metadata or settings (YAML) file, because pandoc translates occurrences of “~” into “\textasciitilde{}”. The LaTeX compiler (XeTeX) do not like “\textasciitilde{}” inside of “\usepackage{}” or “\usetikzlibrary{}”.

Thanks to @VP59m how reported this bug.
@periodicpoint
Copy link
Owner

periodicpoint commented Jan 21, 2019

Hi @VP59m,

thank you for reporting this bug.

BLUF

  1. I fixed the bug you can update now and try again.
  2. Your error is most likely caused by the tilde symbol “~” in file 00_00_settings.yaml at line 269 at “usetusetikzlibrary:”. Removing the tilde should fix your error.

TL;DR

Cause

The error is caused by the ASCII tilde symbol “~” in the settings or metadata files. Here most likely at line 269 at “usetikzlibrary:“.

Explanation

In the general YAML treats tildes as NULL.
The error message: „Error producing PDF. ! Missing \endcsname inserted. \TU\textasciitilde l.86 \usetikzlibrary{\textasciitilde{}}“ is caused by the existence of the tilde symbol in the metadata or settings (YAML) file, because pandoc translates occurrences tildes of into “\textasciitilde{}”. The LaTeX compiler (XeTeX) do not like “\textasciitilde{}” inside of “\usepackage{}” or “\usetikzlibrary{}”.

Fix

Remove every occurrence of “~” in the settings and metadata files.

I hope it helps.

Cheers,
Martin

PS: Please note that I regard arabica not stable at the moment. I'll probably completely redesign arabica in the near future. I plan to simplify the entire thing, but this may be breaking changes. …

periodicpoint added a commit that referenced this issue Jan 21, 2019
Fix bug #3 in file 00_00_settings.yaml
periodicpoint added a commit that referenced this issue Jan 21, 2019
Fix bug #3 in file 00_00_metadata.yaml
@VP59m
Copy link
Author

VP59m commented Jan 21, 2019

thank you so much :)

@periodicpoint periodicpoint added the bug Something isn't working label Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants