TYPO3 Core

Source Path JS validation contains a few problems and a major bug:

- if using regex the validation destroys an entered regex (removes for example questionmarks and asterisks)
- manually transforming special characters to their translit equivalent is implemented on our own instead of using a library (will currently only work with German umlauts)

Ideally we would have
- client and server side validation working the same way
- validation has to differentiate between regex and non-regex mode
- in case translit behaviour is wanted we should use a library --> but in general why should we change users path segments in that way, having umlauts / a lot of special chars in an url might be totally valid