# What is \<TX\_DOT\> and why is it added to my resource string key?

**URL:** https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310
**Category:** Developers
**Tags:** api
**Created:** [March 1, 2023, 4:13am UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310 "2023-03-01T04:13:18Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Kyle\_Tilman](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/kyle_tilman/32/2554_2.png) [@Kyle\_Tilman](https://community.transifex.com/u/Kyle_Tilman)
#### Post date: [March 1, 2023, 4:13am UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310/1 "2023-03-01T04:13:18Z")

</div>

I’m using the [[File Upload](https://developers.transifex.com/reference/post_resource-strings-async-uploads#section/File-Uploads)] API to upload a new translation file. My yaml file has keys with `.` delimiters. When uploaded to the project/resource, Transifex has changed the `.` to `<TX_DOT>`. This change remains when pulling the translated data down later. This is a new behavior as far as I can tell. Do I need to just replace that character on my side or is this a mistake I’m making?

---

<div class="post-metadata">

### Author: ![Cesar\_Garcia](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/cesar_garcia/32/1745_2.png) [@Cesar\_Garcia](https://community.transifex.com/u/Cesar_Garcia)
#### Post date: [March 1, 2023, 9:04pm UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310/2 "2023-03-01T21:04:03Z")

</div>

Hello!,

Thanks for reaching out to Transifex support.

Yes!, This is expected, and this is why. Let’s say you have the following structure in the YAML file :

_ **en:** _

_ **web-forms:** _

_ **design-elements:** _

_ **meta-preheader: Hey There!** _

Our logic is to separate each key level with “ **.** ” so with the above, you will get the following key: “ **web-forms.design-elements.meta-preheader** ”, Now let’s say you decide to use a dot instead of a dash; the result will be something like this: **“web-forms.design-elements.meta\<TX\_DOT\>preheader”**

![](https://downloads.intercomcdn.com/i/o/682350545/1472f11711a33d9d13a9d4ca/image.png)

We understand this is not expected by you and we apologize for the inconvenience, but we needed to implement a way to preserve our logic, so, I’m afraid you must implement a way to change the key or to map this values on a little script outside Transifex.

Let me know if you have any further questions, once again, I. apologize for the inconvenience

**Cesar Alberto Garcia Vazquez |** Customer Success Engineer

---

<div class="post-metadata">

### Author: ![Kyle\_Tilman](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/kyle_tilman/32/2554_2.png) [@Kyle\_Tilman](https://community.transifex.com/u/Kyle_Tilman)
#### Post date: [March 2, 2023, 1:46am UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310/3 "2023-03-02T01:46:10Z")

</div>

> [@Kyle\_Tilman](#):
>
> I’m using the [[File Upload](https://developers.transifex.com/reference/post_resource-strings-async-uploads#section/File-Uploads)] API to upload a new translation file. My yaml file has keys with `.` delimiters.

Ok. So it seems i need to change the uploads that i’m using to break on the dot and send a nested object instead of compound keys.

---

<div class="post-metadata">

### Author: ![Cesar\_Garcia](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/cesar_garcia/32/1745_2.png) [@Cesar\_Garcia](https://community.transifex.com/u/Cesar_Garcia)
#### Post date: [March 2, 2023, 3:10pm UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310/4 "2023-03-02T15:10:41Z")

</div>

Hello,

Yes, You could split your key and avoid having dots in it, the output will be something like this:

![](https://downloads.intercomcdn.com/i/o/682905370/de8288de1deedf24e36ba214/image.png)

File:  
en:

meta:

preheader: Hey There!

String = Hey There!

Key = en.meta.preheader

Let me know if you have any further questions.

Best Regards

---

<div class="post-metadata">

### Author: ![benis\_froms](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/benis_froms/32/3000_2.png) [@benis\_froms](https://community.transifex.com/u/benis_froms)
#### Post date: [April 13, 2024, 7:55pm UTC](https://community.transifex.com/t/what-is-tx-dot-and-why-is-it-added-to-my-resource-string-key/3310/5 "2024-04-13T19:55:42Z")

</div>

To address this, you have two options:

Replace \<TX\_DOT\> with a dot on your side after pulling the translated data. [Autodesk AutoCAD LT 2017 deals](https://procadis.com/version/autodesk-autocad-lt-2017/).  
Change your upload process to avoid using dots in keys. You could split your key and send a nested object instead of compound keys