From: "mame (Yusuke Endoh)" <mame@...>
Date: 2013-12-26T23:06:15+09:00
Subject: [ruby-core:59331] [ruby-trunk - Bug #9304] Invalid XML entity	references


Issue #9304 has been updated by mame (Yusuke Endoh).


Don't mind, I found the repo of your blog: https://github.com/ploeh/ploeh.github.com

I could reproduce the issue successfully ... only when I open rss.xml with Chrome!
With Firefox, Konqueror, wget, and curl download it without "&tt;".

So I now guess this is a bug of Chrome's XML viewer.
Are you also using Chrome?  Can you reproduce the issue without Chrome?

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Bug #9304: Invalid XML entity references
https://bugs.ruby-lang.org/issues/9304#change-43911

Author: ploeh (Mark Seemann)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: 2.0.0
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN


=begin
It seems that the escapeHTML method occasionally generates the invalid XML entity reference (({&tt;})) when XML escaping.

See this Stack Overflow question for more details: http://stackoverflow.com/q/20563078/126014

Although I see this issue manifest itself in Jekyll, the Jekyll maintainers closed the issue I reported there because the Jekyll filter delegates to CGI.escapHTML.

Could it be a but in escapeHTML?

I'm seeing this on my own system, which is currently reporting:

$ ruby --version

ruby 2.0.0p247 (2013-06-27) [i386-mingw32]

but I'm also seeing this on GitHub pages, and I don't know the exact version of Ruby running in that environment.
=end


-- 
http://bugs.ruby-lang.org/