Nested field types breaks parsing #5
Description
Just an FYI that nested fields breaks parsing and you end up with paragraph blocks containing raw RTF. Part of the issue is that when inside a field and hitting a double quote ("), all subsequent chars are parsed as content until the next double quote. The RTF I'm seeing has new blocks inside this content area ({ }) which are nested fields. So the { and } chars need to be handled in the reading of field result content. Adding these doesn't really fix the issue (although it's much closer) and logic around nesting would need to be added. I wasn't able to decipher the code enough to figure this out and ended up with a different external solution.