You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
t3:id is an (optional?) property in the .xlf files. A timestamp (current time) can be used.
It is used to keep track of a file in case it is moved.
It should be used in the core (I think) and a script to check for uniqueness exists (Build/Scripts/xlfcheck.sh)?
Questions:
should this be used in extensions as well?
Is this still used? Is it used within the core? How so? Often the language files are referenced by path so how does this help? Or does it help to keep track of the connection between base file and translated file?
You may rename a translation file but must not split it into multiple files since we use the unique id to track move and renaming of translation files.
Every new language file must have a unique id (timestamp “now”) in the header that is not changed if the file is moved later on.
Add to page: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Internationalization/XliffFormat.html
t3:id is an (optional?) property in the .xlf files. A timestamp (current time) can be used.
It is used to keep track of a file in case it is moved.
It should be used in the core (I think) and a script to check for uniqueness exists (
Build/Scripts/xlfcheck.sh
)?Questions:
Information from Slack:
Concerns core development:
https://wiki.typo3.org/Development/Memos/TranslationHandling
check for uniqueness:
That file still exists in the core in
Build/Scripts/xlfcheck.sh
.As always, for some of this information, it should be checked if it is still up to date.
The text was updated successfully, but these errors were encountered: