[ Adding Org ML back to CC ]
András Simonyi writes:
> On Thu, 19 Jan 2023 at 10:56, Ihor Radchenko wrote:
>> So, do I understand correctly that italics, bold, subscript,
>> superscript, small-caps, and nocase must be passed to the CSL processor
>> in a format understood by CSL? Everything else
Dear All,
On Thu, 19 Jan 2023 at 11:15, M. ‘quintus’ Gülker
wrote:
> That is, the macro has to work both in a citation and in> normal text. Even
> if a @@csl: construct would be ignored in normal text,> I cannot see how to
> write the macro then, because something like
>
> #+MACRO: name @@
Am Donnerstag, dem 19. Januar 2023 schrieb András Simonyi:
> hopefully somebody more knowledgeable than me can comment on how
> viable this is, but would a @@csl like export snippet construct help
> with the problem?
> In that case your macro could be along the lines of
>
> #+MACRO: name @@csl:$1
András Simonyi writes:
> As for the question of other elements, I proposed the custom
> backend-based approach because CSL has its own rich-text markup (which
> is actually not simply a subset of Org's, for example, it contains
> small-caps, which is not in Org), and, consequently, Citeproc-el ha
András Simonyi writes:
> In that case your macro could be along the lines of
>
> #+MACRO: name @@csl:$1@@
>
> and -- assuming the custom export backend approach I proposed in the
> patch -- we would only need to make sure that the inline @@csl export
> snippets are exported as is by this "csl" b
Am Donnerstag, dem 19. Januar 2023 schrieb András Simonyi:
> apologies for replying that late. If I understand the situation
> correctly, we could handle the question of allowing macros in
> citations independently of the handling of other constructs, because
> macros are resolved before processi
Dear All,
On Thu, 19 Jan 2023 at 09:35, M. ‘quintus’ Gülker
wrote:
> I am not sure this targets the usecase I am pursuing, which is to use
> macros to produce @@latex: escape constructs in order to have small-caps
> markup in the citation footnotes:
>
> #+MACRO: name @@latex:\textsc{$1}h
Dear All,
apologies for replying that late. If I understand the situation
correctly, we could handle the question of allowing macros in
citations independently of the handling of other constructs, because
macros are resolved before processing citations, so they have no
effect on the input of Citep
M. ‘quintus’ Gülker writes:
> I probably have not much to contribute to this rather technical thread,
> but Ihor has redirected me here two times for my citation formatting
> questions[1][2]. So I would like to ask if there is something I can do to
> accelerate its inclusion into org so that I ca
Dear all,
I probably have not much to contribute to this rather technical thread,
but Ihor has redirected me here two times for my citation formatting
questions[1][2]. So I would like to ask if there is something I can do to
accelerate its inclusion into org so that I can start using macros in
cit
András Simonyi writes:
> On Wed, 2 Nov 2022 at 07:28, Ihor Radchenko wrote:
>
>> I do not think that CSL limitations are really limiting us.
> ...
> I'm not really familiar with the internals of the Org exporter but,
> looking at the ox.el code, macros and babel calls are processed and
> resolve
Dear All,
On Wed, 2 Nov 2022 at 07:28, Ihor Radchenko wrote:
> I do not think that CSL limitations are really limiting us.
>
> - Allowing macros will be handled by ox.el itself automatically
> - Export snippets can also be processed without much issue (consider
> direct LaTeX code)
> - inline-
András Simonyi writes:
> thanks for pointing out the problem!! I've attached a new version of
> the patch, in which the custom exporter backend has an (in many cases
> trivial) translator for all currently allowed objects.
Thanks!
>> And we may add more, as discussed in
>> https://orgmode.org/l
Dear All,
On Thu, 27 Oct 2022 at 06:10, Ihor Radchenko wrote:
> This will render e.g. strike-through empty.
> Note that citation references may contain the following Org markup objects:
> '(bold code entity italic
> latex-fragment strike-through subscript
> superscript underline verbatim)
th
András Simonyi writes:
> the attached patch improves the parsing and exporting of cite
> prefixes, suffixes and locators -- the most noticeable change is
> probably the support for formatted locators and of underlining in
> general. Comments are welcome.
Thanks!
> +(defconst org-cite-csl--exp
Dear All,
the attached patch improves the parsing and exporting of cite
prefixes, suffixes and locators -- the most noticeable change is
probably the support for formatted locators and of underlining in
general. Comments are welcome.
best wishes,
András
From 5bec7025f66eb65f13a701dc616aca244011
16 matches
Mail list logo
