Jump to content

Search the Community

Showing results for tags 'utf8'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. MySQL's utf8 encoding can only represent a tiny (though useful) subset of the full 31-bit range of Unicode; it's not UTF-8 at all. To fix what never should've been broken, they came up with utf8mb4. It's "of course" (i.e. UTF-8 is some properly designed piece of stuff) upwards compatible with the broken utf8 type. Well, not exactly, but more on that later. Would it be possible to default to the real UTF-8 type, when available? (MySQL 5.5.3+) (even wp did it! nudge nudge) And here comes that "later" you've all been waiting for. This important(ish) change would require the noble sacrifice of cutting some of the core (YES, CORE!) fields down to 250 characters to satisfy MySQL's sad-pathetic-deplorable limitation on index sizes. I know, that's 5 precious characters lost, but think about all those suffering emojis and suddenly you'll feel all fuzzy and warm, right? Anw, just a suggestion, because i18n and l10n and all the like. Edit: It seems a cruel RFC took away much of UTF-8's expressive beauty, and it is now valid only up to 4-byte lengths and values of 0x10FFFF, whichever smaller; I'm gonna go and cry myself to sleep now, goodbye.
  2. Hi, I have had some (more) trouble to get started with PW :-( In my php.ini the default_charset was set to 'ISO-88591' or something similar. So, as the DB uses utf8 and the pages are delivered in utf8, php is required to use it too. If not you can run into errors when try to save strings with e.g. german umlaute: äöü ÄÖÜ Incorrect string value: '\xFCchte ...' for column 'data' at row 1 I'm not sure if this was checked with the install routine, but I have seen only green lines Maybe this could be done to avoid some hassle to users with a setup other than utf8. Or it maybe an option to add "ini_set('default_charset','utf8');" somewhere at the top of index.php, and to be very very sure (also for paranoics like me ) one can set and check it: ini_set('default_charset','utf8'); $php_use_utf8 = strtolower(trim(ini_get('default_charset')))=='utf8' ? true : false; Ok, now I can start try out that wonderful CMS
×
×
  • Create New...