Oh wait -- you're using Emplode 2.0 ... So I would think that the odds are that this is fixed in RMM/Emplode 3.0 since that would coincide with jEmplode 47's version.