GithubHelp home page GithubHelp logo

Comments (5)

nemesit avatar nemesit commented on June 2, 2024

yeah I think this syntax is a bit weird

[foo\][\bar][#citeKey]
[foo\][\bar][#citeKey;]

maybe change this and the way to choose between citep and citet to something more obvious.
I like that the syntax is close to other that of other features e.g. including images.
For the most part I use TextExpander to expand mmd syntax e.g. ,,mdcite will give me defaults and options to select between different ways to cite. So in the end the syntax only matters for readability purposes (for me)

from multimarkdown-6.

fletcher avatar fletcher commented on June 2, 2024

To avoid making the code unduly complicated, I think that both of the arguments (foo and bar) should be wrapped inside a single pair of brackets ([...]). What happens inside the brackets can be customized.

Options could include:

[[foo][bar]][#citekey]
[foo/bar][#citekey]
[foo|bar][#citekey]

or something else;

As for the citep and citet, I wonder how often somone uses both variants in the same document? An option would be to specify one of the two in the metadata. This would avoid the need for the semicolon.

from multimarkdown-6.

muziejus avatar muziejus commented on June 2, 2024

I use both in the same document, as it's typical in literary studies to use parens when citing a novel or something that is cited repeatedly/throughout the article, but footnotes when citing something just once or twice.

However, I use the one requiring the ; more often, meaning there are often mistakes where I've forgotten the semicolon! The semicolon seems to be an arbitrary modifier, but I can't think of a better solution.

As I've mentioned on the email list, I remap \citep and \citet anyway in my .md file, as I use biblatex:

<!--
  \newcommand{\citep}[2][]{\pnotecite[#1]{#2}} % Parenthetical: [page][#Citekey]
  \newcommand{\citet}[2][]{\autocite[#1]{#2}} % Textual, so footnote here: [page][#Citekey;]
-->

from multimarkdown-6.

fletcher avatar fletcher commented on June 2, 2024

I've implemented citations in MMD-6 (both as reference and inline variants, just like footnotes, abbreviations, and glossary terms).

I'm still open to tweaking the syntax to address some of the things above, if anyone has any good ideas.

from multimarkdown-6.

fletcher avatar fletcher commented on June 2, 2024

The latest commit to the development branch includes 2 changes:

  1. HTML Footnotes use <sup>1</sup> instead of [1].

  2. HTML Citations use (1) instead of [1].

from multimarkdown-6.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.