public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Russell <jeff.t.russell-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: autolinks in extended markdown?
Date: Mon, 12 Nov 2012 05:06:22 -0800 (PST)	[thread overview]
Message-ID: <6d06b29d-0439-40ae-8336-21d5c623d2a1@googlegroups.com> (raw)
In-Reply-To: <CAO9PwMUDgceGmh6mgA0B58bbWMOse7C7v5NuY3frMdk2VPE6_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

One point to consider is that monospace fonts usually are designed to 
visually distinguish, for example, 0 and O, or 1 and l, which is important 
if you are trying to use an address from a printed document.

Jeff

On Sunday, November 11, 2012 11:16:10 PM UTC, John Gabriele wrote:
>
> On Sun, Nov 11, 2012 at 5:46 PM, John MacFarlane <fiddlo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org<javascript:>> 
> wrote: 
> > Pandoc puts link addresses and emails in "code" tags. 
> > I think I may change that.  Do people have strong feelings 
> > either way? 
>
> I think they look better as regular text (not monospace). Also, long 
> urls take up less room when rendered as regular text. 
>
> ---John 
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msg/pandoc-discuss/-/A8ipzggQPIwJ.
For more options, visit https://groups.google.com/groups/opt_out.



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

  parent reply	other threads:[~2012-11-12 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 19:56 Pablo Rodríguez
     [not found] ` <50A002F5.8080304-S0/GAf8tV78@public.gmane.org>
2012-11-11 22:46   ` John MacFarlane
     [not found]     ` <20121111224617.GF4399-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org>
2012-11-11 23:16       ` John Gabriele
     [not found]         ` <CAO9PwMUDgceGmh6mgA0B58bbWMOse7C7v5NuY3frMdk2VPE6_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-12 13:06           ` Jeff Russell [this message]
     [not found]             ` <6d06b29d-0439-40ae-8336-21d5c623d2a1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2012-11-12 14:32               ` Ryan Gray
2012-11-12 19:43       ` Pablo Rodríguez

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=6d06b29d-0439-40ae-8336-21d5c623d2a1@googlegroups.com \
    --to=jeff.t.russell-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).