Two issues: 1. Exports for Outlook ============ Gmail seems to have inserted "160 asCharacter" in a few places in a gmail contact csv export, so for example this partial phone number: '(914) 469-' is written to file as: #[40 57 49 52 41 160 52 54 57 45] And then "aFile readStream contents" signals "ZnInvalidUTF8: Invalid utf8 input detected" when it encounters the 160
2. Google csv Exports ============ The file starts with the BOM #[255 254], which generates the same exception ============= Are these problems with gmail or Pharo? Thanks ----- Cheers, Sean -- View this message in context: http://forum.world.st/Gmail-Contact-Export-and-readStream-tp4759306.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
