map ft-content bodyxml nodes to content-tree nodes

[chee]

previously we were only mapping <content/> nodes. which, arjun explains, is only what they are called before publishing. in the live bodyXML they are called <ft-content/>

[adgad]

We call them <content> when we publish (for some reason?!) and then when it comes out of the other end it somehow gets turned into <ft-content>

I didn't think it should ever be <content> out of api.ft.com? unless maybe we're using it inside <experimental> anywhere....

[chee]

We call them <content> when we publish (for some reason?!) and then when it comes out of the other end it somehow gets turned into <ft-content>

I didn't think it should ever be <content> out of api.ft.com? unless maybe we're using it inside <experimental> anywhere....

ahh, thanky ou

[epavlova]

We probably don't need to have ft-content node in the content tree. This is actually happening in the C&M world for some reason. This will probably go in the future logic to transform a tree to body XML.

[chee]

We probably don't need to have ft-content node in the content tree. This is actually happening in the C&M world for some reason. This will probably go in the future logic to transform a tree to body XML.

ah, i think my title is probably confusing. this is only allowing the ft-content bodyxml nodes to be mapped to the correct content-tree node, i'll update the title to be more clear