& and search and destroy and
@Pantagrueliste Can you clarify the parameters of this "search and destroy" campaign? Often, when there has been an & and combo, it is because the & is intended to be read as an "&cetera" followed by an "and".
These need to be assessed individually and carefully.
16 instances identified in TL. &cetera are written differently: &c find . -name '*.xml' -print0 | xargs -0 sed -i "" "s/\& and/\&/g"
Done: 16 changes in total.