http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-04-28T14:11:14ZTYPO3 ForgeTYPO3 Core - Bug #91218: Same name of a xlf/xml file can break the frontendhttp://forge.typo3.org/issues/91218?journal_id=4241952020-04-28T14:11:14ZGeorg Ringer
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul> TYPO3 Core - Bug #91218: Same name of a xlf/xml file can break the frontendhttp://forge.typo3.org/issues/91218?journal_id=4241962020-04-28T14:12:17ZJosef Glatzjosef.glatz@typo3.org
<ul><li><strong>Assignee</strong> set to <i>Josef Glatz</i></li></ul><p>I have to answer some questions myself. Please ignore this issue until then^^</p> TYPO3 Core - Bug #91218: Same name of a xlf/xml file can break the frontendhttp://forge.typo3.org/issues/91218?journal_id=4336112020-10-20T23:02:53ZGeorg Ringer
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Rejected</i></li></ul><p>I am closing this issue because there is no way during rendering to know if an empty string from translation is valid or not. if this is important to an integrator/dev, the <code>default</code> argument needs to be used.</p>
<p>feel free to discuss on slack if still relevant to you</p> TYPO3 Core - Bug #91218: Same name of a xlf/xml file can break the frontendhttp://forge.typo3.org/issues/91218?journal_id=4336272020-10-21T08:34:58ZJosef Glatzjosef.glatz@typo3.org
<ul></ul><p>For reference: it's ok to reject, since only XLF is supported with TYPO3 11</p>