I had the chance to discuss and see this issue with and I confirmed that this happend because she was using a lookup field that was bringing an additional field of type people or groups and the "strange characters" were the standard SP way to identify a lookup value (using #).