- Issue created by @berdir
- Status changed to Needs work
about 1 year ago 2:33pm 30 August 2023 - 🇨🇭Switzerland berdir Switzerland
Pushed some changes to an MR that seems to work in some basic tests.
One thing I'm uncertain about is file names. I have confirmation that there is currently no way to send any metadata about files, so I'm including the job item, file and data item key as prefixes in the name. Plus I'm applying the same cleaning as the job label to the file name, so it's changed anyway. Since I've only tested with an XTM test environment and manually generated/reuploaded files, I'm not sure how file names will look like for real translations, in my case, they are identical to the one I provided, so for now, I opted to just prefix the source filename with the language code.
However, since those tend to be visible when downloading, I assume the expectation is that they are also translated. Maybe an option within TMGMT that allows to send the filename as a separate translatable text?
- Status changed to Needs review
about 1 year ago 2:18pm 6 October 2023 - 🇨🇭Switzerland berdir Switzerland
This has been updated to work with the latest and now committed version of the TMGMT API.
Filenames have been discussed and instead of a prefix, the language code is now added as a suffix. Future additions are possible in the future, likely without the need to customize the integration in integration modules like this.
- First commit to issue fork.
-
wkozlowski →
committed d189dff3 on 8.x-6.x authored by
berdir →
Issue #3384292: Support file translations
-
wkozlowski →
committed d189dff3 on 8.x-6.x authored by
berdir →
-
wkozlowski →
committed d189dff3 on XCN-11169-Deprecated-functions authored by
berdir →
Issue #3384292: Support file translations
-
wkozlowski →
committed d189dff3 on XCN-11169-Deprecated-functions authored by
berdir →