OK. Without writing a lengthy converter, I can't convert
character entities in the XML stream e.g. ∞ or
∞ to its proper character (which CF can't handle
anyway since it doesn't support Unicode characters).
So, for my implementation (not sure about you guys who
are brave enough to use my stuff), I will be doing this:
REReplaceNoCase(HTMLEditFormat(Variables.striSyndicateString, '-1'),
'&(##?[[:alnum:]]+);', '&\1;', 'ALL');
And, yes, that's my "patch" for now. Till Allaire/Macromedia
or some custom tag (that uses no COM/DCOM, Java, or CORBA)
that provides character entity conversion AND CF6 is out,
I will keep my iSyndicate code this way. :)
James Ang
Webmaster, TekBay.com
[EMAIL PROTECTED]
----- Original Message -----
From: "James Ang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 25, 2001 12:11 PM
Subject: Re: [cf-xml] SOXML and iSyndicate
Tom,
Just in case you have not caught the bug....
I only convert ' in the iSyndicate XML
to '. I did not attempt convert other character
entities. Hence, the data stored in WDDX format
is not what we *really* want. I am going to patch
the code now. ;)
James Ang
Webmaster, TekBay.com
[EMAIL PROTECTED]
----- Original Message -----
From: "James Ang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 25, 2001 11:57 AM
Subject: Re: [cf-xml] SOXML and iSyndicate
It is very specific to iSyndicate's XML. I wanted to
write something that does not rely on MSXMLDOM (possible
memory leak issues which the sys.admin. here would harass
me over if it does happen ;) ).
Anyway, attached is the set of modules that do what I
said they are suppose to do. ;) Look into modules/makeWDDX.cfm
for the iSyndicate XML -> WDDX conversion. makeWDDX.cfm relies
on parseTag_newsfeed.cfm and parseTag_channel.cfm (probably
the naming of the submodules could be better ;)).
Any questions or comments are welcome. :)
James Ang
Webmaster, TekBay.com
[EMAIL PROTECTED]
----- Original Message -----
From: "tom dyson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 25, 2001 11:33 AM
Subject: Re: [cf-xml] SOXML and iSyndicate
Hi James
I'd be interested to see how you're doing step 2 (the XML -> WDDX part).
Could you post your code to the list?
Tom
on 25/7/01 4:06 pm, James Ang at [EMAIL PROTECTED] wrote:
> Dave,
>
> If you just want to get iSyndicate XML going for your site,
> I have just completed a set of modules to take care
> translating a given set of iSyndicate XML feeds to WDDX
> with a data structure that looks like:
>
> Root (struct)
> -> newsfeed[] (array of structs)
> -> channel[] (array of structs)
> -> cid (string) (e.g. cnbc.40_market.hl)
> -> date (string) (e.g. 07/10/2001)
> -> time (string) (e.g. 08:01 PST)
> -> title (string) (e.g. CNBC.com: Market Stories)
> -> headline[] (array of structs)
> -> date (string) (e.g. Tue, July 10, 2001 08:01 AM)
> -> time (string) (e.g. 08:01 PST)
> -> title (string) (e.g. Debate rages on IT spending and productivity)
> -> href (string) (a URI)
>
> (I am working on TekBay specific WDDX->HTML portion now. :))
>
> Obviously, this isn't a general solution like soXML or xmlquery.
> This only works for iSyndicate. :)
>
> I batch process TekBay's iSyndicate XML feed with a 3 stage process:
> 1) Get XML via CFHTTP
> 2) Convert XML to WDDX (no datatype conversion here)
> 3) Convert WDDX to HTML
>
> I can provide code for 1) & 2) and skeleton code that traverses
> the deserialized WDDX structure for 3). Let me know if you are
> interested.
>
> You can reach me via:
>
> MSN: [EMAIL PROTECTED]
> ICQ: 28917887 (require auth.)
> Email: [EMAIL PROTECTED]
>
> James Ang
> Webmaster, TekBay.com
> [EMAIL PROTECTED]
-----------------------+
cf-xml mailing list
[EMAIL PROTECTED]
http://torchbox.com/xml
-----------------------+
cf-xml mailing list
[EMAIL PROTECTED]
http://torchbox.com/xml
-----------------------+
cf-xml mailing list
[EMAIL PROTECTED]
http://torchbox.com/xml
