public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: removing highlights and escape values
Date: Tue, 9 May 2023 19:44:07 +0200	[thread overview]
Message-ID: <CADAJKhCoYnfGisEsq6fW749_i8Kj_9_bF5cqguoyDrScOptqvw@mail.gmail.com> (raw)
In-Reply-To: <bc3186fd-822a-40da-99d2-9454caeabb3en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 5819 bytes --]

Den tis 9 maj 2023 12:59Stephan Meijer <me-nPKYAObcRdo6Blr+0TYHagC/G2K4zDHf@public.gmane.org> skrev:

> *> Don't use ChatGPT to "write code"! You will get garbage which may harm
> your computer and/or files if you run it!*
>
> I am sure It won't damage your computer. It will probably be not perfect,
> but with some common sense you will be safe.
>

If you are able to see that it is safe or not you are able to write the
code yourself, and some shit code might manage to wipe your data or burn
your CPU. Not very likely perhaps but possible. Remember that ChatGPT has
no semantic sense. It just assembles "words" based on statistical
probability, and it shows!


> On Monday, 8 May 2023 at 19:28:52 UTC+2 Mark Pinsley wrote:
>
>> Thank you!
>>
>> Yeah ChatGPT isn't really very good at writing code unless you already
>> know what you are doing. Then you can modify it. For me, I was trying to
>> find a way to write this. Thank you!
>>
>>
>> On Mon, May 8, 2023 at 11:59 AM BPJ <mel...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>>> Don't use ChatGPT to "write code"! You will get garbage which may harm
>>> your computer and/or files if you run it!
>>>
>>> This filter will do what you want:
>>>
>>> ``````lua
>>> local str = pandoc.Str
>>> local function quote (q)
>>>   return pandoc.RawInline('markdown', q)
>>> end
>>> local quote_pat = re.compile(
>>>   [[ {| ( [^"']+ -> str / ["'] -> quote )* |} ]],
>>>   { str = str, quote = quote }
>>> )
>>> function Str (elem)
>>>   return quote_pat:match(elem.text)
>>> end
>>> function Span (elem)
>>>   if 1 == #elem.classes and 'mark' == elem.classes[1] then
>>>     return elem.content
>>>   end
>>>   return nil
>>> end
>>> ``````
>>>
>>> /bpj
>>>
>>> Den mån 8 maj 2023 00:09Mark Pinsley <ma...-NHpudssogepBDgjK7y7TUQ@public.gmane.org> skrev:
>>>
>>>> I have a bunch of docx that I want to convert to MD.
>>>>
>>>> The file contains highlighting and it also contains both quotes and
>>>> double quotes
>>>>
>>>> For ease of someone being able to look at this MD, i want to remove the
>>>> escape sequece for the quotes and double quotes.
>>>>
>>>> I also want to remove the highlighting
>>>>
>>>> ChatGPT wrote this LUA for me but it doesn't seem to work. Are there
>>>> alternatives
>>>>
>>>> function process_inlines(inlines)
>>>>     local result = {}
>>>>     for _, inline in ipairs(inlines) do
>>>>         if inline.t == "Str" then
>>>>             inline.text = inline.text:gsub('\\"', '"'):gsub("\\'", "'")
>>>>         elseif inline.content then
>>>>             inline.content = process_inlines(inline.content)
>>>>         end
>>>>         table.insert(result, inline)
>>>>     end
>>>>     return result
>>>> end
>>>>
>>>> function process_blocks(blocks)
>>>>     local result = {}
>>>>     for _, block in ipairs(blocks) do
>>>>         if block.content then
>>>>             block.content = process_inlines(block.content)
>>>>         end
>>>>         table.insert(result, block)
>>>>     end
>>>>     return result
>>>> end
>>>>
>>>> function Pandoc(doc)
>>>>     doc.blocks = process_blocks(doc.blocks)
>>>>     return doc
>>>> end
>>>>
>>>> the command I used was:
>>>>  pandoc "TestHighlightQuotes.docx" --lua-filter
>>>> remove_escaped_quotes.lua --wrap=none --reference-links -o output.md
>>>>
>>>> Is there another way, or did I do something wrong?
>>>>
>>>> --
>>>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/pandoc-discuss/ef709575-3717-493f-b6d8-62862c98d3d8n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/pandoc-discuss/ef709575-3717-493f-b6d8-62862c98d3d8n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>>
>> You received this message because you are subscribed to a topic in the
>>> Google Groups "pandoc-discuss" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/pandoc-discuss/dF3psW96pkA/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhA_g%3D6gfAJONkb3AwdQ9Xqn8PvwUg-fAVEjsKE56%2B%2BgFg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhA_g%3D6gfAJONkb3AwdQ9Xqn8PvwUg-fAVEjsKE56%2B%2BgFg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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/bc3186fd-822a-40da-99d2-9454caeabb3en%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/bc3186fd-822a-40da-99d2-9454caeabb3en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CADAJKhCoYnfGisEsq6fW749_i8Kj_9_bF5cqguoyDrScOptqvw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 8979 bytes --]

      parent reply	other threads:[~2023-05-09 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 22:08 Mark Pinsley
     [not found] ` <ef709575-3717-493f-b6d8-62862c98d3d8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-08 15:59   ` BPJ
     [not found]     ` <CADAJKhA_g=6gfAJONkb3AwdQ9Xqn8PvwUg-fAVEjsKE56++gFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-08 17:28       ` Mark Pinsley
     [not found]         ` <CAOtJyj5-+o3=w-dT1wYbusgTsRv=0JA5J3LE96mN53sAE9eQkg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-09 10:58           ` Stephan Meijer
     [not found]             ` <bc3186fd-822a-40da-99d2-9454caeabb3en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-09 17:44               ` BPJ [this message]

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=CADAJKhCoYnfGisEsq6fW749_i8Kj_9_bF5cqguoyDrScOptqvw@mail.gmail.com \
    --to=melroch-re5jqeeqqe8avxtiumwx3w@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).