GNOME Bugzilla – Bug 308276
Missing name in V-folder error message dialog
Last modified: 2013-09-13 00:52:46 UTC
Missing folder name in V-folder error message dialog. See attached picture for additional information.
Created attachment 47983 [details] There is a missing name of V-folder between double apostrophes ("")
still in 2.5.5. retargetting.
Still in 2.6.0. Any news?
retargetting.
Maybe you can fix that bug by editing line #290 in evolution/mail/mail.error.xml from "<_secondary xml:space="preserve">A folder named "{1}" already exists. Please use a different name.</_secondary>" to "<_secondary xml:space="preserve">A folder named "{0}" already exists. Please use a different name.</_secondary>". Language files should be updated too (maybe).
Oops, I gave a bad bug status, please change it to "in progress" or something like this, but not closed.
pavel: hmm, yeah. but why WONTFIX? :-)
hehe, okay :-)
Created attachment 71277 [details] [review] Fixed
ushveen: the patch is not clean, it also includes a second changelog entry. :-)
Created attachment 71343 [details] [review] thanx andre.resubmitting the patch.
while testing this bug and the patch (the patch works fine, by the way!), i ran into the following issue: go to edit > search folders. add a search folder with a name that already exists (here: "bla"). error message: Name "bla" already used Please choose another name. right-click on "Search folders" in the folder list pane, choose "create folder" (or "new folder" or whatever it is). add a folder name that already exists and once again click on the "search folders" folder list entry. after that you can select the sources and click OK. error message: Cannot add Search Folder "bla". A folder named "" already exists. Please use a different name. best way here, in my humble opinion, would be to enhance the patch by harmonizing the strings and to closely look at the code. i prefer the latter one, as it is easier for the user to understand what has gone wrong here. ushveen, can you update the patch so also the error messages get harmonized? thanks a lot. targetting to 2.9 as this will break the string freeze. guess i will investigate a bit into "similar error messages" and have moved this to a seperate bug report, namely bug 352358.
Committed to HEAD.