Denis Bisson 8e546180ce FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed. ... ADD: In the find file dialog, in the tab of plugins, the column of the unit was the only one with no caption. Added the name "Unit" to it. CHG: Replace the .lrt file of fsearchplugin by the newer .lrj file.		2018-11-17 04:44:05 +00:00
..
lcl	UPD: Chinese (Simplified) language files	2018-05-20 19:08:05 +00:00
doublecmd.be.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.bg.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.ca.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.cs.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.da.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.de.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.el.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.es.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.fr.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.hr.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.hu.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.it.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.ja.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.ko.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.nl.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.pl.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.pt.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.pt_BR.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.ro.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.ru.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.sk.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.sl.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.sr.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.sr@latin.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.tr.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.uk.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.zh_CN.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00
doublecmd.zh_TW.po	FIX: Right after invoking the find file dialog, when loading a search template with a WDX plugin content search, if the first field was of the type "FT_MULTIPLECHOICE", we were not disabling the combo box of the unit and so we were right after attempting to find a null string in the combo box of unit and so it was generating an annoying 'Unit "%s" not found!' error message. This has been fixed.	2018-11-17 04:44:05 +00:00