Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information about t3:id in XLIFF language files #1094

Closed
sypets opened this issue Nov 13, 2020 · 1 comment
Closed

Add information about t3:id in XLIFF language files #1094

sypets opened this issue Nov 13, 2020 · 1 comment

Comments

@sypets
Copy link
Contributor

sypets commented Nov 13, 2020

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:

  • 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?

Information from Slack:

Concerns core development:

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.

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.

@linawolf
Copy link
Member

@sypets can you make a PR about that? There seems to be almost all information in your issue here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants