[TYPO3-core] RFC #12661: Problem with german "Umlaute" in BE file list, no thumbs generated

[Jigal van Hemert]

Martin Kutschker wrote:
> Jigal van Hemert schrieb:
>> Yes, that would be better. I think that the locale settings for the
>>  entire backend will influence more than just the working of 
>> escapeshellarg. What will happen with settings for date and time 
>> formats, etc.?
> 
> IMHO the right thing for most languages, ie proper formatted dates.
> But I recall that Dmitry said that Debian locales for Baltic are
> broken.
> 
>> Anyway, this bug was introduced when esacpeshellarg was used
>> instead of wrapping the filename in double quotes. This is the
>> least disruptive way to solve it.
> 
> Could be, but I fear we still would need at least one configurable
> locale to make it work. I might have installed de_DE.utf-8 but not
> en_US.utf-8.

Taking this all into account, I propose:

- [SYS][systemlocale] (e.g. en_US, ENG, de_DE at euro, ...)
- if [BE][forceCharset] == utf-8 and [SYS][UTF8filesystem] == TRUE:
   add '.UTF-8' and '.UTF8' (Mac seems to dislike the dash) to the 
systemlocale
- use this locale for various settings.
- if [SYS][ddmmyy] or [SYS][hhmm] are set, use these for date/time formats.
- I suppose [SYS][USdateFormat] is used for parsing incoming dates?
- which setlocale categories should be set with or without the extra 
character set suffix?


Questions:
1. What is the best place to set a system locale to make sure it's used 
in as many scripts as possible?
2. How does Windows handle the locales with escapeshellarg() and other 
locale-dependent functions? Windows does not accept the .UTF* charset 
suffix in setlocale?
3. What about Oli's idea to use t3lib_stdGraphic::wrapFileName() also in 
thumbs.php (requiring the function to become static?) ?

Regards,
-- 
Jigal van Hemert.