Locales are stupid
#6885 (In Topic #1815)
You'd expect it to output Iibool(true).
However, if the Turkish locale is actually installed on a server, you get ��bool(false).
This is because the basic letters 'i' and 'I' don't have the same case conversion in Turkish, and everything is following locale rules.
I'm trying to deal with most of this in v11. It seems a small issue, because you can just turn off case conversion locales for Turkish and nobody is going to really be bothered, case conversion is almost entirely used for coding logic rather than display logic.
However, the real kicker is that locale settings are implemented on a per-process level, and if anyone has PHP installed via the Apache module rather than CGI, any other parallel running request on the server may change the locale during your request and screw it up. Imagine you're on a shared server alongside a Turkish website.
For this reason, the Health Check system in v11 is going to give a warning if a server is using the PHP Apache module.
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
1 guest and 0 members have just viewed this.