public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: help filtering languages
Date: Mon, 13 Mar 2023 19:43:11 +0000	[thread overview]
Message-ID: <ZA98zxHsNXsGRE9c@localhost> (raw)
In-Reply-To: <591336ef-c61e-31a8-3f44-2625551f7e07-S0/GAf8tV78@public.gmane.org>

{: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, 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. Maybe a custom reader would be better suited. But it would be easier to stick to existing conventions!

Le Monday 13 March 2023 à 08:25:15PM, Pablo Rodríguez a écrit :
> Dear list,
> 
> I would like to add (natural languages) to attributes, such as in:
> 
>   _Deutsch_{:de}
> 
> A filter would help to filter the language attribute defined as
> everything after a colon (preceded by a space or at the start of the
> attributes) and before a space (or the end of the attributes).
> 
> If I’m not wrong, this would filter:
> 
>   _Straße_{:de-1901}
> 
> but it would avoid:
> 
>   # Title {#first:title}
> 
> I think the filtering rule is pretty simple, but I don’t know how to
> write the filter.
> 
> Many thanks in advance,
> 
> 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/591336ef-c61e-31a8-3f44-2625551f7e07%40web.de.

-- 
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/ZA98zxHsNXsGRE9c%40localhost.


  parent reply	other threads:[~2023-03-13 19:43 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 [this message]
2023-03-13 20:46     ` Pablo Rodríguez
     [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=ZA98zxHsNXsGRE9c@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).