http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-07-16T07:08:27ZTYPO3 ForgeTYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=1735932013-07-16T07:08:27ZGeorg Ringer
<ul></ul><p>this is possible by just adding the full path<br /><pre>
<f:translate key="LLL:EXT:fo/Resources/Private/Language/locallang_fo.xml:bar" />
</pre></p>
<p>however take a look at how the core handles translations using the translation server and the related files in typo3conf/l10n/. those are splitted by language and should be smaller and better to handle.</p>
<p>that ok for you?</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=1736802013-07-16T18:32:05ZChristoph Gross
<ul></ul><p>Adding the full path is an option but really blows up the template, I would like to avoid that.</p>
<p>In the current project, I have some validation errors, some countrynames, some productrelated translation, ... that need translation.<br />The locallang.xlf gets really long and I would prefer a way to divide this nicely by domain.</p>
<p>Would changing this behaviour interfere with the translation server? If yes, then the effort for changing might not be relation to the benefit. If not, I would really like to see this feature and help to implement it if someone could give me some directions.</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=1755252013-07-30T02:21:53ZPhilipp Gampephilipp.gampe@typo3.org
<ul></ul><p>Well, that would require some kind of configuration.</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=2309012014-09-24T10:45:37ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/230901/diff?detail_id=196416">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>Hi,</p>
<p>was this issue fixed or does it still exists?</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=2310082014-09-24T14:52:29ZChristoph Gross
<ul></ul><p>As far as I know it still exists. There is no way to use multiple localization files without specifying them explicitly like this:<br /><pre>
<f:translate key="LLL:EXT:fo/Resources/Private/Language/locallang_fo.xml:bar" />
</pre></p>
<p>It would be nice to split up the translation by model or some other means. Internally those files would need to be merged in one big locallang.xfl.</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=2310172014-09-24T16:21:07ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Project</strong> changed from <i>534</i> to <i>TYPO3 Core</i></li><li><strong>Category</strong> set to <i>Extbase</i></li><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul><p>This sounds more for fluid, but I let it as extbase feature request</p> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=3397242017-09-07T22:38:00ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Category</strong> changed from <i>Extbase</i> to <i>Extbase + l10n</i></li></ul> TYPO3 Core - Feature #49984: Distribute localization over multiple .xlf files (atm only locallang.xlf)http://forge.typo3.org/issues/49984?journal_id=4071322019-10-03T04:52:11ZGeorg Ringer
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>I would like to reject this feature request because we try to have less magic in the core. This feature will increase the magic factor as suddenly strings of some files (which ones) can be retrieved from a different file.</p>
<p>I propose to create a custom VH which extends the translation VH and then you can build up any string by yourself, e.g.</p>
<p><code><fo:translate key="title" type="model" /></code></p>
<p>since version 9 you can even overload the namespaces of VH so that you could use the <code><f:translate /></code> for that as well.</p>