From: Kay Sievers <kay.sievers@vrfy.org>
To: Yasushi SHOJI <yashi@atmark-techno.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb - Use <description> instead of <content:encoded>.
Date: Thu, 18 Aug 2005 18:01:09 +0200 [thread overview]
Message-ID: <20050818160109.GA7237@vrfy.org> (raw)
In-Reply-To: <87ll2zwc4u.wl@mail2.atmark-techno.com>
On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote:
> Use <description> instead of <content:encoded>.
>
> RSS 2.0 Specification doesn't have <content:encoded>.
> see http://blogs.law.harvard.edu/tech/rss
See here:
http://www.notestips.com/80256B3A007F2692/1/NAMO5P9UPQ
The <description> element is designed to contain plain text ONLY. When
the content of your items contains anything other than plain text i.e.
HTML or XHTML the <content:encoded> element should be used.
Hmm, there was a request to change it to "encoded" and the mentioned page
sounded reasonable to me. I will happily change it to the "correct"
format, if you provide _authoritative_ information that we can trust.
"It works in XY-reader" does not count. :)
Thanks,
Kay
next prev parent reply other threads:[~2005-08-18 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 14:30 [PATCH] gitweb - Use <description> instead of <content:encoded> Yasushi SHOJI
2005-08-18 15:36 ` Sven Verdoolaege
2005-08-18 16:52 ` Yasushi SHOJI
2005-08-18 16:01 ` Kay Sievers [this message]
2005-08-18 16:26 ` Yasushi SHOJI
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=20050818160109.GA7237@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=git@vger.kernel.org \
--cc=yashi@atmark-techno.com \
/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).