[NTG-context] process markdown file
Hi all,
I have updated to the latest version and it seems that the MarkDown
module is no longer part of the context installation. I get an
'undefined control sequence' error for \processmarkdownfile and the
module files are gone. Is this on purpose? Why has it been removed?
Can this please be restored?
MWE
\usemodule[markdown]
\starttext
\processmarkdownfile{file.md}
\stoptext
Manual solution: I have found the files 'm-markdown.lua' and
'm-markdown.mkiv' but I am not sure where/how to install them?
Thanks,
Jelle
___
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
___
Re: [NTG-context] Initial release of SBL bibliographic rendering and biblio wishlist
Hello Joey,
Just a quick note to thank you for your work on this. I use Chicago
which is close enough to SBL that I can use it. I'll test it for a
while and report any issues I encounter.
Jelle
On Thu, Dec 9, 2021 at 12:47 AM Joey McCollum via ntg-context
wrote:
>
> A while ago, I mentioned in a thread on the mailing list that I was working
> on a new bibliographic rendering for the SBL citation style. After additional
> testing and implementation of various features (e.g., an authorconversion
> that inverts the first author and prints all subsequent authors in normal
> order, an author-title sort order for bibliographic entries, support for
> shorthands/abbreviations, support for Citation Style Language locators, and
> support for biblatex-style citation macros that intelligently move
> punctuation that follows them). While optimizations for performance,
> simplifications of the code, and new feature additions are still desirable,
> the module is in working condition and can now be incorporated in a future
> ConTeXt update. The new .lua and .mkvi files for the SBL rendering, updated
> publ-aut.lua and publ-imp-author.mkvi files, and some new code intended to be
> incorporated into publ-ini.lua and publ-ini.mkiv can all be found in project
> GitHub repo at the https://github.com/jjmccollum/context-sbl.
>
> While I worked on this module, Denis Maier (who provided valuable feedback
> and suggestions throughout) and I put together a wish list of new features we
> would like to see implemented in the publications support core modules. We
> put together the list with Hans and Alan in mind, but any help is
> appreciated! The list follows:
>
> Probably the most urgent need is for field inheritance mappings through
> crossrefs to be fixed. These should be customizable in bibliographic
> specification .lua files (e.g., publ-imp-sbl.lua), or at the very least, they
> should follow the pattern of biblatex. As it is currently implemented, field
> inheritance seems to map any field from the cross-referenced entry to a field
> of the same name in the current entry if it doesn't have a field of this name
> already. But this causes serious problems when one needs to check if an entry
> has a given field (such as "shorthand") at all; specifically, the \btxdoif
> macro will execute its argument if the current entry or any entry it
> cross-references contains a field with that name. What we want is a more
> disambiguated mapping of inherited fields: for many common entry types (such
> as @book, @collection, @reference, @proceedings, and @inbook, @incollection,
> @inreference, and @inproceedings), biblatex maps the title field of the
> cross-referenced entry to a different-named field in the lower-level entry
> (e.g., maintitle -> booktitle -> title, maineditor -> bookeditor -> editor,
> etc.).
> A mechanism for setting default field values (e.g., "pagination", "options")
> by category in the .lua file for a given specification. (In the SBL spec, for
> instance, an entry of category @ancienttext or @classictext should have
> options={skipbib=true} by default.) If the user actually specifies this field
> in an entry, then the default value would be overwritten.
> If it hasn't been done already, the \btxdoifelsecitedone macro defined in the
> cont-new.mkiv file in https://github.com/jjmccollum/context-sbl should be
> implemented in publ-ini.lua and publ-ini.mkiv.
> Related to the previous entry, the ability to remove existing entry tags from
> the "collected" or "tobesaved" lists defined in publ-ini.lua. This would
> allow us to override the usual list registry rules of \cite based on the
> values of, say, an entry's category, "type" field or "options" field.
> General support for the useauthor, useeditor, usetranslator, skipbib, and
> skipbiblist entry options from biblatex. These could be implemented as
> citation-level btx options (currently, useauthor already is implemented for
> the SBL style).
> Support for disambiguation in "author" citations made with the "name"
> authorconversion. Publications support already allows us to map different
> versions of the same name (e.g., "John Doe" and "J. Doe" to a single value.
> But ideally, the publications support module should also check if surnames
> are shared by distinct authors, and if so, it should then check for distinct
> first and middle initials, and then distinct full names, until it finds a
> difference. The shortest distinct renderings should then be used for the
> "name" authorconversion. Different bibliographic renderings have different
> rules for this, so implementations of these different rules (detailed at
> https://docs.citationstyles.org/en/stable/specification.html#disambiguation)
> would be ideal.
> General support for ibidem (same entry), idem (same author), and op. cit.
> (same title) tracking in the publ-ini module. These could be implemented with
> default settings that could be overridden as
Re: [NTG-context] Different authorconversion for citation alternatives and bibliographic entries
Chicago-style footnote user here,
I would be interested in helping with testing.
Jelle
On Wed, Jun 30, 2021 at 11:50 PM Alan Braslau wrote:
>
> On Wed, 30 Jun 2021 19:40:06 +
> wrote:
>
> > > -Ursprüngliche Nachricht-
> > > Von: Alan Braslau
> > > Gesendet: Mittwoch, 30. Juni 2021 21:11
> > > An: mailing list for ConTeXt users ; Maier,
> > > Denis Christian (UB)
> > > Betreff: Re: [NTG-context] Different authorconversion for citation
> > > alternatives and bibliographic entries
> > >
> > > On 30/06/21 12:59, denis.ma...@unibe.ch wrote:
> > > > Hi,
> > > >
> > > >> -Ursprüngliche Nachricht-
> > > >> Von: ntg-context Im Auftrag von
> > > >> Ágoston Volcz
> > > >> Gesendet: Mittwoch, 30. Juni 2021 10:20 An:ntg-context@ntg.nl
> > > >> Betreff: [NTG-context] Different authorconversion for citation
> > > >> alternatives and bibliographic entries
> > > >>
> > > >> Hi there,
> > > >>
> > > >> My university has special requirements for the theses I submit.
> > > >> Layout, fonts etc. are pretty straightforward to set up in
> > > >> ConTeXt. The one part I'm struggling with is citations /
> > > >> bibliography. I have to use the german citation style with
> > > >> footnotes. Essentially the first time I cite something, I have
> > > >> to put the full entry in a footnote. From the second time on, I
> > > >> only have to put a shorter entry in the
> > > footnotes.
> > > > Is this first citation vs other citations thing currently
> > > > possible with ConTeXt? I
> > > was thinking that there was no proper support for note style
> > > citations in ConTeXt? Has that changed? I remember reading the
> > > phrase "We may add additional citation styles if there demand and
> > > clear requirements exist." So what's the current state of affairs
> > > here?
> > > >
> > > > Denis
> > >
> > > Indeed (one can always use \footnote{} but that might not be a good
> > > substitute for a proper footnote citation style.
> > >
> > > I do not use footnote citations as a general style (and personally
> > > dislike it, finding them somewhat distracting and sloppy). Yet
> > > these are popular in many fields and there is no reason not to
> > > support it.
> >
> > So what would be needed to make add real support for it?
>
> First of all, come to a consensus on a clear style guide to base this
> on, so as not to run after ambiguous and perhaps contradictory
> specifications. This would be distinct from the APA (author-year) model
> as well as from the minimalist APS (numbered) style. Could this perhaps
> be the Chicago style? (does that have a footnote specification?)
>
> Secondly, identify users who would be willing to spend time testing and
> giving feedback.
>
> Thirdly, motivate Hans and myself to spend time on this (implementing
> or helping implement), for neither of us use the footnote style.
>
> So it can be done, and such a model is presently missing.
>
> Alan
>
> ___
> 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
> ___
___
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
___
Re: [NTG-context] Markdown module in LMTX
Hi all,
I can confirm that this problem has not yet been resolved? Any idea
when it might happen?
Cheers,
Jelle
On Mon, Jan 11, 2021 at 5:48 AM Christoph Reller
wrote:
>
> Hi,
>
> In recent versions of ConTeXt LMTX, the builtin markdown module is missing.
> (Files m-markdown.[lua|mkiv])
> Just copying this module from an earlier version shows that they don't work
> anymore.
>
> MWE:
>
> ConTeXt file:
> -- 8< --
> \usemodule[markdown]
> \starttext
> \processmarkdownfile{file.md}
> \stoptext
> -- 8< --
>
> file.md:
> -- 8< --
> Title
> =
>
> Here comes a paragraph text.
> -- 8< --
>
> Are there plans to add and update this module?
>
> Cheers,
> Christoph
> ___
> 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
> ___
___
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
___
Re: [NTG-context] how to set the name of outputfile using a value defined in the source
Thank you, Taco, that is exactly what I need!
Jelle
On Fri, Sep 21, 2018 at 10:44 AM Taco Hoekwater wrote:
>
>
>
> > On 21 Sep 2018, at 10:30, Henri Menke wrote:
> >
> > On 21/09/18 20:09, J Huisman wrote:
> >> Hi all,
> >>
> >> I'm getting back to using ConTeXt after a couple of years, so I might
> >> be missing something obvious...
> >>
> >> I would like to add an I.D. code to the name of my outputfile, but
> >> since this will be used in an automated environment I would like to
> >> load the ID-code from the source file.
> >>
> >> MWE: test.tex
> >>
> >> \starttext
> >>
> >> \def\idcode{something}
> >>
> >> Some text, whatever.
> >>
> >> \stoptext
> >>
> >> If I typeset with: context text --result=test-idcode the result is
> >> obviously "test-idcode.pdf", but I want to get a file name:
> >> "test-something.pdf"
> >> Is this possible?
> >
> > Once you enter TeX, the output file has been opened. The very concept
> > of a filesystem forbids you to change the filehandle while writing. So
> > no, it is not possible easily.
>
> But it can be done sneakily …
>
>
> % start demo
> \enabledirectives[system.callbacks.permitoverloads]
> % previous line allows redefinition of ‘wrapup_run’
>
> % to keep the code short, I use a direct definition of
> % \idcode and \ctxlua. Nicer would be to store the desired
> % output name in a lua variable and replace the
> % \ctxlua with \startluacode … \stopluacode with
> % a string.format inside it.
>
> \def\idcode{something}
>
> \ctxlua{callbacks.register('wrapup_run', function()
> os.execute("cp \jobname.pdf doc-\idcode.pdf")
> end)}
>
> \starttext
> Hello from \idcode
> \stoptext
> % stop demo
>
> Taco
>
> ___
> 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
> ___
___
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
___
[NTG-context] how to set the name of outputfile using a value defined in the source
Hi all,
I'm getting back to using ConTeXt after a couple of years, so I might
be missing something obvious...
I would like to add an I.D. code to the name of my outputfile, but
since this will be used in an automated environment I would like to
load the ID-code from the source file.
MWE: test.tex
\starttext
\def\idcode{something}
Some text, whatever.
\stoptext
If I typeset with: context text --result=test-idcode the result is
obviously "test-idcode.pdf", but I want to get a file name:
"test-something.pdf"
Is this possible?
Thanks,
Jelle
___
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
___
