[Bug-ddrescue] direct mode with AF disks, exit on slow, save mapfile interval, Russian translation

[Анонимный отправитель]

Hello again, Antonio and the developers team!
Using program (v 1.19 in LUBUNTU 16.04 - standard in repository), I've got some 
ideas:
1) Please, add an option to quit or, better, to pause the program or to 
reset/reinit/power_cycle the input hard drive when skipping slow areas.
If made to quit - I can use a shell script to pause and restart the copying (in 
cycle).
I already have seen two problematic disks. They allow to copy some data at high 
speed, then they become slow, until the reading is stopped. If waited a couple 
of seconds - copying resumes at full speed. I suspect the problems (they have) 
are in their caching system (buffering). Or one head is not perfect - causes 
slow readings.
One of them has no important data (no data at all, because that little 
everything that was needed - had already been copied long enough ago, disk 
wiped with Victoria 4.46 for Windows), the other one is being copied with the 
following command line:
(sudo mc), CTRL+O :)
fdisk -lu (system is on sdc, copying from sdb to sda)
ddrescue /dev/sdb /dev/sda ~/log_toshiba_to_wd.txt -f -vv --ask -b4096 -c1 -R 
-u -a102400 -K65536s,784Mib -O --cpass=1,2 --pause=5
This helps a little. Best speed is  about 16 Mb/s, average falls down to 2 Mb/s.
But, if stopped while skipping slow areas, and then restarted with the same 
options - it works at 16 Mb/s again.
Also, when the program is used on a device with surface scratches or with one 
slow head - I need the program to stop immediately when speed falls, without 
any more tries to read damaged areas. So, if it reads stably (from "stable") at 
15 Mb/s and falls to 8 or less - STOP immediately. Is it possible to do so?

2) The second my question is about using direct mode on disks with advanced 
format.
Both input and output devices have native sector sizes of 4kb (emulated to OS 
as 512 bytes) and size of 3000Gb.
direct mode ( -d) did not work on 3Tb Toshiba drive in any of the combinations:
-d
-d -c1 (worked fine with 1Tb Hitachi drive with one dying head - slow readings 
of 128 Mb repeatedly after 640Mb of good areas)
-d -b4096 -c1
-d -c8

3) Can you add (return/implement back) the option of log_saving_time_interval 
or just make it static, about 30 seconds. As I remember, it existed in earlier 
versions. Sometimes the system hangs - and some progress is lost.
Also, this will help to visualize the copying process using ddrescueview :).
It it will slow down the copying - just warn about it, but please, let us have 
this option.

4) I can translate the program and documentation to Russian - will it be 
helpful for the project?

With respect to you and your program,
[nickname=Joe] from Russia.