I'd be happy to take down the broken RSS feed or refund your purchase price if it bothers you that much. Or feel free to just not use it.

[ I didn't write it. There is no infrastructure in place for pmdev to even look at the code. I thank whoever did write it for donating the effort, even if they didn't manage to get it perfect.

If you looked around a bit you'd probably notice that lots of the XML feeds used to have similar problems and such could be resolved by adding a character encoding header.

The whole site is volunteers. I thank those who volunteer answers and discussions. It is a "gift" culture and I donate to it because it is often fun and I often enjoy helping people or producing something of some value.

Someone on pmdev could probably just write code to produce similar but better output based on viewing the current RSS output (and perhaps how the new XML feeds are done, though they don't handle control characters properly -- which are only sent by non-conforming clients and may already be filtered from node titles, but this should, of course, still be fixed). I'd be grateful if someone cared to volunteer to do that (but I certainly don't feel I'm due such a contribution and understand some of the frustration of trying to do that). Such would certainly motivate me to raise the priority on trying out such code and trying to replace the broken feed.

Frankly, ranting is anything but motivating, for me. ]

                - tye

In reply to Re^3: Broken headlines (gift) by tye
in thread Broken headlines by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.