Denise (![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
denise) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_dev_training2009-10-30 03:15 pm
denise) wrote in dw_dev_training2009-10-30 03:15 pm
best practice with the translation system
I've caught myself typing this out to people several times, so, into dw_dev_training it goes:
In general, if you're updating the value of a text string in a .text file or in en.dat, you need to change the name of the string.
The reason for this is -- in order to not undo the site copy team's hard work -- we don't allow updates from cvs to overwrite the existing text on the site, because then the 'old' values would overwrite the values that had been changed on the site. (This is because the translation system is horrible, horrible, horrible.)
So, if you've got:
.string.foo=Bar!
and you want to change it to:
.string.foo=Baz!
you would instead change it to:
.string.foo2=Baz!
and update the BML::ml calls to use the new string name.
dw_dev_training it goes:In general, if you're updating the value of a text string in a .text file or in en.dat, you need to change the name of the string.
The reason for this is -- in order to not undo the site copy team's hard work -- we don't allow updates from cvs to overwrite the existing text on the site, because then the 'old' values would overwrite the values that had been changed on the site. (This is because the translation system is horrible, horrible, horrible.)
So, if you've got:
.string.foo=Bar!
and you want to change it to:
.string.foo=Baz!
you would instead change it to:
.string.foo2=Baz!
and update the BML::ml calls to use the new string name.
no subject