Various fixes to browser print functionality by M. Ogi.

 - If the Browser was invoked from within the context of a ScreenMan form, pressing <PF1><PF1>P to invoke the Browser print would cause the screen to become corrupted.

 - The ability to print to a CRT is no longer restricted.

 - If the input text to the Browser is passed in a local array, and the printout is queued, the text fail to print.

- The scrolling region was sometimes not getting reset to that needed by the Browser, after printing to a CRT.

- Reduced the Hang time from 2 to 1 after a printing to a CRT. This reduces the chance of the user pressing <RET> before leaving the print screen and returning to the Browser. (<RET> causes the browser window to shift to the right, and could cause some confusion.)

- Question mark (?) help at the prompts before device selection could be corrupted if the Browser is invoked within a ScreenMan context.
Fixed the Unit Tests per Don Creaven's input:
Running ^DMUDT000 in dev reports:

Internal Format to External Format - DD^%DT - <1705> vs <-1> - 5 (invalid value) converted to a unknown date.

The test is

dev>s Y=5 D DD^%DT W Y

1705

I think that is the right answer:  DD^%DT takes any sort of partial input.

---

Another unit test failure that I think is not an error:

NOW^DMUDTC00 - Tests NOW^%DTC - <313> vs <2013> - Year incorrect

This is testing the value returned in %I(3), like this:

dev>D NOW^%DTC

dev>W %

3130221.102141

dev>W %H

62874,37301

dev>F I=1:1:3 W %I(I)_"    "

2    21    313

dev>W X

3130221

dev>

The value 313 is FM’s year.  The test expects the calendar year.  But I think the FM year is the correct return value.  You could argue that the documentation is ambiguous.  In any case, can we validate that 313 is correct and (if so) fix the unit test to not report an error.