[Waiting for user feedback] Source language XLIFF File

Hi,

Yes, you can change the target language in an XLIFF file by modifying the `<target-language>` attribute and updating the `<target>` elements inside `<trans-unit>` sections. However, this may not work properly in WPML because WPML creates translation jobs based on language pairs. If a job for a specific language is missing, you might encounter an error message stating that the translation jobs do not exist.

You can do something like this:

- Use a text editor (e.g., Notepad++, VS Code, Sublime Text) or an XML editor.
- Locate the `<file>` element at the beginning of the file. It contains the `target-language` attribute.

For example:

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
    <file original="1-571e0f7e2d992e738adff8b1bd43a521" source-language="nl" target-language="en-US" datatype="plaintext">

If you want to change the target language from NL → EN (US) to NL → EN (GB), modify it:

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
    <file original="1-571e0f7e2d992e738adff8b1bd43a521" source-language="nl" target-language="en-GB" datatype="plaintext">

Furthermore, each `<trans-unit>` section contains a `<source>` and a `<target>` element. If needed, update the translations manually.

It looks something like this:

<trans-unit id="1">
    <source>Hallo</source>
    <target>Hello</target>
</trans-unit>

That being said, a more effective approach is to add custom languages and set up translation jobs. You can find detailed guidance in these resources: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/ https://wpml.org/documentation/translating-your-contents/#assigning-the-translations-to-a-translator.