on my (ab)use of Radio Userland
Also the HTTP Redirection header is obeyed and stored to reduce the number of round trips retrieving files. In addition all this information is stored in a seperate file so that if you are using Aggie to read an OPML file from a remote site you still get all the speed enhancements.
What about this one?
people: no ones, just
Truncated, not the post, but the tag, after "no"
Radio.root contains system.verbs.builtins.radio.html.viewNewsItems.txt, which is what this macro calls. That routine contains a subroutine called decodeEntities:
which calls radio.string.decodeEntities
which calls, in turn, xml.entityDecode after replacing all the apostrophes.
- include a meta refresh element in your rss: this will redirect their aggregator page
- include a title element in your rss: this will cause all items following (in the aggregator) to not render in your browser
- fill in the blank — I'll probably find another
Why is this bug annoying me so much? Because otherwise I would really like using this tool. If I can't use it to write technical documentation, then I won't use at all.
(Wow, the double-decode of title really broke the aggregator.)
I'm posting my tests to this feed, including meta elements. Hopefully I won't forget to uncheck the "Home Page" category checkbox. So far it seems that Radio is encoding just dandy.
It should NOT execute, since the angle-brackets are entity-encoded.
Later: That's whacked. It refreshes even w/o the angle brackets making it a tag. What's up with that?
Isn't markup wonderful?