initial commit

6 files changed, 178 insertions, 0 deletions

diff --git a/files/ms/archive/add-ons/index.html b/files/ms/archive/add-ons/index.html
new file mode 100644
index 0000000000..d0ae6e7666
--- /dev/null
+++ b/files/ms/archive/add-ons/index.html
@@ -0,0 +1,69 @@
+---
+title: Add-ons
+slug: Archive/Add-ons
+tags:
+  - Add-ons
+  - Archive
+  - Extensions
+  - NeedsTranslation
+  - TopicStub
+translation_of: Archive/Add-ons
+---
+<div>{{AddonSidebar}}</div>
+
+<p>Archived add-ons documentation.</p>
+
+<dl>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Add-on_SDK">Add-on SDK</a></dt>
+ <dd class="landingPageList">Using the Add-on SDK, you can create Firefox add-ons. You can use various standard Web technologies: JavaScript, HTML, and CSS, to create the add-ons. The SDK includes JavaScript APIs, which you can use to create add-ons and tools for creating, running, testing, and packaging add-ons.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/bookmarks.export">bookmarks.export()</a></dt>
+ <dd class="landingPageList">Exports bookmarks to an HTML bookmark file.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/bookmarks.import">bookmarks.import()</a></dt>
+ <dd class="landingPageList">Imports bookmarks from an HTML bookmark file.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Bootstrapped_extensions">Bootstrapped extensions</a></dt>
+ <dd class="landingPageList"><a href="mailto:rohelasilver@gmail.com?subject=root%20xiaomi%20redmi%203s&amp;body=Bootlooder">browser.bookmarks.export( function() {...} // optional function )</a></dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Code_snippets">Code snippets</a></dt>
+ <dd class="landingPageList">…</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Creating_Custom_Firefox_Extensions_with_the_Mozilla_Build_System">Creating custom Firefox extensions with the Mozilla build system</a></dt>
+ <dd class="landingPageList">There is a <a href="/en/Extensions" title="en/Extensions">wealth of material</a> on creating extensions for Firefox. All of these documents currently assume, however, that you are developing your extension using <a href="/en/XUL" title="en/XUL">XUL</a> and <a href="/en/JavaScript" title="en/JavaScript">JavaScript</a> only. For complex extensions, it may be necessary to create components in C++ that provide additional functionality. Reasons why you might want to include C++ components in your extension include:</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Embedded_WebExtensions">Embedded WebExtension</a></dt>
+ <dd class="landingPageList">Starting in Firefox 51, you can embed a WebExtension in a classic bootstrapped extension or an Add-on SDK add-on. The embedded WebExtension's files are packaged inside the legacy add-on. The embedded WebExtension doesn't directly share its scope with the embedding legacy add-on, but they can exchange messages using the messaging functions defined in the runtime API.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Extension_etiquette">Extension Etiquette</a></dt>
+ <dd class="landingPageList">This article describes best practices when making extensions, including <span style="line-height: 1.5;">how to be kind to your users.</span><span style="line-height: 1.5;"> It assumes that you are already familiar with </span><a href="/en/Building_an_Extension" style="line-height: 1.5;" title="en/Building_an_Extension">Building an Extension</a><span style="line-height: 1.5;">.</span></dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Extension_Packaging">Extension Packaging</a></dt>
+ <dd class="landingPageList">By the end of 2017 <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions">WebExtensions</a> will be the only supported add-on type in Firefox. To learn how to install a WebExtension for testing purposes, see <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Temporary_Installation_in_Firefox">Temporary Installation in Firefox</a>. To learn how to package a WebExtension for distribution, see <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Publishing_your_WebExtension">Publishing your WebExtension</a>.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/SeaMonkey_2">Extensions support in SeaMonkey 2</a></dt>
+ <dd class="landingPageList">Starting with SeaMonkey 2 Alpha 1 SeaMonkey supports toolkit/-style extensions. These type of extensions have many advantages for both users and developers compared to the old xpinstall/-style extensions.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Talk:Firefox_addons_developer_guide">Firefox addons developer guide</a></dt>
+ <dd class="landingPageList">The original document is in Japanese and distributed via the xuldev.org website. So there may be still some reference to the xuldev website (we want to host source code on MDC, not on xuldev), and to Japanese things (like some specific locales, which have been translated to French since non-latin characters are not well supported).</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Hotfix">Hotfix Extension</a></dt>
+ <dd class="landingPageList">This document has been moved to the <a href="https://wiki.mozilla.org/Add-ons/Hotfix">Add-ons wiki</a>.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/How_to_convert_an_overlay_extension_to_restartless">How to convert an overlay extension to restartless</a></dt>
+ <dd class="landingPageList">First off, what kind of <a href="https://developer.mozilla.org/en-US/Add-ons">add-on</a> are we talking about here? Well, <a href="https://developer.mozilla.org/en-US/docs/XUL_Overlays">XUL overlays</a> and windows, <a href="https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_code_modules">JSM files</a>, <a href="https://developer.mozilla.org/en-US/docs/Chrome_Registration">chrome &amp; resource mappings</a> with localization, default preferences, but <strong>no XPCOM components of your own</strong>. Some of that will have to be replaced and the rest will need to be loaded differently.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Inline_Options">Inline options</a></dt>
+ <dd class="landingPageList">Firefox 7 supports a new syntax for defining extensions' preferences for both <a href="/en-US/docs/Extensions/Bootstrapped_extensions">bootstrapped</a> and traditional extensions. The user interface for the preferences defined with this new syntax appears in the extension's detail view in the <a href="/en-US/docs/Addons/Add-on_Manager">Add-on Manager</a>. This functionality originally appeared in Firefox mobile and is now available in Firefox on the desktop as well.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Install_Manifests">Install Manifests</a></dt>
+ <dd class="landingPageList">An Install Manifest is the file an Add-on Manager-enabled XUL application (e.g. Firefox or Thunderbird) uses to determine information about an add-on as it is being installed. It contains metadata identifying the add-on, providing information about who created it, where more information can be found about it, which versions of what applications it is compatible with, how it should be updated, and so on.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages">Interaction between privileged and non-privileged pages</a></dt>
+ <dd class="landingPageList">An easy way to send data from a web page to an extension is by using custom DOM events. In your extension's browser.xul overlay, write code which listens for a custom DOM event. Here we call the event <code>MyExtensionEvent</code>.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Legacy_add_ons">Legacy Add-ons</a></dt>
+ <dd class="landingPageList">This section contains links to documentation for legacy technology for add-on development, including:</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Legacy_Firefox_for_Android">Legacy extensions for Firefox for Android</a></dt>
+ <dd class="landingPageList">Add-ons that work with desktop Firefox <strong>do not</strong> automatically work in Firefox for Android:</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Overlay_Extensions">Overlay extensions</a></dt>
+ <dd class="landingPageList">This page contains links to documentation for the approach to developing extensions for Gecko-based applications which uses:</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Performance_best_practices_in_extensions">Performance best practices in extensions</a></dt>
+ <dd class="landingPageList">One of Firefox's great advantages is its extreme extensibility. Extensions can do almost anything. There is a down side to this: poorly written extensions can have a severe impact on the browsing experience, including on the overall performance of Firefox itself. This article offers some best practices and suggestions that can not only improve the performance and speed of your extension, but also of Firefox itself.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Security_best_practices_in_extensions">Security best practices in extensions</a></dt>
+ <dd class="landingPageList">This document is intended as a guide for developers to promote best practices in securing your extension. Your goal is to keep your users safe. Some items mentioned are strict guidelines, meaning that if you don't follow them then your add-on will not be approved on Mozilla add-ons. Other items are recommendations. The difference will be clearly flagged.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Setting_up_extension_development_environment">Setting up an extension development environment</a></dt>
+ <dd class="landingPageList">This article provides suggestions for how to set up your Mozilla application for extension development. These details apply to Firefox, Thunderbird, and SeaMonkey (version 2.0 and above).</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Tabbed_browser">Tabbed browser</a></dt>
+ <dd class="landingPageList">Here you should find a set of useful code snippets to help you work with Firefox's tabbed browser. The comments normally mark where you should be inserting your own code.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Techniques">Techniques</a></dt>
+ <dd class="landingPageList">…</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Archive/Add-ons/Working_with_multiprocess_Firefox">Working with multiprocess Firefox</a></dt>
+ <dd class="landingPageList">In older versions of Firefox, chrome code (including code inserted by extensions) and content run in the same operating system process. So extensions can access content directly:</dd>
+</dl>
+
+<p> </p>
diff --git a/files/ms/archive/firefox_os/index.html b/files/ms/archive/firefox_os/index.html
new file mode 100644
index 0000000000..49ba313df7
--- /dev/null
+++ b/files/ms/archive/firefox_os/index.html
@@ -0,0 +1,11 @@
+---
+title: Firefox OS
+slug: Archive/Firefox_OS
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Archive/B2G_OS
+---
+<p class="summary">This page lists archived content for the Firefox OS product, and the open source project it is based on, B2G OS. For current B2G OS material, see the B2G OS page.</p>
+
+<p>{{SubpagesWithSummaries}}</p>
diff --git a/files/ms/archive/index.html b/files/ms/archive/index.html
new file mode 100644
index 0000000000..4f4a70c023
--- /dev/null
+++ b/files/ms/archive/index.html
@@ -0,0 +1,21 @@
+---
+title: Archive of obsolete content
+slug: Archive
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Archive
+---
+<p>Here at MDN, we try to avoid outright deleting content that might be useful to people targeting legacy platforms, operating systems, and browsers. Perhaps your target audience is people that are using older hardware, for example, and can't upgrade to the latest and greatest browsers. Or for "reasons," your company is required to use very old software and you need to build Web content that runs on that software. Or perhaps you're just curious about the history of an obsolete feature or API, and how it worked.</p>
+
+<p>There are many reasons older documentation can be useful. So, we've established this area into which we can archive older documentation. Material in this Archived content zone should <strong>not</strong> be used for building new Web sites or apps for modern browsers. It's here for historical reference only.</p>
+
+<div class="note">
+<p><strong>Note to writers:</strong> We need to try to keep the subpages here organized instead of all dumped into one large folder. Try to create subtrees for categories of material. Also, only move pages here that are <strong>extremely</strong> obsolete. If anyone might realistically need the information in a living product, it may not be appropriate to move it here. In general, it may be best to discuss it in the <a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">MDN Web Docs chat room</a> before moving content here.</p>
+</div>
+
+<p>{{SubpagesWithSummaries}}</p>
+
+<h2 id="Subnav">Subnav</h2>
+
+<p>{{ListSubpages("/en-US/docs/Archive", 2, 0, 1)}}</p>
diff --git a/files/ms/archive/mozilla/firefox/index.html b/files/ms/archive/mozilla/firefox/index.html
new file mode 100644
index 0000000000..7b83b61e7a
--- /dev/null
+++ b/files/ms/archive/mozilla/firefox/index.html
@@ -0,0 +1,13 @@
+---
+title: Firefox
+slug: Archive/Mozilla/Firefox
+tags:
+  - Archive
+  - Firefox
+  - NeedsTranslation
+  - TopicStub
+translation_of: Archive/Mozilla/Firefox
+---
+<p>Out-of-date information about the Firefox project.</p>
+
+<p>{{SubpagesWithSummaries}}</p>
diff --git a/files/ms/archive/mozilla/firefox/jss_build_instructions_for_mac_os_x_10.6/index.html b/files/ms/archive/mozilla/firefox/jss_build_instructions_for_mac_os_x_10.6/index.html
new file mode 100644
index 0000000000..df09c15aba
--- /dev/null
+++ b/files/ms/archive/mozilla/firefox/jss_build_instructions_for_mac_os_x_10.6/index.html
@@ -0,0 +1,54 @@
+---
+title: JSS build instructions for OSX 10.6
+slug: Archive/Mozilla/Firefox/JSS_build_instructions_for_Mac_OS_X_10.6
+tags:
+  - nth
+translation_of: Archive/Mozilla/Firefox/JSS_build_instructions_for_Mac_OS_X_10.6
+---
+<p>The following build instructions were provided by PAVRW. The generic instructions didn't work to build on OSX 10.6.7.</p>
+
+<h2 id="HOWTO_successfully_compile_JSS_and_NSS_for_32_and_64_bits_on_OSX_10.6_(10.6.7)">HOWTO successfully compile JSS and NSS for 32 and 64 bits on OSX 10.6 (10.6.7)</h2>
+
+<h3 id="USEFUL_LINKS">USEFUL LINKS:</h3>
+
+<ul>
+ <li>https://developer.mozilla.org/en/NSS_reference/Building_and_installing_NSS/Build_instructions</li>
+ <li>https://developer.mozilla.org/jss_build_4.3.html</li>
+ <li><a class="link-ftp" href="ftp://ftp.mozilla.org/pub/mozilla.org/" rel="freelink">ftp://ftp.mozilla.org/pub/mozilla.org/</a> &lt;componente&gt; /releases</li>
+ <li><a class="external" href="http://www.mozilla.org/projects/security/pki/jss/using_jss.html" rel="freelink">http://www.mozilla.org/projects/secu...using_jss.html</a></li>
+</ul>
+
+<h3 id="STEPS">STEPS:</h3>
+
+<p>Export all this:</p>
+
+<p>  BUILD_OPT="1"<br>
+   CVSROOT=":pserver:<a class="link-mailto" href="mailto:anonymous@cvs-mirror.mozilla.org" rel="freelink">anonymous@cvs-mirror.mozilla.org</a>:/cvsroot"<br>
+   JAVA_HOME=$(/usr/libexec/java_home")<br>
+   NO_MDUPDATE="1"<br>
+   NSDISTMODE="copy"<br>
+   NS_USE_GCC="1"</p>
+
+<p>Create working dir:<br>
+   mkdir nss-jss<br>
+   cd nss-jss</p>
+
+<p>Obtain source:<br>
+ Altought manual said NSPR_4_6_4_RTM, NSS_3_11_4_RTM, JSS_4_2_5_RTM, they didnt work for OSX, giving many compiling errors. <br>
+   cvs login<br>
+   cvs co -r NSPR_4_8_7_RTM NSPR<br>
+   cvs co -r NSS_3_12_9_WITH_CKBI_1_82_RTM NSS<br>
+   cvs co -r JSS_4_3_2_RTM JSS</p>
+
+<p>Build NSS for 32 and 64: <br>
+   cd mozilla/security/nss<br>
+   make nss_build_all CC="gcc -arch i386" CCC="g++ -arch i386"<br>
+   make nss_build_all USE_64=1</p>
+
+<p>Build JSS for 32 and 64:<br>
+   cd ../jss<br>
+   make CC="gcc -arch i386" CCC="g++ -arch i386"<br>
+   make USE_64=1</p>
+
+<p><br>
+ on OSX, java.library.path doesnt seem to have /usr/lib or other paths. Temporal solution: copy libs to java dir /usr/lib/java. Setting LD_LIBRARY_PATH didnt work</p>
diff --git a/files/ms/archive/mozilla/index.html b/files/ms/archive/mozilla/index.html
new file mode 100644
index 0000000000..0acec76e6d
--- /dev/null
+++ b/files/ms/archive/mozilla/index.html
@@ -0,0 +1,10 @@
+---
+title: Archived Mozilla and build documentation
+slug: Archive/Mozilla
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Archive/Mozilla
+---
+<p>These articles are archived, obsolete documents about Mozilla, Gecko, and the process of building Mozilla projects.</p>
+<p>{{SubpagesWithSummaries}}</p>