ezsystems/ezoe — comment on commit afeb4e90f37a883d8266bbf030d005a61007e43d
File:  line 0
By pkamps:

Actually, I don't care so much how you store &_nbsp; in the DB. I just thought &_#160; would be the easiest and most stable way.

We run into a backward compatibility issue after upgrading from 4.2 to 4.5. The ezxml attribute now stores (and does not replace them). It's causing problems in our custom templates that build an XML nitf document (for a content syndication with amazon). But that's ok -- it's custom code... so I do have to expect some broken things after an upgrade.

It would not have been an issue if ezp would use &_#160; to represent a non-breaking-space. That's why I'm suggesting it - but I'm not aware of other potential problems an &_#160; would cause (as you say in your post). BTW, can you give us some details about that?