Re: Inline images, was Re: Variable slur thickness

[David Wright]

On Thu 10 Mar 2016 at 10:19:29 (-0600), Cynthia Karl wrote:
> On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst  
> schrieb:
> > 
> > HTH,
> > Abraham
> > 
> > P.S. Some of the power users on this list filter inline images, so if you
> > wouldn't mind making the image an attachment next time, I know they'll
> > appreciate it. :-)
> 
> Why on earth would anyone filter inline images?  They are extremely 
> convenient.  They’re right there in the email, one doesn’t have to change 
> context to a browser and interrupt the flow of reading the message.

There are plenty of explanations on the web about the disadvantages of
inline images. Myself, I don't filter them, but I read emails as text,
which amounts to the same thing.

> On the other hand, for me who gets the lilypond-user messages in the Digest 
> form, attachments suck big time.  For example, below after the " next 
> part “ line is a link to such an attachment (I think).  When I click on 
> that link, the result is:
> 
> > Not Found
> > 
> > The requested URL 
> > /archive/html/lilypond-user/attachments/20160310/4addc8f3/attachment.html 
> > was not found on this server.

Agreed, there is a problem. The links are set wrongly, yet the
attachments exist elsewhere. For example, the attachment given
in the digest as
http://lists.gnu.org/archive/html/lilypond-user/attachments/20160312/6eba7c13/attachment.png
is actually at
http://lists.gnu.org/archive/html/lilypond-user/2016-03/pngHJxj6irVRF.png

> That’s not very convenient at all.  Am I the only one with this problem?  
> What’s the solution?

Dunno. Step one is emailing the webmaster, which I've done.

> Maybe it would be nice if inline images were also added as attachments?

Yes; maybe they will.

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

[Brian Barker]

At 10:56 10/03/2016 -0600, Matthew Skala wrote:

On Thu, 10 Mar 2016, Brian Barker wrote:

At 10:33 10/03/2016 -0600, Matthew Skala wrote:

... HTML in email is usually spam.


You are joking, of course!


No.


OK, I'll rephrase that to help you: either you *have to be* joking or 
you are plain wrong.


Brian Barker  



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

[mskala]

On Thu, 10 Mar 2016, Brian Barker wrote:
> At 10:33 10/03/2016 -0600, Matthew Skala wrote:
> > ... HTML in email is usually spam.
>
> You are joking, of course!

No.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

[Brian Barker]

At 10:33 10/03/2016 -0600, Matthew Skala wrote:

... HTML in email is usually spam.


You are joking, of course!

Brian Barker 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

[tisimst]

Pat,

On Thu, Mar 10, 2016 at 9:22 AM, Cynthia Karl [via Lilypond] <
ml-node+s1069038n188389...@n5.nabble.com> wrote:

> On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=188389&i=0>> schrieb:
> >
> > HTH,
> > Abraham
> >
> > P.S. Some of the power users on this list filter inline images, so if
> you
> > wouldn't mind making the image an attachment next time, I know they'll
> > appreciate it. :-)
>
> Why on earth would anyone filter inline images?  They are extremely
> convenient.  They’re right there in the email, one doesn’t have to change
> context to a browser and interrupt the flow of reading the message.
>
> On the other hand, for me who gets the lilypond-user messages in the
> Digest form, attachments suck big time.  For example, below after the
> " next part “ line is a link to such an attachment (I think).
> When I click on that link, the result is:
>
> > Not Found
> >
> > The requested URL
> /archive/html/lilypond-user/attachments/20160310/4addc8f3/attachment.html
> was not found on this server.
>
> That’s not very convenient at all.  Am I the only one with this problem?
> What’s the solution?
>
> Maybe it would be nice if inline images were also added as attachments?
>

Frankly, you won't get any argument from me about having in-line images, I
just know that some other regular list followers have mentioned this in the
past. Perhaps doing both is how to satisfy both worlds, like you said?

Best,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Inline-images-was-Re-Variable-slur-thickness-tp188389p188391.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

[mskala]

On Thu, 10 Mar 2016, Cynthia Karl wrote:
> Why on earth would anyone filter inline images?

I filter HTML, because HTML in email is usually spam.  "Inline" images
imply HTML and thus get filtered too.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Inline images, was Re: Variable slur thickness

[Cynthia Karl]

On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst  
schrieb:
> 
> HTH,
> Abraham
> 
> P.S. Some of the power users on this list filter inline images, so if you
> wouldn't mind making the image an attachment next time, I know they'll
> appreciate it. :-)

Why on earth would anyone filter inline images?  They are extremely convenient. 
 They’re right there in the email, one doesn’t have to change context to a 
browser and interrupt the flow of reading the message.

On the other hand, for me who gets the lilypond-user messages in the Digest 
form, attachments suck big time.  For example, below after the " next 
part “ line is a link to such an attachment (I think).  When I click on 
that link, the result is:

> Not Found
> 
> The requested URL 
> /archive/html/lilypond-user/attachments/20160310/4addc8f3/attachment.html was 
> not found on this server.

That’s not very convenient at all.  Am I the only one with this problem?  
What’s the solution?   

Maybe it would be nice if inline images were also added as attachments?

Regards,
Pat Karl
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188377.html
> Sent from the User mailing list archive at Nabble.com.
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user