Thanks guys for the hint. I'll clean that up. Thanks for the coding hint papeh, I'm still very much on a learning curve, and had looked for a solution like that but failed to find it. Steve, as for the need of a fix, that is the reason the bug was issued. How it came to be is a bit of a mystery, but if I had to guess, the git configuration on the build agent (TC?) for this library might not be set up to use system line endings, so that when this section of code was compiled, it only had the <LF> character instead of <CR><LF> that windows needs. Then when WeSay is run, the list that is displayed simply jams the words together instead of properly putting each word on a new line. So one solution might be to check the way that git for this project is set up, but if we can guarantee that each OS will get what it would like to see regardless of how the build agent's git is set up, then the users will be happy to have a nice consistent display across the board. When I get a chance, I'll resubmit with one of papeh's ideas.