Re: Specifying location of bibliography in document

["Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>]

On 09/01/2015 09:31 PM, Daniel Staal wrote:
> --As of September 1, 2015 7:55:18 PM +0200, Pablo Rodríguez is alleged to 
> have said:
>> [...]
>> The problem with visual editors is that users many not know what they
>> are actually doing.
>>
>> In that case, I think there is no gain in using pandoc.
> 
> There is some gain - the markup is structurally simpler than many others, 
> and it's more cross-platform and widely specified.  Basically, you get a 
> more compatible and easier to work with file, even if the users don't 
> directly deal with it.

Cross-platform compatibility depends in that particular case on having
the tool that deals with pandoc the right way.

I have never used a visual tool for Markdown. But I’m almost sure that
there would be some coding that could only be edited in the source.

>> My comment now is to avoid using XML syntax, since it is harder for
>> newcomers.
> [...]
> So, to sum up: This works, and if you have a good idea for what the syntax 
> for a div or a span *should* be, we're all ears.  ;)

I made my proposal, but you didn’t listen to me ;-):

[this should be a span]{.span #unique-span}

[[[ {.div #unique-div}
and following the same logic

this should be a division
]]]

This syntax is consistent with hyperlinks. And having different opening
and closing characters makes it clearer for ordinary users (remember, no
programers or computer geeks, just people ;-)).

Of course, I don’t claim to have the definitive solution. But I wonder
whether anyone may have this.

And after some years (https://github.com/jgm/pandoc/issues/168), any
syntax may do the job.

I mean, I have reasons to support my proposal. But I prefer other
implementation (surronding the text) than eternal discussion on proposals.

>> It was only a minor issue. But do you really think that there is a need
>> to limit titles to a single line? In other words, does this exception
>> make sense?
>>
>> I’m not trying to change it (mainly because of backwards compatibility),
>> but I don’t see any reason to handle titles as block elements in a
>> different way from paragraphs (in regard to this rule).
> 
> Well, first off, they aren't really titles.  They are *headings.*  (There's 
> only one title per document, after all...)  And part of this is explained 
> by Markdown's roots as a text-to-html converter; HTML heading elements are 
> block elements that can't contain other block elements (like paragraphs), 
> so it was basically assumed.

You are the native speaker, but I don’t think title is wrong here
(http://www.merriam-webster.com/dictionary/title). Heading seems to be a
more specific denomination.

> But in general, I can see your point.  There's no real reason to assume a 
> heading is any specific length.  Practically, you don't want a heading 
> that's to long because most people won't read it, but that doesn't 
> necessarily mean we should limit it.

It’s not only that. What happens if I use Markdown to format a classical
author. It may be the original German version of the “Critique of Pure
Reason”, with contains such a title (http://korpora.org/Kant/aa03/042.html):

Idee und Eintheilung einer besonderen Wissenschaft unter dem Namen einer
Kritik der reinen Vernunft

If it doesn’t fit on a single line, am I supposed to rephrase the heading?

But we agree here, I don’t want to change this rule in Markdown.


Pablo
-- 
http://www.ousia.tk

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/55E741D8.5060108%40web.de.
For more options, visit https://groups.google.com/d/optout.