Method and system for using machine translation with content language specification

DETAILED DESCRIPTION The present invention continues to be based on an administrator authorized configuration, but now employs a new use for an HTTP response as the final factor in driving MT.
In particular, the Content-Language field in the entity-header of the HTTP response is used.
The HTTP 1.
1 specification defines the purpose of the value in this field `to identify and differentiate entities according to a user's own preferred language`.
Its implication is that the content body is in the language defined via the Content-Language field.
For example, if the body content is only appropriate to a German-literate audience then typical use of this information would be to execute some processing to avoid rendering to someone other than that target.
This information is used in rendering decisions.
It is proposed that this value be a determining factor in the MT decision as well.
It is still used in the rendering decision, but if the content is not currently in the desired language, it will be translated to it.
Prior to the response being served, appropriate MT would be initiated based on this value.
In addition to its current use, a new use of this field would be defined as the target language of MT as well as what language is appropriate forrendering.
Now an HTML author or a program that dynamically creates content can do so in only their language of choice while the Content-Language field set during the HTTP response creation process defines what language the content should be dynamically translated into.
Known techniques for Language Guessing could be used to determine the source language.
Normal use of the same Content-Language field would still be applicable in terms of its use to make target rendering decisions.
This solution could be implemented in, for example, the IBM HTTP Server and/or the WebSphere Application Server or any other system that supports HTTP.