Open georgringer opened 5 years ago
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.
it is fine to have something like exceptions not translated but my goal is that a non-english person can use TYPO3 as admin
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.
see above, exceptions are fine in english but an editor/integrator should never see an exception anyway
Found another one: https://forge.typo3.org/issues/68371
Apparently in some parts of the RTE (Linkbuilder), some texts are english only.
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.
Another weird localization part that should be streamlined: https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/backend/Classes/Clipboard/Clipboard.php#L716
BackendUserAuthentication.php has many errors that are not translated yet. Like: "ERROR: Language was not allowed." "ERROR: Record could not be fetched."
etc.
Which parts of TYPO3 core are not yet translated. There should be no string hardcoded in english anymore.
ext_emconf.php
?