ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pavneet Arora <pavneet_arora@waroc.com>
To: ntg-context@ntg.nl
Subject: Re: What is the prescribed way to add attachments to	a list posting?
Date: Tue, 22 Nov 2011 09:20:37 -0500	[thread overview]
Message-ID: <1321971637.14617.10.camel@Nokia-N900> (raw)
In-Reply-To: <CALBOmsavVDxOtB3F1wHGO+cnTzNrp-fjf7D9ygKrgFh+QMJ5xQ@mail.gmail.com>


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

Thanks, Mojca. I was looking at the web-interface of the archives. It seems that the attachments *were* including in the mailing list message, but were converted/stripped in the archives.

Regards.
--
Sent from my Nokia N900. Please excuse my brevity.

----- Original message -----
> On Tue, Nov 22, 2011 at 14:17, Pavneet Arora wrote:
> > In my last posting, I had included the source and .pdf output as
> > attachments, but it seems that the source was included in-line and the
> > .pdf was discarded. Is there a prescribed way to include attachments?
>
> Attachments usually survive, but they may not exceed a certain size
> limit. Usually that is problematic - PDF documents may get very large,
> even the most simple ones usually exceed size limit (it depends on
> what engine and what fonts you use).
>
> I don't know why text attachment was converted into an inline one
> (gmail often displays simple text documents inline, but that doesn't
> mean that they were converted by mailman). Usually that doesn't happen
> unless a moderator did that or something weird happened :).
>
> Many people upload PDFs to their own servers and post a link if PDFs
> are large. Sometimes you can attach PNG with a screenshot of
> problematic part. You could also make an attachment in bug reporting
> software (http://tracker.luatex.org/) if you are reporting a bug.
>
> Mojca


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

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2011-11-22 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 13:17 Pavneet Arora
2011-11-22 13:24 ` Mojca Miklavec
2011-11-22 14:20   ` Pavneet Arora [this message]
2011-11-22 16:07     ` Mojca Miklavec
2011-11-23  8:33       ` Patrick Gundlach

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=1321971637.14617.10.camel@Nokia-N900 \
    --to=pavneet_arora@waroc.com \
    --cc=ntg-context@ntg.nl \
    /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).