[TYPO3-core] RFC: Fix (part of) #7589: FULLTEXT keys are not processed correctly

[Martin Kutschker]

Michael Stucki schrieb:
> Hi Martin,
> 
>> Michael Stucki schrieb:
>>> This will be essential for full UTF8
>>> support (which unfortunately did not make it into this version).
>> What is missing?
> 
> See my notes at http://bugs.typo3.org/view.php?id=6098
> 
> There are two different situations and I think it would maybe be ok to
> enable this for all new installations:
> 
> - enforce UTF8 usage (using these patches, uncomment the line that ignores
>   COLLATE fields)
> - block the Install Tool if client, connection & result charset are not UTF8
> 
> What do you think?

That there is no reason to force UTF-8 upon everyone. iso-8859-1 and 
other charsets are completely valid choices for some installations. The 
only thing I really would like to go (though it will break installations 
I know) is the multi-charset feature. That is, you're using eg English 
(iso-8859-1) and Polish (iso-8859-2) but do not use forceCharset (utf-8).

> - remove multiplyDBfieldSize from config_default.php (so the feature is
>   still available, but it can no longer be set for new installations)

Dmitry likes it to stay for some reasons. I forgot exactly why but it 
has - suprise - something to do with compatibility.

Masi