Hi ... I'm all in favour of as many examples as possible -- cutting and pasting other peoples code is always a quick way to get the hang of something, IMHO. In...
... Provided what you cut from is accurate. I've seen plenty of feed using header namespaces but never using the modules. They obviously cut and paste...
All unicode encodings (UTF-8, UTF-16, whatever) support the same characters. The different encodings are simply that -- different ways of representing the...
That's a great understatement. As there are also sorts of endian issues as well. There are /most certainly/ characters in UTF-16 that cannot be represented...
That's simply not true - UTF-8 can encode any unicode character. UTF-8 also has no BOM isues (although it can use a BOM as part of an encoding signature). Byte...
UTF-8 and UTF-16 are different encodings of the same character set (unicode), UTF-8 uses a variable (1to3) bytes per character, whilst UTF-16 uses a fixed 2...
I believe you've left out the possibility for surrogate pairs, Simon. UTF-8 may require more than 3 bytes per character (and UTF-16 more than 2). See...
Yes, surrogate pairs change that [making a complex issue even more complex]. Still back to the original point, UTF-8 and UTF-16 are different encodings of the...
I'm busy now, but I think it's important to state this clearly: mod_richequiv does not support the inclusion of fragments of a different encoding to the rss...
... Yes, showing your examples, assuming more than one, each in a different encoding would go a long way toward helping people interested in using the concept...
Hi there, ... What would be the point of converting to UTF-8 if the interesting characters are then entified? Wouldn't it be better with three examples: -...
... Entity encoding, presumably that found in HTML would likely require another parsing step. Or at least the requirement that your parser understand that not...
... Hash: SHA1 http://cvs.web.resource.org/*checkout*/webres/rss/1.0/modules/link/index.html?rev=HEAD&content-type=text/html The PURL should be updated in a...
Hi (Bill), ... I was actually refering to the &####; encoding, but I see now that the correct term for this is "Character Reference" [1], I thought I had seen...
Hi there, ... Well, they *could* be, but the point would be exactly that, to choose an encoding that necesitated the character references. Any encoding would...
hey this is a cool idea. I'm getting a funny error message though at the top of the feed: <channel rdf:about="http://www.grassrootsmusic.com/concerts/"> <br> ...
I ran some queries across 11,246 feeds in Syndic8 and came up with a bunch of interesting data. I apologize for the poor format. I will put this on a web page...
... Could that possibly be because 0.92 feeds tend to include the whole article body (default for radio if I'm not mistaken), whereas most other feeds are...
A lot of you will already have caught this via Scripting News but I launched a new service this week called myRSS (http://myrss.com). It lets anyone create an...
Jeff... This is interesting. Thanks for sharing. Assuming I didn't make any rounding errors this is the breakdown of feed version counts: Version Count .91...
... That is indeed correct. The majority of 'large description items' are coming from Radio feeds. This is largely because of how Radio works. The spec does...
... That is indeed correct. The majority of 'large description items' are coming from Radio feeds. This is largely because of how Radio works. The spec does...
... Indeed, some folks are motivated to use a reader for entire bits of text. However, consider that many RSS feeds are coming from sites that depend upon ...
... allow aggregated RSS items by topic, based upon a search of the full text of articles. RSS is about having metadata which gets you to original content and...
Hi all, I'd post this to a Radio specific forum but, well, you know the hassles there. All this talk about new formats for Radio made me wonder what it would...
