From: "Christoph Hintermüller" <christoph@out-world.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: What does the exporter try to tell me.
Date: Mon, 18 May 2020 05:46:54 +0200 [thread overview]
Message-ID: <a573ad8a37211771e0eb0e456392f0920ebec339.camel@out-world.com> (raw)
In-Reply-To: <63f03ebaad629ca9eb396023b8ebb144031533cc.camel@out-world.com>
Hi
[Inline Response to message by Christoph Hintermüller, So, 2020-05-17
18:32 +0200: Answers and comments below corresponding cited
paragraphs.]
> Hi
> I'm trying to improove the T-vim module such that it is also working
> properly in xml export setup.
>
> In the current ConTeXt standalone the exporter tries to tell me
> something when reporting "possible paragraph mixup" at any character
> followoing the first paragraph. And no output from the code block
> between start<>stop. I got that far that it has to do something with
> the redefinitoin of end of line chars or alike in the code behind and
> between the package specific start<> and stop<> commands. But i do
> not
> catch what the exporter trying to yell at me.
>
> So what additoinal trackers exempt the ones registered by the
> exporter
> do i have to activate to see what the exporter has to process on?
> What documentation should i read before continueing?
> What hast to be done inside the start stop, `\obeyline` etc macros to
> ensure the exporter is provided with a proper document
> sturcuture/tree
> which can be properly and flawlessly processed.
>
> All tex commands which should be reflected in the xml output by tags
> include inside their code `\starttagged` and `\stoptagged` commands
> but
> my impression is that something important the exporter needs to have
> any chance to gnereate porper clean output is missing and I'm missign
> any clue what and where to startoff.
>
Sorry. What i forgot. For developing the improovements of the t-vim
module i use a fresh pulled standalone lastest
mtx-context | ConTeXt Process Management 1.03
mtx-context |
mtx-context | main context file:
/home/nother/bin/context/tex/texmf-
context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.05.12 16:17
mtx-context | main context file:
/home/nother/bin/context/tex/texmf-
context/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.05.12 16:17
and in case relevant at all:
This is LuaTeX, Version 1.11.2 (TeX Live 2020/dev)
Execute 'luatex --credits' for credits and version details.
There is NO warranty. Redistribution of this software is covered by
the terms of the GNU General Public License, version 2 or (at your
option)
any later version. For more information about these matters, see the
file
named COPYING and the LuaTeX source.
LuaTeX is Copyright 2019 Taco Hoekwater and the LuaTeX Team.
a not so fresh version of my changes can be found on
https://github.com/hernot/filter/tree/complete-tagging
The line 336 of t-syntax-groups.vim file has to be commented to work
with latest context version mentioned above. It was a hack for an older
version (2018 release). I do not want to commit the chaos found on my
local working tree cause i do not consider it more confusing for others
than helpful.
Best
Xristoph (hernot)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-05-18 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 16:32 Christoph Hintermüller
2020-05-18 3:46 ` Christoph Hintermüller [this message]
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=a573ad8a37211771e0eb0e456392f0920ebec339.camel@out-world.com \
--to=christoph@out-world.com \
--cc=ntg-context@ntg.nl \
/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).