Martijn van der Ven

For completion, I should have probably included this in the previous run output: ``` php --version PHP 7.4.4 (cli) (built: Mar 19 2020 20:12:27) ( NTS ) ``` Installed through...

PHPStorm could be running in an entirely different environent. Maybe it isn’t spinning up a login shell, maybe there is no shell at all, or maybe it is configuring its...

While I think [we will not use it](http://forum.camendesign.com/for_programmers_cleaning_up_user_display_names+1#5j32rfk6gz0l), posting this for completion sake: previously we discussed taking an example of [IDN blacklisting](http://forum.camendesign.com/for_programmers_cleaning_up_user_display_names+1#6c03i1fvzvl1), Mozilla compiled a blacklist of sorts with 107...

Although it is available [from PHP 4.0.6 onward](http://php.net/manual/en/function.mb-internal-encoding.php), it has [never actually been enabled by default](http://php.net/manual/en/mbstring.installation.php): > mbstring is a non-default extension. This means it is not enabled by default....

See [this Stack Overflow question on validating UTF-8](http://stackoverflow.com/a/1523574). Clear options: 1. the [regex by the W3C](http://www.w3.org/International/questions/qa-forms-utf-8.en.php) Internationalization department: ``` perl $string =~ m/\A( [\x09\x0A\x0D\x20-\x7E] # ASCII | [\xC2-\xDF][\x80-\xBF] # non-overlong...

And then there is the Web Application Component Toolkit wiki on [internationalization](http://www.phpwact.org/php/i18n). More specifically: 1. [Checking UTF-8 for Well Formedness](http://www.phpwact.org/php/i18n/charsets#checking_utf-8_for_well_formedness), this has some detail on stuff and mentioned `iconv()` again...

Adding this here, seems to contain stuff that needs to be read but haven’t gotten around to it yet: [UTR #36: Unicode Security Considerations](http://www.unicode.org/reports/tr36/).

Just adding a note that this extends to 403 Forbidden pages.

I am probably over-thinking things, but this might be an idea: ``` php $hash = substr(preg_replace('/=+$/', '', base64_encode(md5($name, true))), 6, 10); ``` Base64 encoded data is easy on the eye...

I was wondering if this should be moved to DOMTemplate? Also wondering if a possible solution might be a jQuery like `.html(function(){})`. This would allow to change the element’s content...