Document Translator Update - Signed bits

Codesigned Installer For V2.9.4

Document Translator Update - Unsigned bits

Fix two issues with HTML translation, reported in #156:

• Break when child node is null
• Translate single elements that are larger than maxrequestsize

Document Translator Update - Unsigned bits

Fixed: Sometimes the set of languages was unavailable at startup.
Fixed: Experimental languages were available only after restart. Now available immediately.

Document Translator Update - Unsigned bits

Translate Footnotes and Endnotes in Word documents.
Added SRT translation functionality to VTTTranslate.

Document Translator Update - Unsigned bits

Fixed BreakSentences and TranslateString to translate arbitrary length strings.
Added VTT file format support. The key in VTT and SRT translation is that the utterances need to be combined to full sentences before translation, and split up afterwards to match the time coding. VTT file translation now does that.
Still to do:

• Same for SRT file format
• Robustness for service call failures

Document Translator Update - Unsigned bits

New: Allows to save "Show Experimental Languages".
Bug: Requires restart of the app to show changes.
New: Show language names in all available languages.

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.

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.

Document Translator Update - Unsigned bits

Turned NormalizeXML and RemoveSmartTags for Word documents OFF to prevent load errors of the translated document.

Document Translator Update - Unsigned bits

Rewrote TranslateV3AsyncInternal to account for the load delay of custom systems as a while loop.