On Sun, May 2, 2021 at 1:45 PM Paul Higgs <[email protected]> wrote: > > I just created the following > ... > I will look into the libxml2 to see where the \n is being converted to a > <space>. > ....
Actually, your repro case is showing the correct behavior. In other words, the \n is NOT being converted to a space character. I created a comparable repro case using lxml.etree, and observed the correct behavior there, as well. So I dug a little further, and found that the second bug is actually in our own code. So, I am suitably embarrassed, and I apologize for the wild goose chase. Thank you both for helping to nudge me back onto the path of truth. :-) Regards, Bob -- Bob Kline https://www.rksystems.com mailto:[email protected] _______________________________________________ lxml - The Python XML Toolkit mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/lxml.python.org/ Member address: [email protected]
