> Is this a known issue, if so is it planned to be corrected? I believe that this was fixed early on in cvs after .16. If not, there is a patch sitting in my inbox to fix it (search the archives). -Chris