Closed (fixed)
Project:
Localization update
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2010 at 11:44 UTC
Updated:
25 Jun 2011 at 17:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
sutharsan commentedThis problem only occurs when Localization Update is installed on an existing site with existing translation and locally modified translation strings. Since Drupal core does not store any state of locally modified translation strings, the is no way to distinguish when L10n Update gets installed.
Localization Update has two Update modes:
* Translation updates replace existing ones, new ones are added
* Edited translations are kept, only default ones (previously imported) are overwritten and new translations are added
The latter is the default.
We could add a third option to only add new translations and not overwrite existing translations. This would be in line with the core Import option:
* Existing strings are kept, only new strings are added.
Comment #2
Thomas_Zahreddin commentedsounds good to me.
Comment #3
sutharsan commentedThis patch does adds an option: "All existing translations are kept, only new translations are added." Which is equal to the Locale option "Existing strings are kept, only new strings are added." and is the new default.
Comment #4
podarok#3 works for me
Yes, we do not need overwrite individual translations without user permission
ported to 7.x
Comment #5
gábor hojtsyHow did you make this the new default? Maybe I'm not seeing something there?
Comment #6
sutharsan commentedGit patch for 7.x with minor text change in the option.
@Gábor Hojtsy: maybe something went wrong with applying the cvs patch. The option is found at the usual (two) places.
Comment #7
sutharsan commentedCommitted to 7.x-1.x-dev.
Backported to 6.x-1.x-dev too.