#2515 - Drop non-utf8 (non-unicode) support This is a spacer post for a website comment topic. The content this topic relates to: #2515 - Drop non-utf8 (non-unicode) support By Guest posted 26th Apr 2016, 9:48 AM Do not fill this field in. The performance impact might be just like 0.2% or something. But if we do as a principle remove 100 useless things that each are 0.2% that's 20%, so it's a policy of simplicity as much as anything else. By Guest posted 26th Apr 2016, 9:53 AM We could also drop this from HTML_HEAD.tpl: <meta http-equiv="Content-Type" content="text/html; charset={$CHARSET*}" /> By Guest posted 26th Apr 2016, 3:40 PM Discussion on http://compo.sr/forum/topicview/browse/deploying/dropping-non-utf8.htm By Guest posted 2nd May 2016, 8:51 PM If we drop UTF8 we can drop some of the textcode symbols that Comcode supports, like the way to write a euro symbol in ISO-8859-1. By Guest posted 30th Jul 2016, 11:13 AM If we assume UTF-8 we can drop Comcode symbol shortcut syntax... $shortcuts = array('(EUR-)' => '€', '{f.}' => 'ƒ', '-|-' => '†', '=|=' => '‡', '{%o}' => '‰', '{~S}' => 'Š', '{~Z}' => 'Ž', '(TM)' => '™', '{~s}' => 'š', '{~z}' => 'ž', '{.Y.}' => 'Ÿ', '(c)' => '©', '(r)' => '®', '---' => '—', '-->' => '→', '<--' => '←', '--' => '–', '...' => '…'); By Guest posted 19th Oct 2016, 12:08 PM We'll keep the non-utf-8 support for now, but it'll be added as non-maintained in the maintenance system. Some people may be integrating with legacy systems where iso-8859-1 is baked really deep into the content being managed. Maybe it can be dropped in 20 years ;-). 0 guests and 0 members have recently viewed this. Sort: Relevance Newest first Oldest first Rating Popularity
<meta http-equiv="Content-Type" content="text/html; charset={$CHARSET*}" />
$shortcuts = array('(EUR-)' => '€', '{f.}' => 'ƒ', '-|-' => '†', '=|=' => '‡', '{%o}' => '‰', '{~S}' => 'Š', '{~Z}' => 'Ž', '(TM)' => '™', '{~s}' => 'š', '{~z}' => 'ž', '{.Y.}' => 'Ÿ', '(c)' => '©', '(r)' => '®', '---' => '—', '-->' => '→', '<--' => '←', '--' => '–', '...' => '…');
Some people may be integrating with legacy systems where iso-8859-1 is baked really deep into the content being managed.
Maybe it can be dropped in 20 years ;-).