-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Unexcepted escape seq in typst template. #9823
Comments
I also have this problem with my email addresses, not sure what is correct in terms of escaping from the yaml to the email field, but I think before the @ was just passed through without problems (at least I previously used Typst and didn't see this but now I do)... |
Might related to this commit: |
I'm not sure that commit is responsible, if I edit my custom template to use the [$author.email$] or "$author.email$" syntax both get the @ escaped. My internet is very flakey for searching commits, but there were a few recent changes to escape more typst content. |
The field is parsed as Markdown, so it turns into Some possible solutions:
(will format as a linked email address)
(will format as verbatim text)
(will just be a plain string without escapes). |
In any case: not a bug. |
Thanks @jgm. If I use the link syntax, the link text is still escaped:
...and currently the backticked verbatim / raw inline is causing yaml parse errors: |
OK, ` is reserved[1] (didn't it used to work before?), but YAML block literal syntax doesn't cause any YAML errors: author:
- name: XXX
email: |
`XXX@xxx.com` ... although the typst output gets some extra newlines these don't affect the PDF I think: authors: (
( name: "XXX",
affiliation: "",
email: "`XXX@xxx.com`
" ), |
Yeah, the link idea was not good. And the other idea requires using block syntax or maybe single quotes. |
Perhaps we can adjust the escaping so that word-internal @ isn't escaped. I think that would be safe. |
No such luck.
in typst.app raises an error because the label |
Maybe the solution is to use |
Explain the problem.
I have a 1.md like this:
Then I run:
I got 1.typ as:
The problem is that
email: "XXX\@xxx.com"
, which make the pdf output of 1.typ looks like this:Note:
pandoc/src/Text/Pandoc/Writers/Typst.hs
Line 467 in c19b44b
I think we maybe need a new context type like this:
pandoc/src/Text/Pandoc/Writers/Typst.hs
Line 476 in c19b44b
Pandoc version?
The text was updated successfully, but these errors were encountered: