Task #105647
Updated by Xavier Perseguers about 23 hours ago
According to https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Localization/XliffFormat.html, a @trans-unit@ node is supposed to have both `id` and `resname` attributes, with the same "key".
From my point of view this is totally useless as I work with XLIFF since TYPO3 4.6 and never did it for my own extensions.
Possible argument is that it's needed for (some) web tool showing that context for the translator.
With Pootle, back then, it was not required.
With Crowdin, it's not required. Proof is with EXT:image_autoresize where I don't have such definitions:
<pre>
<trans-unit id="saveConfiguration">
<source>Save configuration</source>
</trans-unit>
</pre>
(source: https://github.com/xperseguers/t3ext-image_autoresize/blob/master/Resources/Private/Language/locallang.xlf#L6-L8)
and there's no problem seeing that context on Crowdin (https://crowdin.com/editor/typo3-extension-imageautoresiz/7511/en-fr?view=comfortable&filter=basic&value=3):
!clipboard-202411201108-xfbqa.png!
h2. Suggestion
- Core should not have to worry about tools we don't use ourselves (such as Weblate as I was said it was required there)
- Official contribution documentation should not take care of this either
- I would suggest to get rid of all @resname@ attributes for the sake of removing unneeded complexity and possible mismatch when working with Core XLIFF files