From: Karl Weber <karl.weber99-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: syntax-definition no longer working after release upgrade
Date: Sun, 14 May 2023 04:40:16 -0700 (PDT) [thread overview]
Message-ID: <cfe8c5b3-6f89-4735-8945-e47217bf0ba4n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1466 bytes --]
Hi,
yesterday I upgraded from release 2.11.3.2 to 3.1.2 and ran into some
incompatibilities. I could fix those related to lua scripts, but I am stuck
with my syntax definition. (Both releases are the binary distributions
from
the pandoc website.)
I have my own KDE-style XML syntax definition file named asshell.xml. In my
global.yaml file it is specifies as
syntax-definition: ../../../asshell.xml
This relative path is correct. OS is opensuse. I use this syntax definition
as
~~~~~~{.asshell}
blabla
~~~~~~
The file asshell.xml starts with
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE language SYSTEM "language.dtd">
<language name="asshell" version="1" kateversion="2.3" section="Sources"
extensions="*.asshell" priority="5" author="KW" license="GPL">
This worked perfectly with releases up to and including 2.11.3.2, but with
3.1.2 I get the error message
[WARNING] Could not highlight code block:
Unknown syntax or context: ("asshell","Parameters")
Could you please give me some help?
Thanks in advance!
Kind regards
Karl
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/cfe8c5b3-6f89-4735-8945-e47217bf0ba4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1950 bytes --]
next reply other threads:[~2023-05-14 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 11:40 Karl Weber [this message]
[not found] ` <cfe8c5b3-6f89-4735-8945-e47217bf0ba4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-14 16:43 ` John MacFarlane
[not found] ` <2D35C81B-C8B2-49DB-A898-CC5F35C4D72A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-14 19:46 ` Karl Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfe8c5b3-6f89-4735-8945-e47217bf0ba4n@googlegroups.com \
--to=karl.weber99-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).