Identify non translated parts of TYPO3 Core

[georgringer]

Which parts of TYPO3 core are not yet translated. There should be no string hardcoded in english anymore.

• Administration area / Install Tool
• Some errors in DataHandler?
• What about title + description in ext_emconf.php?
• ...

[IndyIndyIndy]

Related issues:
https://forge.typo3.org/issues/87091
https://forge.typo3.org/issues/87092
https://forge.typo3.org/issues/17274

[liayn]

I'm really not sure if this goal is reachable. There will always be a case where we have no translations at hand. Think of exception messages thrown early in bootstrap.

[georgringer]

it is fine to have something like exceptions not translated but my goal is that a non-english person can use TYPO3 as admin

[IndyIndyIndy]

Do we need to translate exceptions? I think they should, just like source code, stay english only. Translated exceptions messages would make it much more difficult, to search for related problems in issue trackers, google, etc.

[georgringer]

see above, exceptions are fine in english but an editor/integrator should never see an exception anyway

[IndyIndyIndy]

Found another one:
https://forge.typo3.org/issues/68371

Apparently in some parts of the RTE (Linkbuilder), some texts are english only.

[IndyIndyIndy]

Also, the default "Translate to" message is always english:
TCEMAIN.translateToMessage = Translate to %s:

Of course this text can be overriden in tsconfig, but maybe this can use the configured backend language as well.

[IndyIndyIndy]

Another weird localization part that should be streamlined:
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/backend/Classes/Clipboard/Clipboard.php#L716

[IndyIndyIndy]

BackendUserAuthentication.php has many errors that are not translated yet. Like:
"ERROR: Language was not allowed."
"ERROR: Record could not be fetched."

etc.