From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: [stoped working]
Date: Sun, 13 Sep 2015 15:16:04 +0200 [thread overview]
Message-ID: <877fnufoiz.fsf@mat.ucm.es> (raw)
In-Reply-To: <87h9mymtgk.fsf@tullinup.koldfront.dk>
>> "Adam" == Adam Sjøgren <asjo@koldfront.dk> writes:
> Uwe writes:
>> You are not going to believe that but the feature stopped working. With
>> the same setting as yesterday the images are not longer fetched.
> Well, then the webserver in the other end (latex.codecogs.com) returns:
> HTTP/1.1 500 Internal Server Error.
> Content-Type: text/html.
> Content-Length: 369.
> Date: Sun, 13 Sep 2015 11:43:58 GMT.
> Server: lighttpd/1.4.36.
> .
> <?xml version="1.0" encoding="iso-8859-1"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
> <head>
> <title>500 - Internal Server Error</title>
> </head>
> <body>
> <h1>500 - Internal Server Error</h1>
> </body>
> </html>
> It _is_ kind of hard for Gnus to display the images.
How do you see this messages?
> That is the downside of relying on a third party to provide images.
But why are displayed in seamonkey/firefox/chrome correctly?
>> In xemacs they are fetched but not displayed.
> I don't know how you concluded that, but I doubt it.
Well I see
--8<---------------cut here---------------start------------->8---
Stored: Email from Uwe Brauer: To: UWE RICHARD OTTO Brauer: Date: Sun,
13 Sep 2015 11:16:58 +0200 Subj:
Retrieval complete.
Reading... 535 bytes.
Contacting latex.codecogs.com:80
tex Actually we have the following situation:
<pre_int>H_1\subse</pre_int><_id id="l0.06521869946887593"> are Hilbert
spaces, a map <pre_int><img_alt
src="http://latex.codecogs.com/gif.latex?%5Cdpi%7B300%7D%5Cinline%09%5CPhi:H%5F1%5Cto%09H%5F1"
width="91" height="14" hseq="2" title="\Phi:H_1\to H_1">\Phi:H_1\to
H</img_alt></pre_int><_id id="l0.3265760676902906"> and we set
<pre_int><img_alt
src="http://latex.codecogs.com/gif.latex?%5Cdpi%7B300%7D%5Cinline%09x%5F{n%2B1}=%5CPhi(x%5Fn)"
width="98" height="16" hseq="3" yoffset="-1"
title="x_{n+1}=\Phi(x_n)">x_{n+1}=\Phi(x</img_alt></pre_int><_id
id="l0.17770456394407674">. Then by the energy estimates we have:
--8<---------------cut here---------------end--------------->8---
Thanks
Uwe
next prev parent reply other threads:[~2015-09-13 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 8:10 math, png: TeX for Gmail, not shown in GNU Emacs Uwe Brauer
2015-09-12 10:48 ` Adam Sjøgren
2015-09-12 12:45 ` Uwe Brauer
2015-09-12 12:54 ` Adam Sjøgren
2015-09-12 13:06 ` Uwe Brauer
2015-09-12 16:14 ` Adam Sjøgren
2015-09-12 17:28 ` Uwe Brauer
2015-09-12 17:39 ` Adam Sjøgren
2015-09-13 8:32 ` [Xemacs] (was: math, png: TeX for Gmail, not shown in GNU Emacs.) Uwe Brauer
2015-09-13 11:45 ` [Xemacs] Adam Sjøgren
2015-09-13 9:05 ` [stoped working] (was: math, png: TeX for Gmail, not shown in GNU Emacs.) Uwe Brauer
2015-09-13 11:47 ` [stoped working] Adam Sjøgren
2015-09-13 13:16 ` Uwe Brauer [this message]
2015-09-13 13:34 ` Adam Sjøgren
2015-09-13 13:26 ` Uwe Brauer
2015-09-13 13:42 ` Adam Sjøgren
2015-09-13 13:46 ` Adam Sjøgren
2015-09-14 17:28 ` Uwe Brauer
2015-09-12 12:53 ` math, png: TeX for Gmail, not shown in GNU Emacs Uwe Brauer
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=877fnufoiz.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.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).