Document Translator Update - Unsigned bits

Enabled Clouds and Regions:
Azure recently allows you to create the Translator resource in a region of your choice. The region determines where your Custom Translator training documents are stored. Using a regional resource instead of a global one requires to pass the region together with the key in every request. Document Transl;ator now does that. Make sure that the region selection in Document Translator matches the reqion of where you created the Azure resource and copied the key from.
Translator runs in multiple clouds: the public cloud, what you know as regular Azure, the US government cloud and the China cloud. You can now pick the cloud you want to run in. The public cloud further allows you to choose whether you want the processing to happen in the Americas, in Europe, or in Asia Pacific. If you don't care where the processing happens, choose the "Global" cloud. In that case the nearest available Azure datacenter will be used to process your request.

Also fixed the bug that write-protected Office documents couldn't be translated. Now they can.
Catch some exception when the settings file is missing.