Sorry to answer my own question, but I discovered that the source of my problem had to do with the browser response limiting the size of text nodes in xml-rpc calls. I found the following useful note here : Also important to note is that although the specifications say that no matter how much text exists between tags, it should all be in one text node, in practice this is not always the case. In Opera 7-9.2x and Mozilla/Netscape 6+, if the text is larger than a specific maximum size, it is split into multiple text nodes.
These text nodes will be next to each other in the childNodes collection of the parent element The response I was receiving to the browser had unknowingly split my text node into multiple text nodes. Heads up for anyone who has a similar issue.
Sorry to answer my own question, but I discovered that the source of my problem had to do with the browser response limiting the size of text nodes in xml-rpc calls. I found the following useful note here: "Also important to note is that although the specifications say that no matter how much text exists between tags, it should all be in one text node, in practice this is not always the case. In Opera 7-9.2x and Mozilla/Netscape 6+, if the text is larger than a specific maximum size, it is split into multiple text nodes.
These text nodes will be next to each other in the childNodes collection of the parent element. " The response I was receiving to the browser had unknowingly split my text node into multiple text nodes. Heads up for anyone who has a similar issue.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.