Adding or removing a line in source XML offset all translations

Hi!
I want to use Crowdin to translate our project and I’m currently testing it, but I can’t understand how we should format our XML.
We have something like this:

<MyGUI>
	<Tag name="zero"><translation>zero</translation></Tag>
	<Tag name="one"><translation>un</translation></Tag>
	<Tag name="two"><translation>deux</translation></Tag>
	<Tag name="three"><translation>trois</translation></Tag>
</MyGUI>

And we want to only translate the translation part.
It works great, but if I remove the 1st line, or add a new line in the source XML and update the source, every existing translation is offset by one line:
deux will be trois etc.

Is there something I don’t understand?

Thanks,
Adrien

Hi @suny2000!

As we assume, you update your existing source file with the translation file. So your source strings get overwritten with translations

If you want to upload existing translations, you need to do that via Dashboard > open needed language > three dots near needed file > upload translations:

Thanks a lot for your quick answer!

But actually, I don’t want to upload existing translations (My example was misleading).
I have a key and a text, and I want to translate the text.
A simpler example:

<?xml version="1.0" encoding="UTF-8"?>
<MyGUI>
	<Tag name="key1">one</Tag>
	<Tag name="key2">two</Tag>
	<Tag name="key3">three</Tag>
	<Tag name="key4">four</Tag>
</MyGUI>

I can translate one, two (with un, deux…).

But if I update the source file with

<?xml version="1.0" encoding="UTF-8"?>
<MyGUI>
        <Tag name="key0">zero</Tag>
	<Tag name="key1">one</Tag>
	<Tag name="key2">two</Tag>
	<Tag name="key3">three</Tag>
	<Tag name="key4">four</Tag>
</MyGUI>

Adding the line with key offset all the translations: translations are not bound to the right key anymore.

I must miss something obvious, sorry about my questions :confused:

A.

Dear @suny2000 , no need to be sorry :slightly_smiling_face:
Seems like you’re adding a new key and the string before the old ones. We’d suggest adding new strings after the old ones, then you won’t encounter shifting of strings