[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/doc_generated/sdk/release-notes.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="release-notes">
 <span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release-notes"></span>Release Notes</h1>
 <section id="chrome-pepper-35-31-mar-2014">
 <h2 id="chrome-pepper-35-31-mar-2014">Chrome/Pepper 35 (31 Mar 2014)</h2>
 <section id="pnacl">
 <h3 id="pnacl">PNaCl</h3>
 <ul class="small-gap">
 <li>Upgraded LLVM to version 3.4.</li>
@@ skipping 76 matching lines @@
 </section><section id="pnacl-15-may-2013">
 <h2 id="pnacl-15-may-2013">PNaCl (15 May 2013)</h2>
 <ul class="small-gap">
 <li>Portable Native Client (PNaCl) is currently available for developer preview
 in Chrome 29 or higher.</li>
 <li>To produce a PNaCl executable (.pexe) file, you must use the pnacl toolchain
 in the current <code>pepper_canary</code> bundle. Chrome 29 does not support .pexe
 files produced by earlier versions of the pnacl toolchain (that is,
 executables compiled with the <code>pepper_28</code> bundle or earlier).</li>
 <li>To run an application with a PNaCl module, you must launch Chrome 29 with the
-<code>--enable-pnacl</code> flag (for <a class="reference external" href="http://developer.chrome.com/apps/about_apps.html">packaged apps</a>), or the
+<code>--enable-pnacl</code> flag (for <a class="reference external" href="/apps/about_apps">packaged apps</a>), or the
 <code>--enable-nacl</code> flag (for other apps).</li>
 <li>When you launch Chrome with the <code>--enable-pnacl</code> flag, Chrome loads a PNaCl
 translator in the background. Wait about a minute after you launch Chrome and
 check <a class="reference external" href="chrome://nacl">chrome://nacl</a> to verify that the translator loaded.</li>
 <li>PNaCl translators are currently available for 32-bit x86, 64-bit x86, and ARM
 architectures.</li>
 <li>PNaCl applications must use the newlib C library (glibc and dynamic linking
 are not supported yet).</li>
 <li>The intermediate representation (IR) format may change prior to the release
 of PNaCl. If so, you will need to recompile your application with the pnacl
@@ skipping 132 matching lines @@
 </ul>
 </li>
 <li>The simple web server included in the SDK, <code>httpd.py</code>, has been moved from
 the <code>examples/</code> directory to the <code>tools/</code> directory. On Windows, you can
 run <code>httpd.cmd</code> (in the <code>examples/</code> directory) to start the server.</li>
 </ul>
 </section><section id="ppapi">
 <h3 id="ppapi">PPAPI</h3>
 <p>Pepper 25 includes two new APIs:</p>
 <ul class="small-gap">
-<li>The <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/struct_p_p_b___console__1__0">Console API</a>
-lets your module log messages to the JavaScript console in the Chrome browser.</li>
-<li>The <a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop">MessageLoop</a>
-API lets your module make PPAPI calls on a background thread.  Once you&#8217;ve
-created a message loop resource, attached it to a thread, and run it, you can
-post work to the thread, including completion callbacks for asynchronous
-operations. For a C++ example of how to use the MessageLoop API,
-see <code>pepper_25/include/ppapi/utility/threading/simple_thread.h</code>. Note that
-you cannot make asynchronous PPAPI calls on a background thread without
-creating and using a message loop.</li>
+<li>The <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___console__1__0">Console API</a> lets your
+module log messages to the JavaScript console in the Chrome browser.</li>
+<li>The <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_message_loop">MessageLoop</a> API lets your
+module make PPAPI calls on a background thread.  Once you&#8217;ve created a
+message loop resource, attached it to a thread, and run it, you can post work
+to the thread, including completion callbacks for asynchronous operations.
+For a C++ example of how to use the MessageLoop API, see
+<code>pepper_25/include/ppapi/utility/threading/simple_thread.h</code>. Note that you
+cannot make asynchronous PPAPI calls on a background thread without creating
+and using a message loop.</li>
 </ul>
 </section><section id="id6">
 <h3 id="id6">Libraries</h3>
 <p>The SDK includes two new libraries:</p>
 <ul class="small-gap">
 <li><p class="first">The <strong>nacl_mounts</strong> library provides a virtual file system that your module
 can &#8220;mount&#8221; in a given directory tree. The file system can be one of several
 types:</p>
 <ul class="small-gap">
 <li>&#8220;memfs&#8221; is an in-memory file system,</li>
@@ skipping 91 matching lines @@
 your development machine. Within each toolchain build, each example also
 builds both a debug and a release version.</li>
 <li>The example Makefiles use dependency (.d) files to enable incremental builds.</li>
 <li>The pong example has been cleaned up and modified to run more smoothly. The
 drawing function is now set up as the Flush() callback, which allows 2D
 drawing to occur as quickly as possible.</li>
 </ul>
 </section><section id="id11">
 <h3 id="id11">PPAPI</h3>
 <ul class="small-gap">
-<li>When creating a 3D rendering context, the <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8">attribute list</a>
+<li>When creating a 3D rendering context, the <a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8">attribute list</a>
 for the context can specify whether to prefer low power or performance for
 the GPU. Contexts with a low power preference may be created on an integrated
 GPU; contexts with a performance preference may be created on a discrete GPU.</li>
 </ul>
 </section><section id="windows-sdk">
 <h3 id="windows-sdk">Windows SDK</h3>
 <ul class="small-gap">
 <li>The Windows SDK includes the pthreads-win32 library to assist in porting from
 win32 code. You can use this library when developing your module as a Pepper
 plug-in (.dll). See pepper_24/include/win/pthread.h and
 pepper_24/src/pthread/README for additional information.</li>
 <li>The update utility naclsdk.bat works when it is run from a path with spaces.</li>
 </ul>
 </section></section><section id="pepper-23-15-october-2012">
 <h2 id="pepper-23-15-october-2012">Pepper 23 (15 October 2012)</h2>
 <p>The Pepper 23 bundle includes support for the nacl-gdb debugger on Mac and
 32-bit Windows, resources to enable hosted development on Linux, and changes to
 make the SDK examples compliant with version 2 of the Chrome Web Store manifest
 file format.</p>
 <section id="tools">
 <h3 id="tools">Tools</h3>
 <ul class="small-gap">
-<li>The <a class="reference external" href="https://developers.google.com/native-client/pepper23/devguide/devcycle/debugging#gdb">nacl-gdb debugger</a>
-now works on all systems (Mac, Windows, and Linux).</li>
+<li>The <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#using-gdb"><em>nacl-gdb debugger</em></a> now works on all systems (Mac,
+Windows, and Linux).</li>
 <li>The output of the SDK update utility has been simplified. When you run the
 command <code>naclsdk list</code>, the utility displays one line for each available
 bundle, annotated with an &#8220;<code>I</code>&#8221; if the bundle is already installed on your
 system, and a &#8220;<code>*</code>&#8221; if the bundle has an update available. To see full
 information about a bundle, use the command <code>naclsdk info &lt;bundle&gt;</code> (for
 example, <code>naclsdk info pepper_28</code>).</li>
 </ul>
 </section><section id="linux-sdk">
 <h3 id="linux-sdk">Linux SDK</h3>
 <ul class="small-gap">
@@ skipping 37 matching lines @@
 </li>
 </ul>
 </section><section id="id12">
 <h3 id="id12">Examples</h3>
 <ul class="small-gap">
 <li>On Linux and Windows systems, most of the examples now build with three
 toolchains: the Native Client glibc and newlib toolchains, and the native
 toolchain on the host system. Modules built with the native toolchain on the
 host system can only run as Pepper plugins.</li>
 <li>All examples in the SDK now comply with version 2 of the Chrome Web Store
-<a class="reference external" href="http://developer.chrome.com/extensions/manifest.html">manifest file format</a>. By default,
+<a class="reference external" href="/extensions/manifest">manifest file format</a>. By default,
 applications that use version 2 of the manifest file format apply a strict
-<a class="reference external" href="http://developer.chrome.com/extensions/contentSecurityPolicy.html">content security policy</a>, which
+<a class="reference external" href="/extensions/contentSecurityPolicy">content security policy</a>, which
 includes a restriction against inline JavaScript. This restriction prohibits
 both inline <code>&lt;script&gt;</code> blocks and inline event handlers (e.g., <code>&lt;button
-onclick=&quot;...&quot;&gt;</code>).  See <a class="reference external" href="http://developer.chrome.com/extensions/manifestVersion.html">Manifest Version</a> for a list of
-changes between version 1 and version 2 of the manifest file format, and a
-support schedule for applications that use version 1.</li>
+onclick=&quot;...&quot;&gt;</code>).  See <a class="reference external" href="/extensions/manifestVersion">Manifest Version</a> for
+a list of changes between version 1 and version 2 of the manifest file
+format, and a support schedule for applications that use version 1.</li>
 </ul>
 </section><section id="id13">
 <h3 id="id13">PPAPI</h3>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/pepper23/pepperc/group___enums#ga21b811ac0484a214a8751aa3e1c959d9">PP_InputEvent_Modifier</a>
+<li><a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga21b811ac0484a214a8751aa3e1c959d9">PP_InputEvent_Modifier</a>
 has two new enum values (_ISLEFT and _ISRIGHT).</li>
-<li>The memory leak in the <a class="reference external" href="https://developers.google.com/native-client/pepper23/pepperc/struct_p_p_b___web_socket__1__0">WebSocket</a>
-API has been fixed.</li>
+<li>The memory leak in the <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___web_socket__1__0">WebSocket</a> API has
+been fixed.</li>
 </ul>
 </section></section><section id="pepper-22-22-august-2012">
 <h2 id="pepper-22-22-august-2012">Pepper 22 (22 August 2012)</h2>
 <p>The Pepper 22 bundle includes a <strong>command-line debugger</strong>, resources to enable
 <strong>hosted development on Windows</strong>, and changes to the example Makefiles (each
 example now builds both a debug and a release version).</p>
 <section id="id14">
 <h3 id="id14">Tools</h3>
 <ul class="small-gap">
 <li>The SDK now includes a <strong>command-line debugger</strong> that you can use to debug
@@ skipping 62 matching lines @@
 <li>Comments have been added to common.js, which is used in all the examples. The
 JavaScript in common.js inserts an &lt;embed&gt; element that loads the NaCl module
 in each example&#8217;s web page, attaches event listeners to monitor the loading
 of the module, and implements handleMessage() to respond to messages sent
 from the NaCl module to the JavaScript side of the application</li>
 </ul>
 </section><section id="id17">
 <h3 id="id17">PPAPI</h3>
 <ul class="small-gap">
 <li>The <code>CompletionCallbackFactory</code> class template now takes a thread traits
-class as its second parameter. For details see the <a class="reference external" href="https://developers.google.com/native-client/pepper22/peppercpp/classpp_1_1_completion_callback_factory#details">CompletionCallbackFactory
+class as its second parameter. For details see the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory#details">CompletionCallbackFactory
 class template reference</a>.</li>
 </ul>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}