public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: help filtering languages
Date: Mon, 13 Mar 2023 21:46:19 +0100	[thread overview]
Message-ID: <103a971c-503b-e15e-8e1d-2b9700099138@web.de> (raw)
In-Reply-To: <ZA98zxHsNXsGRE9c@localhost>

On 3/13/23 20:43, Bastien DUMONT wrote:
> {:de} will be parsed as a string, not as an attribute list.
> Attributes are of the form key=value. In this case, you can write
> (-f commonmark+attributes):
>
> _Deutsch_{lang=de}
>
> What you propose is a syntax extension

Many thanks for your reply, Bastien.

I know there is a way to full attribute specification, since the
original proposal is almost a decade old
(https://github.com/jgm/pandoc/issues/895 [which was superseded by
https://github.com/jgm/pandoc/issues/3451]).

> and it would be quite difficult to write a filter taking into
> account multiple attributes and cases where the {...} string is
> immediately followed by other characters.

Well, I see what I was missing here.

> Maybe a custom reader would be better suited.

I wouldn’t mind to add this to (a custom version of) djot. But I clearly
lack the knowledge to do that.

> But it would be easier to stick to existing conventions!

I’m used to the convention (although I‘d rather avoid it, since it tend
to mix languages a lot), but when explaining CommonMark/Markdown to
newcomers, this is one important exception to lightweight markup.

And believe me, it is not easy to explain the key="value" attribute
syntax (it doesn’t make it easier to ignore the quotes) to people with
practically no computer background at all. Because this goes on top of a
bunch of new things for them (which would make anyone explode).

Many thanks for your help,

Pablo

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/103a971c-503b-e15e-8e1d-2b9700099138%40web.de.


  reply	other threads:[~2023-03-13 20:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 19:25 Pablo Rodríguez
     [not found] ` <591336ef-c61e-31a8-3f44-2625551f7e07-S0/GAf8tV78@public.gmane.org>
2023-03-13 19:43   ` Bastien DUMONT
2023-03-13 20:46     ` Pablo Rodríguez [this message]
     [not found]       ` <103a971c-503b-e15e-8e1d-2b9700099138-S0/GAf8tV78@public.gmane.org>
2023-03-15  8:32         ` BPJ
     [not found]           ` <CADAJKhDcpBdJxQO7qCbnj2Tk+kuxuVrh+HGS7eg8JoUoGSuC0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-15 19:45             ` Pablo Rodríguez
     [not found]               ` <f5687eba-f82c-64c2-21b8-94093a1158f5-S0/GAf8tV78@public.gmane.org>
2023-03-16  9:32                 ` Julien Dutant
     [not found]                   ` <49e8c09d-513a-47e5-a85e-c4cf9ca01d5en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-16 17:45                     ` Pablo Rodríguez
     [not found]                       ` <c54cca0e-6eaf-273b-caaa-882f5d9e1c1e-S0/GAf8tV78@public.gmane.org>
2023-03-16 21:28                         ` Julien Dutant
     [not found]                           ` <c238d079-4ba5-4f39-8171-c17e1119d4c5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-20 17:20                             ` Pablo Rodríguez
     [not found]                               ` <68de3cab-a729-7728-2652-774a8ff599f4-S0/GAf8tV78@public.gmane.org>
2023-03-20 21:22                                 ` Julien Dutant

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=103a971c-503b-e15e-8e1d-2b9700099138@web.de \
    --to=oinos-s0/gaf8tv78@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).