How should software licenses be displayed in multi-lingual applications?
<p>I have been hired by a Canadian governmental agency to release a version of my application on their behalf. They have informed me that I must add the French language to my application to comply with local law according to the  to <a href="http://www.ofa.gov.on.ca/en/flsa-mapdesig.html" rel="nofollow">French Language Services Act</a> which:</p>

<blockquote>
  <p>...guarantees the right to services in French from the provincial government in government offices in designated areas of the province.</p>
</blockquote>

<p>I was in the process of updating my applications to French when I ran into an interesting dilemma: <strong>Should the attribution screen, which includes copyright and 3rd party software licenses, also be translated?</strong> </p>

<p>Previously, I had always worked with the understanding that any alterations (including translations) violate the licenses unless an official translated license is obtained from the license authors;  If no official translation exists, then these licenses must be displayed as-is in English. This is further supported by <a href="http://info.protecode.com/bid/33956/How-you-can-comply-with-open-source-license-attribution" rel="nofollow">my research</a> which states</p>

<blockquote>
  <p>Most licenses, open source or commercial, require that a copy of the copyright, patent, trademark, and attribution notices from the source software be distributed <strong>verbatim</strong> with the product using that software.</p>
</blockquote>

<p>However, I don't have any official documentation that backs this understanding and this goes against what has been requested of me by this agency. They would like this page to also be translated. </p>

<p>This leads me to ask the additional following questions:</p>

<ul>
<li>If it should <em>not</em> be translated, is there a legal reference I can provide to the agency to support this conclusion?</li>
<li>If it <em>is allowed</em> to be translated, is hiring a translator sufficient?</li>
</ul>

<p>The licenses that are used in my application include: </p>

<ul>
<li>Apache 2.0</li>
<li>MPLv2</li>
<li>BSD License</li>
<li>MIT license</li>
</ul>

<p>It's not your license. It's the MIT's license, for example. </p>

<p>What all these licenses have in common is that they allow the user to use the software in the way that copyright law allows, and then give the user certain further rights. So all the users of the software can use it just fine without being able to read the license terms, as long as they don't do anything outside what copyright law allows. </p>

<p>If they want to do things that exceed what copyright law does, they must adhere to the license. That requires being confident that you understand the license text - if you don't understand it, it would be stupid to do things that might be copyright infringement. But all that is of no concern to users, only to software developers. </p>

<p>As an example, German courts have decided that GPL being in English is Ok in Germany, because German software developers can be expected to speak English. </p>

<p>All in all, I would say that a translation of these licenses isn't necessary because users don't need it, and the reason why you have to display the license is usually because the license itself requires you to display the unmodified license. </p>

<p>Translating a license can change its terms, I would suggest looking on the appropriate site for the French versions.</p>

<p>I would contact the owners as some sites won't allow you to do this.</p>

licensing software translation