<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <item>
+ <title>Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</title>
+ <link>http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</guid>
+ <pubDate>Mon, 25 Aug 2014 22:10:00 +0200</pubDate>
+ <description><p>Two years later, I am still not sure if it is legal here in Norway
+to use or publish a video in H.264 or MPEG4 format edited by the
+commercially licensed video editors, without limiting the use to
+create "personal" or "non-commercial" videos or get a license
+agreement with <a href="http://www.mpegla.com">MPEG LA</a>. If one
+want to publish and broadcast video in a non-personal or commercial
+setting, it might be that those tools can not be used, or that video
+format can not be used, without breaking their copyright license. I
+am not sure.
+<a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Back
+then</a>, I found that the copyright license terms for Adobe Premiere
+and Apple Final Cut Pro both specified that one could not use the
+program to produce anything else without a patent license from MPEG
+LA. The issue is not limited to those two products, though. Other
+much used products like those from Avid and Sorenson Media have terms
+of use are similar to those from Adobe and Apple. The complicating
+factor making me unsure if those terms have effect in Norway or not is
+that the patents in question are not valid in Norway, but copyright
+licenses are.</p>
+
+<p>These are the terms for Avid Artist Suite, according to their
+<a href="http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2">published
+end user</a>
+<a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">license
+text</a> (converted to lower case text for easier reading):</p>
+
+<p><blockquote>
+<p>18.2. MPEG-4. MPEG-4 technology may be included with the
+software. MPEG LA, L.L.C. requires this notice: </p>
+
+<p>This product is licensed under the MPEG-4 visual patent portfolio
+license for the personal and non-commercial use of a consumer for (i)
+encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
+video”) and/or (ii) decoding MPEG-4 video that was encoded by a
+consumer engaged in a personal and non-commercial activity and/or was
+obtained from a video provider licensed by MPEG LA to provide MPEG-4
+video. No license is granted or shall be implied for any other
+use. Additional information including that relating to promotional,
+internal and commercial uses and licensing may be obtained from MPEG
+LA, LLC. See http://www.mpegla.com. This product is licensed under
+the MPEG-4 systems patent portfolio license for encoding in compliance
+with the MPEG-4 systems standard, except that an additional license
+and payment of royalties are necessary for encoding in connection with
+(i) data stored or replicated in physical media which is paid for on a
+title by title basis and/or (ii) data which is paid for on a title by
+title basis and is transmitted to an end user for permanent storage
+and/or use, such additional license may be obtained from MPEG LA,
+LLC. See http://www.mpegla.com for additional details.</p>
+
+<p>18.3. H.264/AVC. H.264/AVC technology may be included with the
+software. MPEG LA, L.L.C. requires this notice:</p>
+
+<p>This product is licensed under the AVC patent portfolio license for
+the personal use of a consumer or other uses in which it does not
+receive remuneration to (i) encode video in compliance with the AVC
+standard (“AVC video”) and/or (ii) decode AVC video that was encoded
+by a consumer engaged in a personal activity and/or was obtained from
+a video provider licensed to provide AVC video. No license is granted
+or shall be implied for any other use. Additional information may be
+obtained from MPEG LA, L.L.C. See http://www.mpegla.com.</p>
+</blockquote></p>
+
+<p>Note the requirement that the videos created can only be used for
+personal or non-commercial purposes.</p>
+
+<p>The Sorenson Media software have
+<a href="http://www.sorensonmedia.com/terms/">similar terms</a>:</p>
+
+<p><blockquote>
+
+<p>With respect to a license from Sorenson pertaining to MPEG-4 Video
+Decoders and/or Encoders: Any such product is licensed under the
+MPEG-4 visual patent portfolio license for the personal and
+non-commercial use of a consumer for (i) encoding video in compliance
+with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
+MPEG-4 video that was encoded by a consumer engaged in a personal and
+non-commercial activity and/or was obtained from a video provider
+licensed by MPEG LA to provide MPEG-4 video. No license is granted or
+shall be implied for any other use. Additional information including
+that relating to promotional, internal and commercial uses and
+licensing may be obtained from MPEG LA, LLC. See
+http://www.mpegla.com.</p>
+
+<p>With respect to a license from Sorenson pertaining to MPEG-4
+Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
+MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
+product is licensed under the MPEG-4 systems patent portfolio license
+for encoding in compliance with the MPEG-4 systems standard, except
+that an additional license and payment of royalties are necessary for
+encoding in connection with (i) data stored or replicated in physical
+media which is paid for on a title by title basis and/or (ii) data
+which is paid for on a title by title basis and is transmitted to an
+end user for permanent storage and/or use. Such additional license may
+be obtained from MPEG LA, LLC. See http://www.mpegla.com for
+additional details.</p>
+
+</blockquote></p>
+
+<p>Some free software like
+<a href="https://handbrake.fr/">Handbrake</A> and
+<a href="http://ffmpeg.org/">FFMPEG</a> uses GPL/LGPL licenses and do
+not have any such terms included, so for those, there is no
+requirement to limit the use to personal and non-commercial.</p>
+</description>
+ </item>
+
<item>
<title>Lenker for 2014-08-03</title>
<link>http://people.skolelinux.org/pere/blog/Lenker_for_2014_08_03.html</link>
</description>
</item>
- <item>
- <title>Språkkoder for POSIX locale i Norge</title>
- <link>http://people.skolelinux.org/pere/blog/Spr_kkoder_for_POSIX_locale_i_Norge.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Spr_kkoder_for_POSIX_locale_i_Norge.html</guid>
- <pubDate>Fri, 11 Apr 2014 21:30:00 +0200</pubDate>
- <description><p>For 12 år siden, skrev jeg et lite notat om
-<a href="http://i18n.skolelinux.no/localekoder.txt">bruk av språkkoder
-i Norge</a>. Jeg ble nettopp minnet på dette da jeg fikk spørsmål om
-notatet fortsatt var aktuelt, og tenkte det var greit å repetere hva
-som fortsatt gjelder. Det jeg skrev da er fortsatt like aktuelt.</p>
-
-<p>Når en velger språk i programmer på unix, så velger en blant mange
-språkkoder. For språk i Norge anbefales følgende språkkoder (anbefalt
-locale i parantes):</p>
-
-<p><dl>
-<dt>nb (nb_NO)</dt><dd>Bokmål i Norge</dd>
-<dt>nn (nn_NO)</dt><dd>Nynorsk i Norge</dd>
-<dt>se (se_NO)</dt><dd>Nordsamisk i Norge</dd>
-</dl></p>
-
-<p>Alle programmer som bruker andre koder bør endres.</p>
-
-<p>Språkkoden bør brukes når .po-filer navngis og installeres. Dette
-er ikke det samme som locale-koden. For Norsk Bokmål, så bør filene
-være navngitt nb.po, mens locale (LANG) bør være nb_NO.</p>
-
-<p>Hvis vi ikke får standardisert de kodene i alle programmene med
-norske oversettelser, så er det umulig å gi LANG-variablen ett innhold
-som fungerer for alle programmer.</p>
-
-<p>Språkkodene er de offisielle kodene fra ISO 639, og bruken av dem i
-forbindelse med POSIX localer er standardisert i RFC 3066 og ISO
-15897. Denne anbefalingen er i tråd med de angitte standardene.</p>
-
-<p>Følgende koder er eller har vært i bruk som locale-verdier for
-"norske" språk. Disse bør unngås, og erstattes når de oppdages:</p>
-
-<p><table>
-<tr><td>norwegian</td><td>-> nb_NO</td></tr>
-<tr><td>bokmål </td><td>-> nb_NO</td></tr>
-<tr><td>bokmal </td><td>-> nb_NO</td></tr>
-<tr><td>nynorsk </td><td>-> nn_NO</td></tr>
-<tr><td>no </td><td>-> nb_NO</td></tr>
-<tr><td>no_NO </td><td>-> nb_NO</td></tr>
-<tr><td>no_NY </td><td>-> nn_NO</td></tr>
-<tr><td>sme_NO </td><td>-> se_NO</td></tr>
-</table></p>
-
-<p>Merk at når det gjelder de samiske språkene, at se_NO i praksis
-henviser til nordsamisk i Norge, mens f.eks. smj_NO henviser til
-lulesamisk. Dette notatet er dog ikke ment å gi råd rundt samiske
-språkkoder, der gjør
-<a href="http://www.divvun.no/">Divvun-prosjektet</a> en bedre
-jobb.</p>
-
-<p><strong>Referanser:</strong></p>
-
-<ul>
-
- <li><a href="http://www.rfc-base.org/rfc-3066.html">RFC 3066 - Tags
- for the Identification of Languages</a> (Erstatter RFC 1766)</li>
-
- <li><a href="http://www.loc.gov/standards/iso639-2/langcodes.html">ISO
- 639</a> - Codes for the Representation of Names of Languages</li>
-
- <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n897-14652w25.pdf">ISO
- DTR 14652</a> - locale-standard Specification method for cultural
- conventions</li>
-
- <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n610.pdf">ISO
- 15897: Registration procedures for cultural elements (cultural
- registry)</a>,
- <a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n849-15897wd6.pdf">(nytt
- draft)</a></li>
-
- <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/">ISO/IEC
- JTC1/SC22/WG20</a> - Gruppen for i18n-standardisering i ISO</li>
-
-<ul>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff