Sat, 05 Jul 2008 18:38:51 -0400 http://bugs.horde.org/ticket/2072 Word paste document When I cut and paste a Word text document into a new Horde email letter it looks fine. However, when it issent and received, all quotes, apostrophies and dashes(" ' - ) are turned into question marks (?) in the text. Thu, 02 Jun 2005 22:03:17 -0400 http://bugs.horde.org/ticket/2072#t8836 Word uses illegal characters. We can't really do much about it. Thu, 02 Jun 2005 22:11:40 -0400 http://bugs.horde.org/ticket/2072#t8837 Can't we convert the illegal characters using something like this code: http://shiflett.org/blog/2005/oct/convert-smart-quotes-with-php function convert_smart_quotes($string) { $search = array(chr(145), chr(146), chr(147), chr(148), chr(151)); $replace = array("'", "'", '"', '"', '-'); return str_replace($search, $replace, $string); } Mon, 17 Dec 2007 15:13:56 -0500 http://bugs.horde.org/ticket/2072#t39992 This won't help. It's a charset conversion problem. Mon, 17 Dec 2007 17:53:41 -0500 http://bugs.horde.org/ticket/2072#t39998 My source document is utf8. It's a plain text file. And the IMP UI is set to utf8. Why is character set conversion happening? Mon, 17 Dec 2007 18:09:39 -0500 http://bugs.horde.org/ticket/2072#t40002 Because you usually don't send messages in utf-8. If you choose utf-8 in the compose view, those characters are probably rendered fine at the recipient. Mon, 17 Dec 2007 18:23:02 -0500 http://bugs.horde.org/ticket/2072#t40005 Thanks. Changing the sending charset fixed the problem. Would it be crazy to check for character set conversion problems and warn the user before sending? Or make UTF-8 the default and downgrade to ISO-8859-1 when UTF-8 isn't needed? Mon, 17 Dec 2007 18:48:04 -0500 http://bugs.horde.org/ticket/2072#t40006 > Would it be > crazy to check for character set conversion problems and warn the > user before sending? This is not possible unfortunately. > Or make UTF-8 the default and downgrade to > ISO-8859-1 when UTF-8 isn't needed? No, that's not possible either. You can't determine which charset you might need from an utf-8 stream. Mon, 17 Dec 2007 18:59:49 -0500 http://bugs.horde.org/ticket/2072#t40009 pine/alpine has a function pith/send.c:set_charset_possibly_to_ascii(), which does exactly this. If no-non-ASCII characters are found, then convert text to ASCII. Mon, 17 Dec 2007 19:29:47 -0500 http://bugs.horde.org/ticket/2072#t40010 We do this already iirc. But only having the choice between utf-8 and ascii is not what we want to do. Mon, 17 Dec 2007 19:58:19 -0500 http://bugs.horde.org/ticket/2072#t40013 Agreed. But this seems useful though overly simplified... Wed, 19 Dec 2007 17:01:00 -0500 http://bugs.horde.org/ticket/2072#t40088 This seems just annoying to me, especially since if there's a non-printing char that isn't visible, the user will just be confused. I would be fine with running a smart-quotes-fixing function (we have the cleanascii text_filter routine already) if we're in ascii or iso-8859-1, but otherwise I think this goes back to being Not A Bug. Sun, 06 Jan 2008 20:03:26 -0500 http://bugs.horde.org/ticket/2072#t40816 I agree with Chuck. Wed, 16 Jan 2008 17:35:11 -0500 http://bugs.horde.org/ticket/2072#t41204 Maybe this should be opened as a new bug, but why does the user have to select a character set at all? Fat mail clients (including Mail.app and alpine) seem to detect the character set automatically (with the option to override). Don't we want that feature? Thu, 14 Feb 2008 01:43:20 -0500 http://bugs.horde.org/ticket/2072#t42327 Something like: $str = "שלום"; echo mb_detect_encoding($str, "ASCII, ISO-8859-15, ISO-8859-1, ISO-8859-2, KOI8-R, ISO-8859-7, ISO-8859-6, ISO-8859-8, ISO-2022-JP, BIG-5, EUC-KR, UTF-8") . "\n"; Thu, 14 Feb 2008 02:26:19 -0500 http://bugs.horde.org/ticket/2072#t42328 mbstring doesn't support all charsets that we do. Thu, 14 Feb 2008 05:13:49 -0500 http://bugs.horde.org/ticket/2072#t42331 What if we default to UTF-8 and downgrade to ASCII if we pass something similar to Data_ldif's _is_safe_string() check? The user always has the option to override this... Mon, 24 Mar 2008 01:54:23 -0400 http://bugs.horde.org/ticket/2072#t44165 UTF-8 is not a good default for email messages. Contrary to browsers, the UTF-8 support in email clients is still not that widespread yet, and the market is much more diverse too. Mon, 24 Mar 2008 08:49:09 -0400 http://bugs.horde.org/ticket/2072#t44168 Then what character set are you supposed to use when ASCII doesn't cut it? Can we ask the user to manually choose another character set if their message won't fit in ASCII, but they're using the default of ASCII? Dropping the extra characters silently is not user-friendly. Mon, 24 Mar 2008 14:26:43 -0400 http://bugs.horde.org/ticket/2072#t44170 Pasting word documents into email messages isn't friendly either. I think the best solution is to teach users. There is no golden way to handle this. At least until PHP or browsers provide a better way to reliably detect charsets. Mon, 24 Mar 2008 18:53:12 -0400 http://bugs.horde.org/ticket/2072#t44173