Notices tagged with utf8
-
Roland Häder (roland)'s status on Tuesday, 11-Oct-2016 14:11:38 CEST Roland Häder @clacke with #UTF-8 (or in general #Unicode ) you can preserve any fonts that existed on this planet, from #Egyptian #hieroglyphics to #German #Runes and much more are preserved as long as one computer stores them. Very ultimate text format! :-) http://www.unicode.org -
Roland Häder (roland)'s status on Monday, 22-Aug-2016 12:01:15 CEST Roland Häder I have noticed that the #contact application in !owncloud has misinterpreted #UTF-8 encoded entries (like my family name #Häder) and has not fully decoded it. E.g. An "ü" ends up as "=C3=BC". -
Roland Häder (roland)'s status on Tuesday, 09-Feb-2016 19:07:25 CET Roland Häder @nds And full #UTF8 or #UTF16 support for URLs. Some websites test this with something like "&utf8=<check>" by <check> is a UTF-8 symbol (I don't know how to enter it here). -
lnxw48 (Linux Walt) (lnxw48)'s status on Monday, 16-Mar-2015 22:57:07 CET
lnxw48 (Linux Walt)
MySQL Character Encoding, Part 2
Gotchas and solutions to character encodings with MySQL databases
-
lnxw48 (Linux Walt) (lnxw48)'s status on Monday, 16-Mar-2015 22:54:58 CET
lnxw48 (Linux Walt)
MySQL Character Encoding, Part 1
Gotchas and solutions to character encodings with MySQL databases.
-
Roland Häder (roland)'s status on Tuesday, 03-Mar-2015 20:43:48 CET Roland Häder @blogrobatik Das ist kaputtes #UTF-8. @mmn Sometimes UTF-8 gets damaged, see @blogrobatik dent: http://gnusocial.blogrobatik.de/notice/3871 -
Roland Häder (roland)'s status on Saturday, 28-Feb-2015 23:24:50 CET Roland Häder @blogrobatik Ich nutze eine modifizierte Version von #rss2queet, das der @goebelmasse geschrieben hat. Ich habe das Script noch mit #UTF-8 (nicht ganz stabil) und #ATOM-Feed (derzeit recht stabil) -Support erweitert und hier auf meinem Blog gehostet: https://social.mxchange.org/file/rss2queet.py -
mmn (mmn)'s status on Sunday, 22-Feb-2015 21:26:52 CET mmn @pskosinski@quitter.no Regarding your #Unicode problems in !gnusocial at https://social.mxchange.org/url/28852 We have actually, in the current nightly branch, made the necessary changes to support UTF-8 properly. The problem is #MySQL encoding support ("utf8" != UTF-8) and limited indexing lengths in #InnoDB (making 191 characters the most when using 4 byte unicode characters). If one wants to support proper UTF-8 in #MySQL the tables and columns…