public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Pinsley <mark-NHpudssogepBDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Where to store pictures
Date: Sun, 25 Jun 2023 06:45:43 -0700 (PDT)	[thread overview]
Message-ID: <68628273-6c1a-4647-9dd3-3853368670bcn@googlegroups.com> (raw)
In-Reply-To: <3a90f125-a388-4f6a-a634-fce8cbe21ce7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2462 bytes --]

Great idea. I am going to give that a try!

On Sunday, June 25, 2023 at 9:02:58 AM UTC-4 Pedro P. Palazzo wrote:

> I use Pinterest. In addition to storing images for free and allowing 
> cross-site direct links, it automatically provides scaled-down version 
> should you need them.
>
> Em sábado, 24 de junho de 2023 às 10:54:29 UTC-3, BPJ escreveu:
>
>>
>>
>> Den lör 24 juni 2023 02:17Mark Pinsley <ma...-NHpudssogepBDgjK7y7TUQ@public.gmane.org> skrev:
>>
>>> I have been storing pictures in a shared google drive and then using the 
>>> link (with some modfiications) to access the picture. It doesn't always 
>>> work. Where do you like to store images?
>>>
>>> Separately if you are not writing a scientific book are you still using 
>>> LaTex or just Pandoc?I feel like I am often inserting HTML code in order to 
>>> center things, have line breaks, when I am using just Pandoc markdown. 
>>>
>>
>> I guess the hardcore way is to store images inside the HTML document as 
>> data URIs (--self-contained will do that.) It used to be frowned upon to 
>> store images and documents on different servers, not only because of the 
>> loading delay but because when people linked to other people's images they 
>> effectively stole their bandwidth, apart from any rights in the images as 
>> such. I'm not sure how much of a problem any of that is nowadays.
>>
>> /bpj
>>
>>
>>> Thanks
>>> Mark 
>>>
>>> -- 
>>> 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/854f51e5-4ea0-4b6b-b5f9-af56828c44d5n%40googlegroups.com 
>>> <https://groups.google.com/d/msgid/pandoc-discuss/854f51e5-4ea0-4b6b-b5f9-af56828c44d5n%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/68628273-6c1a-4647-9dd3-3853368670bcn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4027 bytes --]

      parent reply	other threads:[~2023-06-25 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  0:16 Mark Pinsley
     [not found] ` <854f51e5-4ea0-4b6b-b5f9-af56828c44d5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-24 13:54   ` BPJ
     [not found]     ` <CADAJKhCyDGgjCEZzCY=cYYjG3B5d3KeCveizjdSxertKhzWdzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-25 13:00       ` Pedro P. Palazzo
2023-06-25 13:02       ` Pedro P. Palazzo
     [not found]         ` <3a90f125-a388-4f6a-a634-fce8cbe21ce7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-25 13:45           ` Mark Pinsley [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=68628273-6c1a-4647-9dd3-3853368670bcn@googlegroups.com \
    --to=mark-nhpudssogepbdgjk7y7tuq@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).