# Bug in XLIFF download of plurals

**URL:** <https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270>\
**Category:** Q&A\
**Created:** [February 1, 2023, 10:09am UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270 "2023-02-01T10:09:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![eboth](https://avatars.discourse-cdn.com/v4/letter/e/c67d28/32.png) [@eboth](https://community.transifex.com/u/eboth)\
**Post date:** [February 1, 2023, 10:09am UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/1 "2023-02-01T10:09:35Z")

</div>

When downloading an XLIFF file (whether via UI or API), the plural forms contain the singular source text (the translation, where it exists, is correctly in the plural). This appears to happen in some files, but not others.

As a workaround until this bug is fixed, the `pluralized:yes` filter can be used to doublecheck these strings in the UI.

---

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [February 8, 2023, 8:10pm UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/2 "2023-02-08T20:10:19Z")

</div>

Hello, this is Sandy from the Transifex support team. To investigate this further, can you please share with me the URLs of two resources? For the first resource, please share one where you see this issue, and the second should be a resource where you do not see this issue. Many thanks in advance for considering my request.

---

<div class="post-metadata">

**Author:** ![eboth](https://avatars.discourse-cdn.com/v4/letter/e/c67d28/32.png) [@eboth](https://community.transifex.com/u/eboth)\
**Post date:** [February 9, 2023, 11:20am UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/3 "2023-02-09T11:20:10Z")

</div>

Hello Sandy,

Thanks for getting back to me. Here is the only resource where I have observed this problem so far (with the offending string selected; in this string, the singular source is exported twice):  
[https://www.transifex.com/meganz-1/desktop-en\_nz/translate/#de/translationsourcets/441950362?q=key%3AWe're+text%3A’backing+up+your+folder.+The+time+this+takes+depends+on+the+files+in+this+folder](https://www.transifex.com/meganz-1/desktop-en_nz/translate/#de/translationsourcets/441950362?q=key%3AWe're+text%3A'backing+up+your+folder.+The+time+this+takes+depends+on+the+files+in+this+folder).’

And here is one of many resources that work fine:  
[https://www.transifex.com/meganz-1/android-40/translate/#de/strings?q=key%3Aphotos\_album\_delete\_confirmation\_description](https://www.transifex.com/meganz-1/android-40/translate/#de/strings?q=key%3Aphotos_album_delete_confirmation_description)

Let me know if you need anything else.

Kind regards,  
Endre

---

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [February 10, 2023, 9:54pm UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/4 "2023-02-10T21:54:30Z")

</div>

Hello, thank you for your reply; I reviewed your files and found what is happening; the issue is specifically on .ts source files.

Here is an example of a .ts file:

[![](https://downloads.intercomcdn.com/i/o/670287795/fc3fd83ae6545d5d969024da/Screenshot+2023-02-10+at+14.58.36.png)](https://downloads.intercomcdn.com/i/o/670287795/fc3fd83ae6545d5d969024da/Screenshot+2023-02-10+at+14.58.36.png)

As you can see, the source is a single string ("You have %n new video(s) "), whether the translation contains plurals or not. Source pluralized strings are in “numerusform” tags; the first one (“You have %n new video”) is for “single”, and the second one (“You have %n new videos”) is for “other”.

When the translation file is downloaded as an XLIFF file, the content looks like this (NOTE: singular and plural are dummy translations):

[![](https://downloads.intercomcdn.com/i/o/670297132/15a2b8ea333213a6a26a6b4c/Screenshot+2023-02-10+at+15.19.39.png)](https://downloads.intercomcdn.com/i/o/670297132/15a2b8ea333213a6a26a6b4c/Screenshot+2023-02-10+at+15.19.39.png)

As you can see, the source elements (in both trans unit elements 4[0] and 4[1]) in the XLIFF file are filled with the source element ("You have %n new video(s) ") from the .ts file; in theory, this behavior is correct.

To have the XLIFF file the way you want (this is also the way it makes sense, in my opinion), source elements in the XLIFF file should be filled with “numerusform” elements from .ts file, “You have %n new video” should be the source of trans-unit id=“4[0]”, and “You have %n new videos” should be the source of trans-unit id=“4[1]”. Something like in the image below:  
 ![Screenshot 2023-02-10 at 15.51.42](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/5/585275fe73f62a7f4146a7d907f30aa99aa2de33.png)

I communicated this to our engineering team to identify if this is a bug or expected behavior; I’ll keep you posted as soon as I receive information about this matter, many thanks for bringing this to us.

---

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [February 13, 2023, 8:32pm UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/5 "2023-02-13T20:32:55Z")

</div>

Hello, This situation was registered as a bug; our product team will work on having this fixed as soon as possible; I’m sorry for the inconvenience this issue caused you. I’ll be following this issue closely, and I’ll let you know when it is fixed. Thank you for bringing this to us.

---

<div class="post-metadata">

**Author:** ![eboth](https://avatars.discourse-cdn.com/v4/letter/e/c67d28/32.png) [@eboth](https://community.transifex.com/u/eboth)\
**Post date:** [February 14, 2023, 8:32am UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/6 "2023-02-14T08:32:22Z")

</div>

Thanks for the update, Sandy, I greatly appreciate both the clear communication and the fact that the issue is being dealt with.

Kind regards,  
Endre

---

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [March 6, 2023, 5:15pm UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/7 "2023-03-06T17:15:54Z")

</div>

Hello Endre!

This issue was handled; please give it a try, download an xliff file, and see the file contains all the pluralized translations!

---

<div class="post-metadata">

**Author:** ![eboth](https://avatars.discourse-cdn.com/v4/letter/e/c67d28/32.png) [@eboth](https://community.transifex.com/u/eboth)\
**Post date:** [March 17, 2023, 10:51am UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/8 "2023-03-17T10:51:55Z")

</div>

Dear Sandy,

I confirm that the problem in ts files is solved – many thanks for your effective help!

Kind regards,  
Endre

---

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [March 22, 2023, 2:18pm UTC](https://community.transifex.com/t/bug-in-xliff-download-of-plurals/3270/9 "2023-03-22T14:18:03Z")

</div>

I’m glad to read this! Thanks for letting us know the fix was successful!

Regards,

Sandy
