update based on https://github.com/mdn/yari/issues/2028

4 files changed, 0 insertions, 209 deletions

diff --git a/files/zh-cn/mozilla/add-ons/plugins/index.html b/files/zh-cn/mozilla/add-ons/plugins/index.html
deleted file mode 100644
index f35791a3bf..0000000000
--- a/files/zh-cn/mozilla/add-ons/plugins/index.html
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Plugins
-slug: Mozilla/Add-ons/Plugins
-tags:
-  - Add-ons
-  - NPAPI
-  - NeedsTranslation
-  - Plugins
-  - TopicStub
-translation_of: Archive/Plugins
----
-<div class="blockIndicator warning">
-<p><strong>Important</strong>: Since <a href="/en-US/docs/Mozilla/Firefox/Releases/52">Firefox 52</a>, all plugin support except Flash has been dropped (see <span><a href="https://www.fxsitecompat.com/en-CA/docs/2016/plug-in-support-has-been-dropped-other-than-flash/">Plug-in support has been dropped other than Flash</a> for more details</span>). Flash usage is also set to be phased out in the future.</p>
-</div>
-
-<div class="blockIndicator note">
-<p><strong>Note</strong>: Plugins are now a legacy technology. They are not available on most mobile devices. Mozilla encourages website developers to avoid using plugins wherever possible and use standard Web APIs instead. If there are plugin features which are not available in the web platform, we encourage developers to post their use cases to mozilla.dev.platform project list, so that Mozilla can prioritize web platform work to make those use cases possible.</p>
-</div>
-
-<p>For more information about plugin roadmap, see <a href="/en-US/docs/Plugins">non-archived plugin information</a>.</p>
-
-<p>Plugins are shared libraries that users can install to display content that the browser can't display natively. For example, the Adobe Reader plugin lets the user open PDF files directly inside the browser, and the QuickTime and RealPlayer plugins are used to play special format videos in a web page.</p>
-
-<p>Plugins are written using <strong>NPAPI</strong>, the cross-browser API for plugins. The main source of documentation for NPAPI is the <a href="/en/Gecko_Plugin_API_Reference" title="en/Gecko_Plugin_API_Reference">Gecko Plugin API Reference</a>. To make your plugin scriptable from web pages, use <a href="/en/Gecko_Plugin_API_Reference/Scripting_plugins" title="en/Gecko_Plugin_API_Reference/Scripting_plugins">npruntime</a>.</p>
-
-<p>Plugins can be written completely from scratch using C APIs (usually in C or C++) or they may be built on a plugin framework such as <a class="external" href="http://www.firebreath.org" title="http://www.firebreath.org/">Firebreath</a>, <a class="external" href="http://www.juce.com/" title="http://www.rawmaterialsoftware.com/juce.php">JUCE</a>, or <a class="external" href="http://doc.qt.nokia.com/solutions/4/qtbrowserplugin/developingplugins.html" title="http://doc.qt.nokia.com/solutions/4/qtbrowserplugin/developingplugins.html">QtBrowserPlugin</a>. There are also some code generation tools that may be helpful. More information about these tools can be found on the <a href="/en/Plugins/External_resources_for_plugin_creation" title="en/Plugins/External resources for plugin creation">External Resources</a> page.</p>
-
-<p>Plugins are different from <a href="/en/Extensions" title="en/Extensions">extensions</a>, which modify or enhance the functionality of the browser itself. Plugins are also different from <a href="/en/Creating_OpenSearch_plugins_for_Firefox" title="en/Creating_OpenSearch_plugins_for_Firefox">search plugins</a>, which plug additional search engines in the search bar.</p>
-
-<hr>
-<div class="topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en/Gecko_Plugin_API_Reference" title="en/Gecko_Plugin_API_Reference">Gecko Plugin API Reference</a> (NPAPI)</dt>
- <dd>This reference describes the application programming interfaces for NPAPI plugins and provides information about how to use these interfaces.</dd>
- <dt><a href="/en-US/docs/Site_Author_Guide_for_Click-To-Activate_Plugins">Site Author Guide For Click-To-Activate Plugins</a></dt>
- <dd>These guidelines will help website authors use plugins when they are blocked by default with the Firefox click-to-activate feature.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Gecko_Plugin_API_Reference/Scripting_plugins" title="en/Gecko_Plugin_API_Reference/Scripting_plugins">Scripting plugins</a> (npruntime)</dt>
- <dd>This reference describes the new cross-browser NPAPI extensions that let plugins be scriptable and also let them access the script objects in the browser.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Shipping_a_plugin_as_a_Toolkit_bundle" title="en/Shipping_a_plugin_as_a_Toolkit_bundle">Shipping a plugin as a Toolkit bundle</a></dt>
- <dd>Plugins can be shipped as a Toolkit <a href="/en/Bundles" title="Bundles">bundle</a>, allowing a user to easily install, uninstall and manage their personal plugins.</dd>
-</dl>
-
-<dl>
- <dt><a class="internal" href="/En/Supporting_private_browsing_in_plugins" title="en/Supporting private browsing in plugins">Supporting private browsing in plugins</a></dt>
- <dd>Firefox 3.5 introduced support for private browsing; learn how to make your plugin respect the user's privacy wishes.</dd>
- <dt><a href="/en/Plugins/Multi-Process_Plugin_Architecture" title="en/Plugins/Multi-Process Plugin Architecture">Multi-Process Plugin Architecture</a></dt>
- <dd>How Firefox loads plugins into a separate process. Firefox 3.6.4 introduced out-of-process plugins which execute in a separate process so that a crashing plugin does not crash the browser.</dd>
- <dt><a href="/en/Plugins/Logging" title="en/Plugins/Logging">Logging and Debugging for Multi-Process Plugins</a></dt>
- <dd>How to create a plugin log to aid in debugging problems with multi-process plugins.</dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a class="internal" href="/En/Writing_a_plugin_for_Mac_OS_X" title="en/Writing a plugin for Mac OS X">Writing a plugin for Mac OS X</a></dt>
- <dd>Learn how to write a plugin for Mac OS X; a template Xcode project is provided.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Monitoring_plugins" title="en/Monitoring_plugins">Monitoring Plugins</a></dt>
- <dd>Use an observer service notification to monitor the amount of time spent executing calls in plugins. This can be useful when trying to determine if a plug-in is consuming too many resources.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Scripting_Plugins/Adobe_Flash" title="en/Scripting_Plugins/Macromedia_Flash">Scripting Plugins: Macromedia Flash</a></dt>
- <dd>This article explains how JavaScript can be used to access methods from within the Flash plugin, as well as how a feature called FSCommands can be used to access JavaScript functions from within the Flash animation.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Gecko_Plugin_API_Reference/Plug-in_Development_Overview" title="en/Plugins/The_First_Install_Problem">Plugins: The First Install Problem</a></dt>
- <dd>The First Install Problem is the name given to the conditions arising when a plugin or embeddable software installs itself on a system first, before any other Gecko-based browser.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/Plugins/Samples_and_Test_Cases" title="en/Plugins/Samples_and_Test_Cases">Plugins: Samples and Test Cases</a></dt>
- <dd>NPAPI plugin samples and test cases.</dd>
- <dt><a href="/en/Plugins/External_resources_for_plugin_creation" title="https://developer.mozilla.org/en/Plugins/External_resources_for_plugin_creation">External Resources for Plugin Creation</a></dt>
- <dd>External projects, frameworks, and blog posts that may be useful.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en/XEmbed_Extension_for_Mozilla_Plugins" title="en/XEmbed_Extension_for_Mozilla_Plugins">XEmbed Extension for Mozilla Plugins</a></dt>
- <dd>Recent versions of Mozilla on *nix-based systems include an extension for writing plugins that use XEmbed instead of using the old Xt-based main loop that most plugins have been using since the Netscape 3.x days.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<p><span class="comment">Categories</span></p>
-
-<p><span class="comment">Interwiki Language Links</span></p>
-
-<div class="blockIndicator communitybox" dir="ltr">
-<div class="column-container">
-<h2 id="Join_the_plugin_development_community">Join the plugin development community</h2>
-
-<div class="column-half">
-<div class="communitysubhead">Choose your preferred method for joining the discussion:</div>
-
-<ul class="communitymailinglist">
- <li><a href="https://lists.mozilla.org/listinfo/dev-tech-plugins">Mailing list</a></li>
- <li><a href="http://groups.google.com/group/mozilla.dev.tech.plugins">Newsgroup</a></li>
- <li><a href="http://groups.google.com/group/mozilla.dev.tech.plugins/feeds">RSS feed</a></li>
-</ul>
-</div>
-
-<div class="column-half"> </div>
-</div>
-</div>
diff --git a/files/zh-cn/mozilla/add-ons/plugins/reference/index.html b/files/zh-cn/mozilla/add-ons/plugins/reference/index.html
deleted file mode 100644
index fcb2ba7232..0000000000
--- a/files/zh-cn/mozilla/add-ons/plugins/reference/index.html
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: NPAPI plugin reference
-slug: Mozilla/Add-ons/Plugins/Reference
-tags:
-  - Deprecated
-  - Landing
-  - NPAPI
-  - NeedsTranslation
-  - Plugins
-  - Reference
-  - TopicStub
-translation_of: Archive/Plugins/Reference
----
-<p>{{deprecated_header}}</p>
-<p>The articles below describe each of the APIs related to NPAPI plugins.</p>
-<p>{{LandingPageListSubpages}}</p>
diff --git a/files/zh-cn/mozilla/add-ons/plugins/samples_and_test_cases/index.html b/files/zh-cn/mozilla/add-ons/plugins/samples_and_test_cases/index.html
deleted file mode 100644
index 4d0ac34085..0000000000
--- a/files/zh-cn/mozilla/add-ons/plugins/samples_and_test_cases/index.html
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Samples and Test Cases
-slug: Mozilla/Add-ons/Plugins/Samples_and_Test_Cases
-translation_of: Archive/Plugins/Samples_and_Test_Cases
----
-<h2 id="NPAPI_Plugin_Samples">NPAPI Plugin Samples</h2>
-<p>Collections of NPAPI plugin samples can be found in the Seamonkey source code at <a class="external" href="http://mxr.mozilla.org/seamonkey/source/modules/plugin/samples/" title="http://mxr.mozilla.org/seamonkey/source/modules/plugin/samples/">/modules/plugin/sdk/samples</a>.</p>
-<p>The samples may not build any more on all platforms. There are plans to clean up the sample plugin situation - better organization, updated build systems, get them building on all platforms. However, even if one cannot build the samples they can still be very valuable as code references.</p>
-<p>There is a <a href="/en/Compiling_The_npruntime_Sample_Plugin_in_Visual_Studio" title="en/Compiling_The_npruntime_Sample_Plugin_in_Visual_Studio">guide to compiling the npruntime sample in Visual Studio</a>.</p>
-<p>In addition to those samples, there are 2 more plugins in the tree that might be helpful.</p>
-<ul>
- <li><a class="external" href="http://mxr.mozilla.org/seamonkey/source/modules/plugin/tools/spy/">Spy</a></li>
- <li><a class="external" href="http://mxr.mozilla.org/seamonkey/source/modules/plugin/tools/tester/">Tester</a></li>
-</ul>
-<h2 id="NPAPI_Plugin_Test_Cases">NPAPI Plugin Test Cases</h2>
-<ul>
- <li>mozilla.org QA <a class="external" href="http://www.mozilla.org/quality/browser/front-end/testcases/plugins/">Plugins testcases</a></li>
- <li>mozilla.org QA <a class="external" href="http://www.mozilla.org/quality/browser/front-end/testcases/oji/">OJI testcases</a></li>
- <li><a class="external" href="http://www.mozilla.org/projects/plugins/plugins_testing_checklist.html">Plugins Verification Testing Checklist</a> (including <a class="external" href="http://www.mozilla.org/quality/smoketests/">SmokeTesting</a>)</li>
-</ul>
-<p>{{ languages( { "de": "de/Plugins/Beispiele_und_Testfälle" } ) }}</p>
diff --git a/files/zh-cn/mozilla/add-ons/plugins/shipping_a_plugin_as_a_toolkit_bundle/index.html b/files/zh-cn/mozilla/add-ons/plugins/shipping_a_plugin_as_a_toolkit_bundle/index.html
deleted file mode 100644
index 30aae2d422..0000000000
--- a/files/zh-cn/mozilla/add-ons/plugins/shipping_a_plugin_as_a_toolkit_bundle/index.html
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Shipping a plugin as an extension
-slug: Mozilla/Add-ons/Plugins/Shipping_a_plugin_as_a_Toolkit_bundle
-tags:
-  - Extensions
-  - Plugins
-translation_of: Archive/Plugins/Shipping_a_plugin_as_a_Toolkit_bundle
----
-<p>One of the new features that is available in Firefox 1.5 is the ability to place browser plug-ins in a Firefox extension.</p>
-<p>Historically, most people have chosen to use an install.js script to install a plug-in. When this method is used, you can choose to either place the plug-in into the plugins directory, or place it into your own directory and modify the Windows registry to let Firefox know where to find the plug-in. The downside to this method is that once the plug-in is installed, it might be difficult for users to upgrade, uninstall, or disable the plug-in. As of Firefox 3 (and any Gecko 1.9 based application) the use of install.js scripts is no longer possible and plugins must either be shipped as an executable installer or as an extension as described here.</p>
-<h2 id="Bundle_structure" name="Bundle_structure">Bundle structure</h2>
-<p><a href="cn/Bundles">Toolkit bundles</a> can be used for all add-ons including extensions, themes and plugins. Plugin packages should only need to package a small set of files in the follow structure in the xpi file:</p>
-<pre>install.rdf
-plugins/
-    pluginlib.dll
-    plugintypes.xpt
-</pre>
-<p>The install.rdf file contains an <a href="#Install_Manifest">install manifest</a> that describes the plugin to the user. The library and scripting interfaces are held in the &lt;tt&gt;plugins&lt;/tt&gt; directory.</p>
-<h3 id="Platform-specific_files" name="Platform-specific_files">Platform-specific files</h3>
-<p>It is possible to package multiple plugin libraries for different operating systems into a single xpi bundle. In the xpi you can use the following structure:</p>
-<pre>platform/
-    Linux_x86-gcc3/
-        plugins/
-            libplugin.so
-    Darwin_ppc-gcc3/
-        plugins/
-            libplugin.dylib
-</pre>
-<p>More specific information can be found in the <a href="cn/Bundles#Platform-specific_Subdirectories">platform-specific subdirectories</a> documentation.</p>
-<h2 id="Install_Manifest" name="Install_Manifest">Install Manifest</h2>
-<p>The <a href="cn/Install.rdf">install manifest</a> describes the plugin to the user. For a plugin the manifest only needs to be very simple:</p>
-<pre>&lt;RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#"&gt;
-  &lt;Description about="urn:mozilla:install-manifest"&gt;
-    &lt;em:id&gt;mypluginid@myplugin.com&lt;/em:id&gt;
-    &lt;em:name&gt;My Plugin&lt;/em:name&gt;
-    &lt;em:version&gt;1.0&lt;/em:version&gt;
-    &lt;em:targetApplication&gt;
-      &lt;Description&gt;
-        &lt;em:id&gt;{ec8030f7-c20a-464f-9b0e-13a3a9e97384}&lt;/em:id&gt;
-        &lt;em:minVersion&gt;1.5&lt;/em:minVersion&gt;
-        &lt;em:maxVersion&gt;3.0.*&lt;/em:maxVersion&gt;
-      &lt;/Description&gt;
-    &lt;/em:targetApplication&gt;
-  &lt;/Description&gt;
-&lt;/RDF&gt;
-</pre>
-<p>This contains 4 required pieces of information.</p>
-<ol>
- <li>Every add-on must have a unique id. This can be in a guid form but the simpler email form is preferred now. You should aim to use a domain-name that you own and then your own unique short-name for the plugin before the @.</li>
- <li>The plugin must have a name to identify the plugin to the user in the list of add-ons.</li>
- <li>The version is fairly self-descriptive, it must be a <a href="cn/Toolkit_version_format">toolkit version format</a>.</li>
- <li>The target application block says which versions of an application the plugin is compatible with. It includes the application ID and the minimum and maximum version of the application that the plugin works with. There can be multiple targetApplication blocks listed.</li>
-</ol>
-<h2 id="Providing_updates" name="Providing_updates">Providing updates</h2>
-<p>When plugins are packaged in this way they can make use of the built in add-on update system. This allows a remote update file to be read periodically and an updated version of the plugin offered to the user or to mark the plugin as compatible with a wider range of applications.</p>
-<p>This is performed by including an <a href="cn/Install.rdf#updateURL">updateURL</a> in the install manifest. This should point to an <a href="cn/Extension_Versioning%2c_Update_and_Compatibility#Update_RDF_Format">update.rdf</a> file on the internet which will include the updated versions and version information for the plugin.</p>