You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by db...@apache.org on 2015/09/19 02:05:52 UTC
[2/2] docs commit: Moving docs README.md.
Moving docs README.md.
Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/66ea750c
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/66ea750c
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/66ea750c
Branch: refs/heads/cordova-website
Commit: 66ea750c02c533c5891ab03bba058292b48e3a96
Parents: 36f7280
Author: Dmitry Blotsky <dm...@gmail.com>
Authored: Fri Sep 18 17:05:41 2015 -0700
Committer: Dmitry Blotsky <dm...@gmail.com>
Committed: Fri Sep 18 17:05:41 2015 -0700
----------------------------------------------------------------------
doc/README/de/README.md | 107 ++++++++++++++++
doc/README/en/README.md | 259 ++++++++++++++++++++++++++++++++++++++
doc/README/es/README.md | 107 ++++++++++++++++
doc/README/fr/README.md | 107 ++++++++++++++++
doc/README/it/README.md | 107 ++++++++++++++++
doc/README/ja/README.md | 107 ++++++++++++++++
doc/README/ko/README.md | 107 ++++++++++++++++
doc/README/pl/README.md | 107 ++++++++++++++++
doc/README/zh/README.md | 107 ++++++++++++++++
doc/docs-README/de/README.md | 107 ----------------
doc/docs-README/en/README.md | 259 --------------------------------------
doc/docs-README/es/README.md | 107 ----------------
doc/docs-README/fr/README.md | 107 ----------------
doc/docs-README/it/README.md | 107 ----------------
doc/docs-README/ja/README.md | 107 ----------------
doc/docs-README/ko/README.md | 107 ----------------
doc/docs-README/pl/README.md | 107 ----------------
doc/docs-README/zh/README.md | 107 ----------------
18 files changed, 1115 insertions(+), 1115 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/de/README.md
----------------------------------------------------------------------
diff --git a/doc/README/de/README.md b/doc/README/de/README.md
new file mode 100644
index 0000000..90dc430
--- /dev/null
+++ b/doc/README/de/README.md
@@ -0,0 +1,107 @@
+# Dokumentation zum Apache Cordova API
+
+Die JavaScript-API-Dokumentation für [Apache-Cordova](http://cordova.io/).
+
+Die Dokumentation ist unter [docs.cordova.io](http://docs.cordova.io/) verfügbar.
+
+## Dokumentationsformat
+
+Alle [Apache-Cordova](http://cordova.io/) -Dokumentation geschrieben mit [Markdown](http://daringfireball.net/projects/markdown/syntax), eine leichte Markup-Sprache, die in HTML geschrieben werden kann. Markdown bietet eine einfache und flexible Möglichkeit, Cordova Core API und plattformspezifischen APIs zu dokumentieren.
+
+## Dateistruktur
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## Zu der Dokumentation beitragen
+
+### Melden oder ein Problem zu beheben
+
+Wir verwenden [Apache JIRA](https://issues.apache.org/jira/browse/CB)
+
+Übrigens, wiegen Sie! Vielen Dank, dass uns die Dokumentation zu verbessern!
+
+### Mit Hilfe von Git
+
+Sind Sie neu bei Git oder auf GitHub beiträgt?
+
+Wir haben [ein paar Git-Tutorials geschrieben](http://wiki.apache.org/cordova/ContributorWorkflow) , helfen Ihnen den Einstieg mit zu der Dokumentation beitragen.
+
+### Senden von Pull-Anforderungen
+
+Pull-Requests sind willkommen!
+
+Wir bedanken uns für die Nutzung der Thema-Filialen.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### Hinzufügen einer Sprache
+
+Wollen Sie die Apache-Cordova-Dokumentation in einer anderen Sprache? Wir tun es auch! Mit der Unterstützung der [Crowdin](http://crowdin.net/project/cordova)eine Übersetzung und Lokalisierung-Management-Plattform können Übersetzer einloggen, um die einfach zu bedienende Werkzeuge und bieten so viel oder so wenig Übersetzung Unterstützung, wie sie möchten. Wenn Sie, eine andere Sprache bitte Cordova zu unterstützen und einen Beitrag leisten wissen. http://crowdin.net/project/cordova. Einige bewährte Methoden zur Nutzung des Crowdin-Tools finden Sie in unserer Wiki-http://wiki.apache.org/cordova/CordovaTranslations.
+
+Cordova Sprache Administratoren, vergessen Sie nicht folgende Schritte aus:
+
+**1. config.json**
+
+Für jede Sprache und Version gibt es eine `config.json` , die den Namen der Sprache und Zusammenführen von Dateien definiert.
+
+**2. Anpassen der HTML-Vorlage**
+
+Jede Sprache kann die Standard-Vorlage in `Vorlage/Docs/Sprache` überschreiben..
+
+### Redaktionelle Richtlinien
+
+Finden Sie auf Sprache und Verwendung in der Datei `STYLEGUIDE.md` Richtlinien.
+
+## Generierung von Dokumentation mit Node.js
+
+Jetzt konnte die Dokumentation mit Node.js entweder auf Windows oder Linux-Rechner ausgeführt werden.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Einrichten von Node.js
+
+ 1. Gehen Sie auf Node.JS [-Downloadseite](http://nodejs.org/download/)
+ 2. Downloaden Sie und installieren Sie Paket für Ihr Betriebssystem.
+ 3. Kasse dieses mit Git Repository
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. Abhängigkeiten zu installieren. In der Wurzel der geklonten Cordova-Docs-Ordner ausführen
+
+ npm install
+
+
+ 5. Jetzt können Sie in der Lage, zur Erstellung von Dokumentation lokal.
+
+### Schnelle Vorschau
+
+Wenn Sie kleinere Bearbeitungen vornehmen, ist es normalerweise sicher einfach die bearbeitete von Markdown in HTML gerendert. Viele Code-Editoren haben Plugins Markdown für HTML zu rendern, und es gibt eine Handvoll [guter](http://dillinger.io/) online-Redaktion.
+
+Derzeit sind ein Node.JS Skript und [JoDoc-Js](https://github.com/kant2002/jodoc-js) zum Generieren von HTML-Dokumentation.
+
+## Erzeugen einer Version Release
+
+Es gibt eine Rake-Aufgabe und die Version, das Versionsverzeichnis zu generieren und aktualisieren die Rand-Dokumentation.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/en/README.md
----------------------------------------------------------------------
diff --git a/doc/README/en/README.md b/doc/README/en/README.md
new file mode 100644
index 0000000..529ef31
--- /dev/null
+++ b/doc/README/en/README.md
@@ -0,0 +1,259 @@
+Apache Cordova API Documentation
+================================
+
+The JavaScript API documentation for [Apache Cordova](http://cordova.io/).
+
+The documentation is available at [docs.cordova.io](http://docs.cordova.io/).
+
+Documentation Format
+--------------------
+
+All of the [Apache Cordova](http://cordova.io/) documentation is written with [markdown](http://daringfireball.net/projects/markdown/syntax), a lightweight markup language that can be typeset to HTML. Markdown provides a simple and flexible way to document Cordova's core API and platform-specific APIs.
+
+File Structure
+--------------
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+Contributing to the Documentation
+---------------------------------
+
+### Report or Fix an Issue
+
+We use [Apache JIRA](https://issues.apache.org/jira/browse/CB)
+
+By the way, you rock! Thanks for helping us improve the documentation!
+
+### Using Git
+
+Are you new to Git or contributing on GitHub?
+
+We have [written a few Git tutorials](http://wiki.apache.org/cordova/ContributorWorkflow)
+to help you get started with contributing to the documentation.
+
+### Sending Pull Requests
+
+Pull requests are welcome!
+
+We appreciate the use of topic branches.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+### Adding a Language
+
+Do you want the Apache Cordova documentation in another language? We do too!
+With the support of [Crowdin](http://crowdin.net/project/cordova),
+a translation and localization management platform, translators can login to
+the easy-to-use tooling and provide as much or as little translation assistance as
+they would like. If you know another language please support Cordova and contribute.
+http://crowdin.net/project/cordova. For some best practices for using the
+Crowdin tool please see our wiki http://wiki.apache.org/cordova/CordovaTranslations.
+
+Cordova language administrators, don't forget these steps:
+
+__1. config.json__
+
+For each language and version, there is a `config.json` that defines the name of the language and
+how to merge the files.
+
+__2. Customizing HTML template__
+
+Each language can override the default template in `template/docs/LANGUAGE`.
+
+### Editorial Guidelines
+
+Please see the `STYLEGUIDE.md` file for guidelines on language and usage.
+
+## Generating Documentation with Node.js
+
+Right now documentation could be run using Node.js either on Windows, or on Linux box.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+### Setting up Node.js
+
+1. Go to Node.JS [downloads page](http://nodejs.org/download/)
+2. Download and install package for your operation system.
+3. Checkout this repository using Git
+
+ git clone https://github.com/apache/cordova-docs
+
+4. Install dependencies. In the root of the cloned cordova-docs folder run
+
+ npm install
+5. Now you able to build documentation locally.
+
+### Quick Preview
+
+When making minor edits, it is usually safe to simply render the edited from
+Markdown to HTML. Many code editors have plugins to render Markdown to HTML
+and there are a handful of [good](http://dillinger.io/) online editors.
+
+Currently, a Node.JS script and [joDoc-js](https://github.com/kant2002/jodoc-js) are
+used to generate the HTML documentation.
+
+Generating a Version Release
+---------------------------
+
+There is a Rake task to increment the version, generate the version directory, and update the edge documentation.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
+
+QA for docs & translation
+---------------------------
+In order to maintain quality of documentation and translation, following tools could be used.
+
+1. `fixyaml` tool.
+2. `translationreport` tool.
+3. `validatejsdoc` tool.
+
+### FixYaml tool.
+The tool `fixyaml` created to automatically fix YAML headers in the translation files after
+exporting translated content from CrowdIn. Sometimes Crowdin messup with Apache license headers
+and this tool created to fix that.
+
+Usage:
+
+ bin\fixyaml # Runs fixyaml across all docs.
+ bin\fixyaml ru # Runs fixyaml across all Russian docs.
+ bin\fixyaml ru edge # Runs fixyaml on the latest Russian docs.
+ bin\fixyaml ru 5.0.0 # Runs fixyaml on the version 5.0.0 of Russian docs.
+
+### Translation Report tool.
+The tool `translationreport` currently provide two QA checks for translation.
+1. It verifies that autolinking works after translation, and that translated text point to the same pages as
+in the original documentation.
+2. It verifies that translated and original files create same DOM structure, since after exporting from
+Crowdin, the markdown files could contain unnescessary lines, which lead to broken HTML, and could create
+not needed code sections for example.
+
+### Validate JSDoc tool.
+The tool `validatejsdoc` allow verification of the current implementation of JSDoc with reference implementation.
+It was used during porting JSDoc to the Node version of JSDoc, and now currently not used in the workflow.
+
+Recommendations for the translators
+-------------------------
+If you intend to create quality translation of the Cordova docs, please not only
+work in Crowdin and translate documentation, but also please go extra mile and verify that
+generated documentation for your language is also produce quality results.
+
+For that you should have Crowdin CLI tool. You could
+1. take it from [here](https://crowdin.com/page/cli-tool)
+2. or install alternate NodeJS client
+
+ `npm -g install crowdin-cli`
+
+You will use that tool for the downloading translation from Crowdin.
+To be able to download translated content from the Crowdin you should have API key for the project.
+Please ask for it on the mailing list.
+
+After you receive access to API key, create `crowdin.yaml` coniguration file, as described in the [CrowdIn cli tool page](https://crowdin.com/page/cli-tool).
+
+Now you ready to download content from CrowdIn.
+Run following commands (All commands here would be for NodeJS version of Crowdin CLI)
+
+1. Prepare translated content for downloading.
+
+ `crowdin-cli export`
+
+ This command collect latest translations and made them available for downloading. Without that command, the translation which you would download would be stalled.
+ Be careful with this command, since Crowdin implement throttling and allow you export content not faster then 1 time in 30 minutes, or so.
+2. Download content for you language. I will use Russian as example.
+
+ `crowdin-cli download -l ru -o ru.zip`
+
+ This command download all translations for Russian language to the `ru.zip` file.
+
+3. Now unpack the download content to the temporary directory.
+
+ `unzip -x ru.zip -d tmp/ru`
+
+4. Copy the unpacked content to the `docs` folder.
+
+ a) on Linux:
+ `cp tmp/ru/cordova-docs/docs/ru/edge/* docs/ru/edge/`
+
+ b) on Windows:
+ `xcopy tmp/ru/cordova-docs/docs/ru/edge/* docs/ru/edge/`
+
+5. Remove temporary directory. In my case `tmp/ru`.
+
+ Now you have fresh translation and could generate content.
+
+6. Fix Yaml headers by running.
+
+ `bin/fixyaml ru edge`
+
+7. Run generator. You should generate both English version and language which you tranlate.
+
+ ```
+ bin/genjs en edge
+ bin/genjs ru edge
+ ```
+
+ The generated documentation contains in the `public/en/edge` and `public/ru/edge`
+
+ You need both versions, to validate that translated docs would have same structure as original documentation.
+
+8. Validate you translation.
+
+ `bin/translationreport ru edge`
+
+ This will give you list of files which has structural differences from the original docs.
+ Below the example output:
+ ```
+ => Validating translation for version edge on language ru...
+ Comparing C:\Users\kant\Documents\GitHub\cordova-docs\public\en\edge
+ with C:\Users\kant\Documents\GitHub\cordova-docs\public\ru\edge
+ Path guide_platforms_blackberry10_upgrade.md.html is different.
+ Path guide_platforms_blackberry_upgrade.md.html is different.
+ Path guide_platforms_ios_tools.md.html is different.
+ Path guide_support_index.md.html is different.
+ ```
+
+9. Now you could open pregenerated files and compare the English version with your translated versions.
+ Open both versions and find out what's wrong.
+
+ If on the first sight you could not find the differences, you could add switch `-v` which will increase verbosity of the tool.
+ For example:
+
+ `bin/translationreport ru edge -v`
+
+10. Currently there two type of errors reported:
+
+ a. Missing or additional links.
+
+ b. The broken HTML structure.
+
+11. Let's fix first type of errors - Missing/Additional links.
+ To fix these type of errors you have to make sure that text in your translation where you want to have link,
+ match exactly the header in the translated document, otherwise auto-linking would not work.
+ You have to rephrase the sentences to fix that.
+
+12. Broken HTML DOM structure.
+
+ Most likely this type of errors caused by the additional lines created by Crowdin during export.
+ You have to manually spot these places and remove additional lines when needed and then commit your changes to Git.
+ Most likely these erorrs reappear after next exprot from CrowdIn, so don't hunt for these errors until release, or create
+ tool which will fix these error after each export and use it.
+
+13. Now you ready to create pull request with documentation to the main `crodova-docs` repository.
+
+Enjoy translation!!!
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/es/README.md
----------------------------------------------------------------------
diff --git a/doc/README/es/README.md b/doc/README/es/README.md
new file mode 100644
index 0000000..8423a0f
--- /dev/null
+++ b/doc/README/es/README.md
@@ -0,0 +1,107 @@
+# Documentación de Cordova API de Apache
+
+La documentación de la API de JavaScript para [Apache Cordova](http://cordova.io/).
+
+La documentación está disponible en [docs.cordova.io](http://docs.cordova.io/).
+
+## Formato de documentación
+
+Toda la documentación de [Apache Cordova](http://cordova.io/) escrito con [descuento](http://daringfireball.net/projects/markdown/syntax), un lenguaje de marcado ligero que se puede tipografiar en HTML. Descuento proporciona una manera simple y flexible para documentar base de Cordova API y API específicas de la plataforma.
+
+## Estructura del archivo
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## Contribuir a la documentación
+
+### Informe o solucionar un problema
+
+Usamos [JIRA de Apache](https://issues.apache.org/jira/browse/CB)
+
+Por cierto, rock! ¡ Gracias por ayudarnos a mejorar la documentación!
+
+### Usando Git
+
+¿Eres nuevo en Git o contribuyendo en GitHub?
+
+Tenemos [algunos tutoriales de Git por escrito](http://wiki.apache.org/cordova/ContributorWorkflow) para ayudarle a comenzar a contribuir a la documentación.
+
+### Envío de solicitudes de extracción
+
+Las solicitudes de extracción son bienvenidas!
+
+Apreciamos el uso de las ramas del tema.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### Añadir un idioma
+
+¿Quieres la documentación de Apache Cordova en otro idioma? Hacemos demasiado! Con el apoyo de la plataforma de gestión de [Crowdin](http://crowdin.net/project/cordova), una traducción y localización, traductores pueden acceder a las herramientas de fácil uso y ofrecen como mucho o como poco ayuda de la traducción como ellos quisieran. Si sabes otro idioma por favor apoyar Cordova y contribuir. http://crowdin.net/project/cordova. Algunas mejores prácticas para el uso de la herramienta de Crowdin consulte en nuestra wiki http://wiki.apache.org/cordova/CordovaTranslations.
+
+Administradores de lenguaje de Cordova, no olvides estos pasos:
+
+**1. config.json**
+
+Para cada idioma y versión, hay un `config.json` que define el nombre de la lengua y cómo combinar los archivos.
+
+**2. personalización de plantilla HTML**
+
+Cada idioma puede reemplazar la plantilla por defecto en el `Lenguaje de plantillas de documentos`.
+
+### Pautas editoriales
+
+Consulte el archivo `STYLEGUIDE.md` para las pautas en el lenguaje y el uso.
+
+## Generar documentación con Node.js
+
+Ahora se podía ejecutar documentación usando Node.js en Windows o en Linux box.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Configuración de Node.js
+
+ 1. Ir a Node.JS [descargas página](http://nodejs.org/download/)
+ 2. Descargar e instalar el paquete para su sistema operativo.
+ 3. Retirada este repositorio usando Git
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. Instalar dependencias. En la raíz de la carpeta clonada cordova-docs ejecutar
+
+ npm install
+
+
+ 5. Ahora usted es capaz de construir documentación localmente.
+
+### Vista previa rápida
+
+Al hacer modificaciones menores, es generalmente seguro simplemente prestar el editado de descuento a HTML. Muchos editores de código tienen plugins para hacer descuento a HTML y hay un puñado de [buenos](http://dillinger.io/) editores en línea.
+
+Actualmente, se utilizan un script de Node.JS y [joDoc-js](https://github.com/kant2002/jodoc-js) para generar la documentación HTML.
+
+## Generando una versión
+
+Hay una tarea de Rake para incrementar la versión, generar el directorio de versión y actualizar la documentación de borde.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/fr/README.md
----------------------------------------------------------------------
diff --git a/doc/README/fr/README.md b/doc/README/fr/README.md
new file mode 100644
index 0000000..bea3b67
--- /dev/null
+++ b/doc/README/fr/README.md
@@ -0,0 +1,107 @@
+# Apache Cordova API Documentation
+
+La documentation de l'API JavaScript pour [Apache Cordova](http://cordova.io/).
+
+La documentation est disponible à [docs.cordova.io](http://docs.cordova.io/).
+
+## Format de documentation
+
+Toute la documentation [Apache Cordova](http://cordova.io/) est écrit avec [markdown](http://daringfireball.net/projects/markdown/syntax), un langage de balisage léger qui peut être composé au format HTML. Markdown offre un moyen simple et flexible pour documenter le noyau de Cordova API et API spécifique à la plateforme.
+
+## Structure des fichiers
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## Contribuer à la Documentation
+
+### Rapport ou résoudre un problème
+
+Nous utilisons [JIRA Apache](https://issues.apache.org/jira/browse/CB)
+
+Par ailleurs, vous bercer ! Merci de nous aider à améliorer la documentation !
+
+### À l'aide de Git
+
+Vous êtes nouveau sur Git ou contribuer sur GitHub ?
+
+Nous avons [écrit quelques Git tutoriaux](http://wiki.apache.org/cordova/ContributorWorkflow) pour vous aider à commencer à contribuer à la documentation.
+
+### Envoyer des demandes de Pull
+
+Requêtes d'extraction sont les bienvenus !
+
+Nous apprécions l'utilisation des branches du sujet.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### Ajout d'une langue
+
+Voulez-vous la documentation Apache Cordova, dans une autre langue ? Nous faisons aussi ! Avec le soutien de la plateforme de gestion de [Crowdin](http://crowdin.net/project/cordova), une traduction et de localisation, traducteurs peuvent vous connecter à l'outillage facile à utiliser et fournissent autant ou aussi peu d'assistance traduction comme ils le voudraient. Si vous connaissez une autre langue s'il vous plaît soutenir Cordova et contribuer. http://crowdin.net/project/cordova. Pour certaines meilleures pratiques pour utiliser l'outil Crowdin, veuillez consulter notre wiki http://wiki.apache.org/cordova/CordovaTranslations.
+
+Administrateurs de langue de Cordova, n'oubliez pas les étapes suivantes :
+
+**1. config.json**
+
+Pour chaque langue et chaque version, il y a un `config.json` qui définit le nom de la langue et comment fusionner les fichiers.
+
+**2. personnalisation de modèle HTML**
+
+Chaque langue peut remplacer le modèle par défaut dans le `template/docs/LANGUAGE`.
+
+### Règles éditoriales
+
+S'il vous plaît voir le fichier `STYLEGUIDE.md` pour connaître les instructions sur l'utilisation et de la langue.
+
+## Génération de Documentation avec Node.js
+
+Ce moment documentation pouvait être exécutée à l'aide de Node.js sur GNU / Linux ou sous Windows.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Mise en place de Node.js
+
+ 1. Aller à Node.JS [téléchargements de page](http://nodejs.org/download/)
+ 2. Téléchargez et installez le paquet pour votre système d'exploitation.
+ 3. Commander ce référentiel à l'aide de Git
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. Installer les dépendances. Dans la racine du dossier clonés cordova-docs exécuter
+
+ npm install
+
+
+ 5. Maintenant vous en mesure de construire la documentation localement.
+
+### Aperçu rapide
+
+Lorsque vous effectuez des modifications mineures, il est généralement sans danger pour simplement rendre l'édité de Markdown au format HTML. De nombreux éditeurs de code ont plugins pour restituer Markdown en HTML et il ya une poignée de [bons](http://dillinger.io/) rédacteurs en ligne.
+
+Actuellement, un script de Node.JS et [joDoc-js](https://github.com/kant2002/jodoc-js) sont utilisés pour générer la documentation HTML.
+
+## Génération d'une Version Release
+
+Il y a une tâche de Rake pour incrémenter la version, générer le répertoire de version et mettre à jour la documentation de bord.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/it/README.md
----------------------------------------------------------------------
diff --git a/doc/README/it/README.md b/doc/README/it/README.md
new file mode 100644
index 0000000..26e1a28
--- /dev/null
+++ b/doc/README/it/README.md
@@ -0,0 +1,107 @@
+# Documentazione di Apache Cordova API
+
+La documentazione API JavaScript per [Apache Cordova](http://cordova.io/).
+
+La documentazione è disponibile presso [docs.cordova.io](http://docs.cordova.io/).
+
+## Formato della documentazione
+
+Tutta la documentazione di [Apache Cordova](http://cordova.io/) è scritto con [markdown](http://daringfireball.net/projects/markdown/syntax), un linguaggio di markup leggero che può essere impaginare in HTML. Markdown consente di documentare il nucleo di Cordova API e API specifiche della piattaforma in modo semplice e flessibile.
+
+## Struttura dei file
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## Contribuire alla documentazione
+
+### Segnalare o risolvere un problema
+
+Utilizziamo [Apache JIRA](https://issues.apache.org/jira/browse/CB)
+
+A proposito, è rock! Grazie per averci aiutato a migliorare la documentazione!
+
+### Uso di Git
+
+Sei nuovo a Git o contribuendo su GitHub?
+
+Abbiamo [scritto un paio di Git tutorial](http://wiki.apache.org/cordova/ContributorWorkflow) per aiutarvi a iniziare a contribuire alla documentazione.
+
+### L'invio di richieste di Pull
+
+Tirare le richieste sono benvenute!
+
+Apprezziamo l'uso dei rami di argomento.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### L'aggiunta di una lingua
+
+Vuoi che la documentazione di Apache Cordova in un'altra lingua? Lo facciamo anche noi! Con il supporto della piattaforma di gestione [Crowdin](http://crowdin.net/project/cordova), traduzione e localizzazione, traduttori collegarti alla lavorazione con utensili di facile da usare e fornire tanto o poichè poca assistenza di traduzione come vorrebbero. Se si conosce un'altra lingua si prega di sostenere Cordova e contribuire. http://crowdin.net/project/cordova. Per alcune procedure consigliate per l'utilizzo lo strumento Crowdin si prega di consultare il nostro wiki http://wiki.apache.org/cordova/CordovaTranslations.
+
+Gli amministratori di lingua di Cordova, non dimenticare questi passaggi:
+
+**1. config**
+
+Per ogni lingua e versione, c'è un `config` che definisce il nome della lingua e come unire i file.
+
+**2. personalizzazione del template HTML**
+
+Ogni lingua può sovrascrivere il template predefinito nella `Lingua/docs/modello`.
+
+### Direttive editoriali
+
+Vedere il file `STYLEGUIDE.md` per le linee guida sull'utilizzo e la lingua.
+
+## La generazione della documentazione con node. js
+
+In questo momento la documentazione potrebbe essere eseguito utilizzando node. js su Windows o su Linux box.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Configurazione di node. js
+
+ 1. Vai a node. js [pagina downloads](http://nodejs.org/download/)
+ 2. Scaricare e installare il pacchetto per il sistema di funzionamento.
+ 3. Check-out questo repository utilizzando Git
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. Installare le dipendenze. Nella radice della cartella clonata cordova-docs eseguita
+
+ npm install
+
+
+ 5. Ora siete in grado di generare documentazione locale.
+
+### Anteprima rapida
+
+Quando si apportano le modifiche minori, è solitamente sicuro semplicemente rendere il modificato da Markdown a HTML. Molti editor di codice sono plugin per eseguire il rendering HTML Markdown e ci sono una manciata di [buoni](http://dillinger.io/) editor online.
+
+Attualmente, un node. js script e [joDoc-js](https://github.com/kant2002/jodoc-js) vengono utilizzati per generare la documentazione HTML.
+
+## Generazione di una rilascio di versione
+
+C'è un compito di Rake per incrementare il numero di versione, la directory della versione di generare e aggiornare la documentazione di bordo.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/ja/README.md
----------------------------------------------------------------------
diff --git a/doc/README/ja/README.md b/doc/README/ja/README.md
new file mode 100644
index 0000000..be95c11
--- /dev/null
+++ b/doc/README/ja/README.md
@@ -0,0 +1,107 @@
+# Apache コルドバ API ドキュメント
+
+[Apache コルドバ](http://cordova.io/)の JavaScript API ドキュメント.
+
+マニュアルは、 [docs.cordova.io](http://docs.cordova.io/).
+
+## ドキュメントの形式
+
+すべての[Apache コルドバ](http://cordova.io/)ドキュメントは[値下げ](http://daringfireball.net/projects/markdown/syntax)HTML にタイプセットすることができます軽量マークアップ言語で書き込まれます。 値下げは、コルドバのコア API やプラットフォーム固有の Api を文書化する簡単かつ柔軟な方法を提供します。
+
+## ファイル構造
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## ドキュメントに貢献
+
+### 問題を修正または報告
+
+我々 は、 [Apache JIRA](https://issues.apache.org/jira/browse/CB)を使用してください。
+
+ところで、あなたは揺れ動きます!ドキュメントの改善にご協力いただきありがとうございます!
+
+### Git を使ってください。
+
+あなたは Git または GitHub に貢献する新しいですか。
+
+我々 が[書かれていくつかの Git チュートリアル](http://wiki.apache.org/cordova/ContributorWorkflow)ドキュメントに貢献を始めるため。
+
+### プル要求を送信します。
+
+プルリクエストは大歓迎です!
+
+トピック ブランチの使用お願い申し上げます。
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### 言語を追加します。
+
+別の言語で Apache コルドバ ドキュメントですか? 我々 はあまりにも行う! [Crowdin](http://crowdin.net/project/cordova)、翻訳およびローカリゼーション管理プラットフォームのサポート、翻訳は簡単に使用できるツールにログインし、彼らのようで、少し翻訳支援を提供できます。 場合してくださいコルドバをサポートし、貢献する別の言語を知っています。 http://crowdin.net/project/cordova. Crowdin ツールを使用してのいくつかのベスト プラクティスは、私たちの wiki の http://wiki.apache.org/cordova/CordovaTranslations を参照してください。
+
+コルドバ言語管理者は、これらの手順を忘れてはいけない。
+
+**1. config.json**
+
+各言語およびバージョン、言語とファイルをマージする方法の名前を定義する`config.json`があります。
+
+**2. HTML テンプレートをカスタマイズします。**
+
+各言語の`テンプレート/ドキュメント/言語`で既定のテンプレートをオーバーライドできます。.
+
+### 編集ガイドライン
+
+言語および使用に関するガイドラインの`STYLEGUIDE.md`ファイルを参照してください。
+
+## Node.js のドキュメントを生成します。
+
+今、Windows または Linux ボックスのいずれか、Node.js を使用してドキュメントを実行でした。
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Node.js を設定
+
+ 1. Node.JS[のダウンロード ページ](http://nodejs.org/download/)へ
+ 2. ダウンロードして、あなたの操作システムにパッケージをインストールします。
+ 3. チェック アウトこのリポジトリは Git を使って
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. 依存関係をインストールします。実行クローン コルドバ docs フォルダーのルートに
+
+ npm install
+
+
+ 5. 今ローカルでドキュメントをビルドすることができます。
+
+### クイック プレビュー
+
+細部の編集の際、通常単に HTML に値下げから編集レンダリングしても安全です。 多くのコード エディターは、記法を HTML に表示するプラグインを持っているし、[良い](http://dillinger.io/)オンライン編集者の一握りがあります。
+
+現在、Node.JS スクリプトと[joDoc js](https://github.com/kant2002/jodoc-js)を使用して HTML ドキュメントを生成します。
+
+## バージョンのリリースを生成します。
+
+バージョンをインクリメント、バージョン、ディレクトリを生成し、エッジのマニュアルを更新する Rake タスクがあります。
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/ko/README.md
----------------------------------------------------------------------
diff --git a/doc/README/ko/README.md b/doc/README/ko/README.md
new file mode 100644
index 0000000..fd20233
--- /dev/null
+++ b/doc/README/ko/README.md
@@ -0,0 +1,107 @@
+# 아파치 코르도바 API 설명서
+
+[아파치 Cordova](http://cordova.io/) 에 대 한 JavaScript API 설명서.
+
+설명서는 [docs.cordova.io](http://docs.cordova.io/) 에서 사용할 수.
+
+## 문서 형식
+
+모든 [아파치 코르도바](http://cordova.io/) 문서 [markdown](http://daringfireball.net/projects/markdown/syntax), HTML로 활자 수는 가벼운 마크업 언어와 함께 기록 됩니다. Markdown은 코르도바의 핵심 API 및 플랫폼 특정 Api를 문서화 하는 간단 하 고 유연한 방법을 제공 합니다.
+
+## 파일 구조
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## 설명서에 기여
+
+### 신고 또는 문제 해결
+
+우리는 [아파치 JIRA](https://issues.apache.org/jira/browse/CB) 사용
+
+그건 그렇고, 당신은 바위! 설명서를 개선 하는 데 도움을 주셔서 감사!
+
+### Git를 사용 하 여
+
+당신은 새로운 자식 또는 GitHub에 기여?
+
+우리는 [몇 가지 Git 튜토리얼 작성](http://wiki.apache.org/cordova/ContributorWorkflow) 설명서에 기여와 함께 시작할 수 있도록.
+
+### 끌어오기 요청을 보내는
+
+끌어오기 요청은 환영 합니다!
+
+항목 지점의 사용 부탁 드립니다.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### 언어 추가
+
+다른 언어에서 아파치 코르도바 설명서 보기 우리는 너무 해! [Crowdin](http://crowdin.net/project/cordova), 번역 및 로컬라이제이션 관리 플랫폼의 지원, 번역 수 사용 하기 쉬운 툴에 로그인 하 고 그들이 했던 것 처럼 작은 번역 지원을 제공. 당신이 알고 있다면 다른 언어 코르도바를 지원 하 고 기여 하십시오. http://crowdin.net/project/cordova. Crowdin 도구를 사용 하 여에 대 한 몇 가지 모범 사례에 대 한 우리의 위 키 http://wiki.apache.org/cordova/CordovaTranslations를 참조 하십시오.
+
+코르도바 언어 관리자는 다음이 단계를 잊지 마세요:
+
+**1입니다. config.json**
+
+각 언어 및 버전에 대 한 파일을 병합 하는 방법과 언어의 이름을 정의 하는 `config.json` 입니다.
+
+**2. 사용자 지정 HTML 서식 파일**
+
+각 언어 `서식 파일/문서/언어` 에서 기본 서식 파일을 재정의할 수 있습니다..
+
+### 광고문 안 가이드
+
+언어 및 사용에 대 한 `STYLEGUIDE.md` 파일을 참조 하십시오.
+
+## Node.js 함께 문서 생성
+
+지금 문서 Windows, 또는 리눅스 상자에 Node.js를 사용 하 여 실행할 수 있습니다.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Node.js를 설정
+
+ 1. Node.JS [다운로드 페이지](http://nodejs.org/download/) 이동
+ 2. 다운로드 및 운영 체제에 대 한 패키지를 설치 합니다.
+ 3. 체크 아웃 Git를 사용 하 여이 저장소
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. 종속성을 설치 합니다. 실행 복제 코르도바-오피스 폴더의 루트에
+
+ npm install
+
+
+ 5. 지금 당신은 로컬로 문서를 만들 수입니다.
+
+### 빠른 미리 보기
+
+사소한 편집 때, 그것은 일반적으로 간단 하 게 렌더링 하는 편집 Markdown에서 HTML로 안전입니다. 많은 코드 에디터는 Markdown HTML로 렌더링 하는 플러그인 그리고 [좋은](http://dillinger.io/) 온라인 편집자의 한 줌 있다.
+
+현재, Node.JS 스크립트와 [joDoc js](https://github.com/kant2002/jodoc-js) HTML 문서를 생성 하 데 사용 됩니다.
+
+## 생성 버전 출시
+
+버전 디렉터리를 생성 하 버전 증가 가장자리 설명서를 업데이트 레이크 작업이입니다.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/pl/README.md
----------------------------------------------------------------------
diff --git a/doc/README/pl/README.md b/doc/README/pl/README.md
new file mode 100644
index 0000000..9051ba0
--- /dev/null
+++ b/doc/README/pl/README.md
@@ -0,0 +1,107 @@
+# Apache Cordova API Documentation
+
+Dokumentacja JavaScript API dla [Apache Cordova](http://cordova.io/).
+
+Dokumentacja jest dostępna na [docs.cordova.io](http://docs.cordova.io/).
+
+## Format dokumentacji
+
+Całą dokumentację, [Apache Cordova](http://cordova.io/) jest napisany z [promocji cenowych](http://daringfireball.net/projects/markdown/syntax), język znaczników, które mogą być składane do HTML. Markdown zapewnia prosty i elastyczny sposób do dokumentu rdzeń Cordova w API i API platformy.
+
+## Struktura pliku
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## Przyczyniając się do dokumentacji
+
+### Raport lub rozwiązać problem
+
+Używamy [Apache JIRA](https://issues.apache.org/jira/browse/CB)
+
+Mimochodem ty skała! Dzięki za pomoc nam poprawić dokumentację!
+
+### Za pomocą Git
+
+Czy jesteś nowym Git lub przyczyniających się na GitHub?
+
+Mamy [napisane kilka tutoriali Git](http://wiki.apache.org/cordova/ContributorWorkflow) , które pomogą Ci rozpocząć pracę z przyczyniając się do dokumentacji.
+
+### Wysyłanie żądań Pull
+
+Wyciągnąć wnioski są mile widziane!
+
+Dziękujemy za korzystanie z gałęzi tematycznych.
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### Dodanie języka
+
+Czy chcesz, aby Apache Cordova dokumentacji w innym języku? Robimy też! Przy wsparciu [Crowdin](http://crowdin.net/project/cordova), tłumaczenie i lokalizacja platformy zarządzania tłumaczy można zalogować się łatwy wobec używać narzędzi i zapewnić jak dużo lub za mało tłumaczenie pomocy, jak chcą. Jeśli znasz inny język, prosimy o wsparcie Cordova i przyczynić się. http://crowdin.net/project/cordova. Niektóre najważniejsze wskazówki dotyczące korzystania z narzędzia Crowdin Zobacz nasze wiki http://wiki.apache.org/cordova/CordovaTranslations.
+
+Cordova język Administratorzy, nie zapomnij następujące kroki:
+
+**1. config.json**
+
+Dla każdego języka i wersji jest `config.json` , która określa nazwę języka oraz jak scalić pliki.
+
+**2. dostosowywanie szablonu HTML**
+
+Każdy język można zastąpić domyślny szablon w `Język szablonu/dokumenty`.
+
+### Wskazówkami redakcyjnymi
+
+Zobacz plik `STYLEGUIDE.md` do wytycznych na język i sposób użycia.
+
+## Generowanie dokumentacji z Node.js
+
+Już teraz dokumentacji mogą być uruchamiane za pomocą Node.js na Windows, albo na linux'ie.
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### Definiowanie Node.js
+
+ 1. Przejdź do Node.JS, [pliki do pobrania strony](http://nodejs.org/download/)
+ 2. Pobierz i zainstaluj pakiet dla systemu pracy.
+ 3. Zamówienie to repozytorium za pomocą Git
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. Zainstalować zależności. W głównym folderze sklonowany cordova dokumenty uruchomić
+
+ npm install
+
+
+ 5. Teraz jesteś w stanie budować dokumentacji lokalnie.
+
+### Szybki podgląd
+
+Podczas dokonywania drobnych zmian, to zazwyczaj po prostu uczynić edytowane z Markdown do HTML. Wiele edytorów kodu masz pluginy do renderowania Markdown do HTML i istnieje kilka [dobrych](http://dillinger.io/) redaktorów online.
+
+Obecnie skrypt Node.JS i [joDoc-js](https://github.com/kant2002/jodoc-js) są używane do generowania dokumentacji HTML.
+
+## Generowanie wersji
+
+Jest zadaniem Rake przyrost wersji, wersji katalogu, i aktualizacji dokumentacji krawędzi.
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/README/zh/README.md
----------------------------------------------------------------------
diff --git a/doc/README/zh/README.md b/doc/README/zh/README.md
new file mode 100644
index 0000000..b65379d
--- /dev/null
+++ b/doc/README/zh/README.md
@@ -0,0 +1,107 @@
+# Apache 科爾多瓦 API 文檔
+
+[Apache 科爾多瓦](http://cordova.io/)JavaScript API 文檔.
+
+該文檔是發售[docs.cordova.io](http://docs.cordova.io/).
+
+## 文檔格式
+
+所有[Apache 科爾多瓦](http://cordova.io/)文檔編寫時[降價](http://daringfireball.net/projects/markdown/syntax)，可以到 HTML 排版的羽量級標記語言。 降價提供了一種簡單而靈活的方式來記錄科爾多瓦的核心 API 和特定于平臺的 Api。
+
+## 檔結構
+
+ docs/
+ docs/LANGUAGE
+ docs/LANGUAGE/VERSION
+ docs/LANGUAGE/VERSION/cordova/
+ docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
+
+
+## 檔作出貢獻
+
+### 報告或解決問題
+
+我們使用[Apache JIRA](https://issues.apache.org/jira/browse/CB)
+
+順便說一句，你搖滾!感謝您説明我們改進文檔!
+
+### 使用 Git
+
+你是新到 Git 或在 GitHub 上作出貢獻?
+
+我們要[寫幾個 Git 教程](http://wiki.apache.org/cordova/ContributorWorkflow)説明您開始使用檔作出貢獻。
+
+### 發送的請求
+
+請求，歡迎!
+
+我們欣賞主題設立分支機搆。
+
+ git checkout -b issue_23
+
+ # code
+
+ git commit -m "Issue 23: Fix a bad bug."
+
+ git push origin issue_23
+
+ # send pull request from branch issue_23 to cordova:master
+
+
+### 添加一種語言
+
+你想要另一種語言中的 Apache 科爾多瓦文檔嗎? 我們也做了! [Crowdin](http://crowdin.net/project/cordova)、 翻譯和當地語系化管理平臺的支援下，譯者可以登錄到使用方便模具並提供作為多或少的翻譯協助，會像他們。 如果你知道請支援科爾多瓦和作出貢獻的另一種語言。 http://crowdin.net/project/cordova. 使用 Crowdin 工具的一些最佳做法，請參閱我們的 wiki HTTP://wiki.apache.org/cordova/CordovaTranslations。
+
+科爾多瓦語言管理員，別忘了這些步驟:
+
+**1.config.json**
+
+對於每種語言和版本，還有`config.json`所定義的語言以及如何合併的檔的名稱。
+
+**2.自訂 HTML 範本**
+
+每一種語言可以重寫預設範本在`templates/docs/LANGUAGE`.
+
+### 編輯指南
+
+請參閱準則`STYLEGUIDE.md`檔的語言和使用方式。
+
+## 生成文檔與 Node.js
+
+現在，文檔可以使用 Node.js，Windows，或 Linux 機器上運行。
+
+ $ rm -r tmp public # Clear out old docs
+ $ ./bin/genjs # compile all docs
+ $ ./bin/genjs en edge # compile English Edge docs
+ $ ./bin/genjs ru edge # compile Russian Edge docs
+ $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
+
+
+### 設置 Node.js
+
+ 1. 去 Node.JS[下載頁](http://nodejs.org/download/)
+ 2. 下載並安裝包為您的作業系統。
+ 3. 簽出此存儲庫使用 Git
+
+ git clone https://github.com/apache/cordova-docs
+
+
+ 4. 安裝的依賴關係。在運行的克隆的科爾多瓦 docs 資料夾的根目錄
+
+ npm install
+
+
+ 5. 現在，您能夠構建本地文檔。
+
+### 快速預覽
+
+小編輯時，它通常是安全，使 HTML 簡單地編輯從降價。 很多代碼編輯器外掛程式要呈現為 HTML 的降價和有極少數的[好](http://dillinger.io/)線上編輯。
+
+目前，Node.JS 腳本和[joDoc js](https://github.com/kant2002/jodoc-js)用於生成的 HTML 文檔。
+
+## 生成版本
+
+還有 Rake 任務，將版本遞增，生成版本目錄中，並更新邊緣文檔。
+
+ # generate version 4.1.0 for english.
+ .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/de/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/de/README.md b/doc/docs-README/de/README.md
deleted file mode 100644
index 90dc430..0000000
--- a/doc/docs-README/de/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Dokumentation zum Apache Cordova API
-
-Die JavaScript-API-Dokumentation für [Apache-Cordova](http://cordova.io/).
-
-Die Dokumentation ist unter [docs.cordova.io](http://docs.cordova.io/) verfügbar.
-
-## Dokumentationsformat
-
-Alle [Apache-Cordova](http://cordova.io/) -Dokumentation geschrieben mit [Markdown](http://daringfireball.net/projects/markdown/syntax), eine leichte Markup-Sprache, die in HTML geschrieben werden kann. Markdown bietet eine einfache und flexible Möglichkeit, Cordova Core API und plattformspezifischen APIs zu dokumentieren.
-
-## Dateistruktur
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## Zu der Dokumentation beitragen
-
-### Melden oder ein Problem zu beheben
-
-Wir verwenden [Apache JIRA](https://issues.apache.org/jira/browse/CB)
-
-Übrigens, wiegen Sie! Vielen Dank, dass uns die Dokumentation zu verbessern!
-
-### Mit Hilfe von Git
-
-Sind Sie neu bei Git oder auf GitHub beiträgt?
-
-Wir haben [ein paar Git-Tutorials geschrieben](http://wiki.apache.org/cordova/ContributorWorkflow) , helfen Ihnen den Einstieg mit zu der Dokumentation beitragen.
-
-### Senden von Pull-Anforderungen
-
-Pull-Requests sind willkommen!
-
-Wir bedanken uns für die Nutzung der Thema-Filialen.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### Hinzufügen einer Sprache
-
-Wollen Sie die Apache-Cordova-Dokumentation in einer anderen Sprache? Wir tun es auch! Mit der Unterstützung der [Crowdin](http://crowdin.net/project/cordova)eine Übersetzung und Lokalisierung-Management-Plattform können Übersetzer einloggen, um die einfach zu bedienende Werkzeuge und bieten so viel oder so wenig Übersetzung Unterstützung, wie sie möchten. Wenn Sie, eine andere Sprache bitte Cordova zu unterstützen und einen Beitrag leisten wissen. http://crowdin.net/project/cordova. Einige bewährte Methoden zur Nutzung des Crowdin-Tools finden Sie in unserer Wiki-http://wiki.apache.org/cordova/CordovaTranslations.
-
-Cordova Sprache Administratoren, vergessen Sie nicht folgende Schritte aus:
-
-**1. config.json**
-
-Für jede Sprache und Version gibt es eine `config.json` , die den Namen der Sprache und Zusammenführen von Dateien definiert.
-
-**2. Anpassen der HTML-Vorlage**
-
-Jede Sprache kann die Standard-Vorlage in `Vorlage/Docs/Sprache` überschreiben..
-
-### Redaktionelle Richtlinien
-
-Finden Sie auf Sprache und Verwendung in der Datei `STYLEGUIDE.md` Richtlinien.
-
-## Generierung von Dokumentation mit Node.js
-
-Jetzt konnte die Dokumentation mit Node.js entweder auf Windows oder Linux-Rechner ausgeführt werden.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Einrichten von Node.js
-
- 1. Gehen Sie auf Node.JS [-Downloadseite](http://nodejs.org/download/)
- 2. Downloaden Sie und installieren Sie Paket für Ihr Betriebssystem.
- 3. Kasse dieses mit Git Repository
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. Abhängigkeiten zu installieren. In der Wurzel der geklonten Cordova-Docs-Ordner ausführen
-
- npm install
-
-
- 5. Jetzt können Sie in der Lage, zur Erstellung von Dokumentation lokal.
-
-### Schnelle Vorschau
-
-Wenn Sie kleinere Bearbeitungen vornehmen, ist es normalerweise sicher einfach die bearbeitete von Markdown in HTML gerendert. Viele Code-Editoren haben Plugins Markdown für HTML zu rendern, und es gibt eine Handvoll [guter](http://dillinger.io/) online-Redaktion.
-
-Derzeit sind ein Node.JS Skript und [JoDoc-Js](https://github.com/kant2002/jodoc-js) zum Generieren von HTML-Dokumentation.
-
-## Erzeugen einer Version Release
-
-Es gibt eine Rake-Aufgabe und die Version, das Versionsverzeichnis zu generieren und aktualisieren die Rand-Dokumentation.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/en/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/en/README.md b/doc/docs-README/en/README.md
deleted file mode 100644
index 529ef31..0000000
--- a/doc/docs-README/en/README.md
+++ /dev/null
@@ -1,259 +0,0 @@
-Apache Cordova API Documentation
-================================
-
-The JavaScript API documentation for [Apache Cordova](http://cordova.io/).
-
-The documentation is available at [docs.cordova.io](http://docs.cordova.io/).
-
-Documentation Format
---------------------
-
-All of the [Apache Cordova](http://cordova.io/) documentation is written with [markdown](http://daringfireball.net/projects/markdown/syntax), a lightweight markup language that can be typeset to HTML. Markdown provides a simple and flexible way to document Cordova's core API and platform-specific APIs.
-
-File Structure
---------------
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-Contributing to the Documentation
----------------------------------
-
-### Report or Fix an Issue
-
-We use [Apache JIRA](https://issues.apache.org/jira/browse/CB)
-
-By the way, you rock! Thanks for helping us improve the documentation!
-
-### Using Git
-
-Are you new to Git or contributing on GitHub?
-
-We have [written a few Git tutorials](http://wiki.apache.org/cordova/ContributorWorkflow)
-to help you get started with contributing to the documentation.
-
-### Sending Pull Requests
-
-Pull requests are welcome!
-
-We appreciate the use of topic branches.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-### Adding a Language
-
-Do you want the Apache Cordova documentation in another language? We do too!
-With the support of [Crowdin](http://crowdin.net/project/cordova),
-a translation and localization management platform, translators can login to
-the easy-to-use tooling and provide as much or as little translation assistance as
-they would like. If you know another language please support Cordova and contribute.
-http://crowdin.net/project/cordova. For some best practices for using the
-Crowdin tool please see our wiki http://wiki.apache.org/cordova/CordovaTranslations.
-
-Cordova language administrators, don't forget these steps:
-
-__1. config.json__
-
-For each language and version, there is a `config.json` that defines the name of the language and
-how to merge the files.
-
-__2. Customizing HTML template__
-
-Each language can override the default template in `template/docs/LANGUAGE`.
-
-### Editorial Guidelines
-
-Please see the `STYLEGUIDE.md` file for guidelines on language and usage.
-
-## Generating Documentation with Node.js
-
-Right now documentation could be run using Node.js either on Windows, or on Linux box.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-### Setting up Node.js
-
-1. Go to Node.JS [downloads page](http://nodejs.org/download/)
-2. Download and install package for your operation system.
-3. Checkout this repository using Git
-
- git clone https://github.com/apache/cordova-docs
-
-4. Install dependencies. In the root of the cloned cordova-docs folder run
-
- npm install
-5. Now you able to build documentation locally.
-
-### Quick Preview
-
-When making minor edits, it is usually safe to simply render the edited from
-Markdown to HTML. Many code editors have plugins to render Markdown to HTML
-and there are a handful of [good](http://dillinger.io/) online editors.
-
-Currently, a Node.JS script and [joDoc-js](https://github.com/kant2002/jodoc-js) are
-used to generate the HTML documentation.
-
-Generating a Version Release
----------------------------
-
-There is a Rake task to increment the version, generate the version directory, and update the edge documentation.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
-
-QA for docs & translation
----------------------------
-In order to maintain quality of documentation and translation, following tools could be used.
-
-1. `fixyaml` tool.
-2. `translationreport` tool.
-3. `validatejsdoc` tool.
-
-### FixYaml tool.
-The tool `fixyaml` created to automatically fix YAML headers in the translation files after
-exporting translated content from CrowdIn. Sometimes Crowdin messup with Apache license headers
-and this tool created to fix that.
-
-Usage:
-
- bin\fixyaml # Runs fixyaml across all docs.
- bin\fixyaml ru # Runs fixyaml across all Russian docs.
- bin\fixyaml ru edge # Runs fixyaml on the latest Russian docs.
- bin\fixyaml ru 5.0.0 # Runs fixyaml on the version 5.0.0 of Russian docs.
-
-### Translation Report tool.
-The tool `translationreport` currently provide two QA checks for translation.
-1. It verifies that autolinking works after translation, and that translated text point to the same pages as
-in the original documentation.
-2. It verifies that translated and original files create same DOM structure, since after exporting from
-Crowdin, the markdown files could contain unnescessary lines, which lead to broken HTML, and could create
-not needed code sections for example.
-
-### Validate JSDoc tool.
-The tool `validatejsdoc` allow verification of the current implementation of JSDoc with reference implementation.
-It was used during porting JSDoc to the Node version of JSDoc, and now currently not used in the workflow.
-
-Recommendations for the translators
--------------------------
-If you intend to create quality translation of the Cordova docs, please not only
-work in Crowdin and translate documentation, but also please go extra mile and verify that
-generated documentation for your language is also produce quality results.
-
-For that you should have Crowdin CLI tool. You could
-1. take it from [here](https://crowdin.com/page/cli-tool)
-2. or install alternate NodeJS client
-
- `npm -g install crowdin-cli`
-
-You will use that tool for the downloading translation from Crowdin.
-To be able to download translated content from the Crowdin you should have API key for the project.
-Please ask for it on the mailing list.
-
-After you receive access to API key, create `crowdin.yaml` coniguration file, as described in the [CrowdIn cli tool page](https://crowdin.com/page/cli-tool).
-
-Now you ready to download content from CrowdIn.
-Run following commands (All commands here would be for NodeJS version of Crowdin CLI)
-
-1. Prepare translated content for downloading.
-
- `crowdin-cli export`
-
- This command collect latest translations and made them available for downloading. Without that command, the translation which you would download would be stalled.
- Be careful with this command, since Crowdin implement throttling and allow you export content not faster then 1 time in 30 minutes, or so.
-2. Download content for you language. I will use Russian as example.
-
- `crowdin-cli download -l ru -o ru.zip`
-
- This command download all translations for Russian language to the `ru.zip` file.
-
-3. Now unpack the download content to the temporary directory.
-
- `unzip -x ru.zip -d tmp/ru`
-
-4. Copy the unpacked content to the `docs` folder.
-
- a) on Linux:
- `cp tmp/ru/cordova-docs/docs/ru/edge/* docs/ru/edge/`
-
- b) on Windows:
- `xcopy tmp/ru/cordova-docs/docs/ru/edge/* docs/ru/edge/`
-
-5. Remove temporary directory. In my case `tmp/ru`.
-
- Now you have fresh translation and could generate content.
-
-6. Fix Yaml headers by running.
-
- `bin/fixyaml ru edge`
-
-7. Run generator. You should generate both English version and language which you tranlate.
-
- ```
- bin/genjs en edge
- bin/genjs ru edge
- ```
-
- The generated documentation contains in the `public/en/edge` and `public/ru/edge`
-
- You need both versions, to validate that translated docs would have same structure as original documentation.
-
-8. Validate you translation.
-
- `bin/translationreport ru edge`
-
- This will give you list of files which has structural differences from the original docs.
- Below the example output:
- ```
- => Validating translation for version edge on language ru...
- Comparing C:\Users\kant\Documents\GitHub\cordova-docs\public\en\edge
- with C:\Users\kant\Documents\GitHub\cordova-docs\public\ru\edge
- Path guide_platforms_blackberry10_upgrade.md.html is different.
- Path guide_platforms_blackberry_upgrade.md.html is different.
- Path guide_platforms_ios_tools.md.html is different.
- Path guide_support_index.md.html is different.
- ```
-
-9. Now you could open pregenerated files and compare the English version with your translated versions.
- Open both versions and find out what's wrong.
-
- If on the first sight you could not find the differences, you could add switch `-v` which will increase verbosity of the tool.
- For example:
-
- `bin/translationreport ru edge -v`
-
-10. Currently there two type of errors reported:
-
- a. Missing or additional links.
-
- b. The broken HTML structure.
-
-11. Let's fix first type of errors - Missing/Additional links.
- To fix these type of errors you have to make sure that text in your translation where you want to have link,
- match exactly the header in the translated document, otherwise auto-linking would not work.
- You have to rephrase the sentences to fix that.
-
-12. Broken HTML DOM structure.
-
- Most likely this type of errors caused by the additional lines created by Crowdin during export.
- You have to manually spot these places and remove additional lines when needed and then commit your changes to Git.
- Most likely these erorrs reappear after next exprot from CrowdIn, so don't hunt for these errors until release, or create
- tool which will fix these error after each export and use it.
-
-13. Now you ready to create pull request with documentation to the main `crodova-docs` repository.
-
-Enjoy translation!!!
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/es/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/es/README.md b/doc/docs-README/es/README.md
deleted file mode 100644
index 8423a0f..0000000
--- a/doc/docs-README/es/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Documentación de Cordova API de Apache
-
-La documentación de la API de JavaScript para [Apache Cordova](http://cordova.io/).
-
-La documentación está disponible en [docs.cordova.io](http://docs.cordova.io/).
-
-## Formato de documentación
-
-Toda la documentación de [Apache Cordova](http://cordova.io/) escrito con [descuento](http://daringfireball.net/projects/markdown/syntax), un lenguaje de marcado ligero que se puede tipografiar en HTML. Descuento proporciona una manera simple y flexible para documentar base de Cordova API y API específicas de la plataforma.
-
-## Estructura del archivo
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## Contribuir a la documentación
-
-### Informe o solucionar un problema
-
-Usamos [JIRA de Apache](https://issues.apache.org/jira/browse/CB)
-
-Por cierto, rock! ¡ Gracias por ayudarnos a mejorar la documentación!
-
-### Usando Git
-
-¿Eres nuevo en Git o contribuyendo en GitHub?
-
-Tenemos [algunos tutoriales de Git por escrito](http://wiki.apache.org/cordova/ContributorWorkflow) para ayudarle a comenzar a contribuir a la documentación.
-
-### Envío de solicitudes de extracción
-
-Las solicitudes de extracción son bienvenidas!
-
-Apreciamos el uso de las ramas del tema.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### Añadir un idioma
-
-¿Quieres la documentación de Apache Cordova en otro idioma? Hacemos demasiado! Con el apoyo de la plataforma de gestión de [Crowdin](http://crowdin.net/project/cordova), una traducción y localización, traductores pueden acceder a las herramientas de fácil uso y ofrecen como mucho o como poco ayuda de la traducción como ellos quisieran. Si sabes otro idioma por favor apoyar Cordova y contribuir. http://crowdin.net/project/cordova. Algunas mejores prácticas para el uso de la herramienta de Crowdin consulte en nuestra wiki http://wiki.apache.org/cordova/CordovaTranslations.
-
-Administradores de lenguaje de Cordova, no olvides estos pasos:
-
-**1. config.json**
-
-Para cada idioma y versión, hay un `config.json` que define el nombre de la lengua y cómo combinar los archivos.
-
-**2. personalización de plantilla HTML**
-
-Cada idioma puede reemplazar la plantilla por defecto en el `Lenguaje de plantillas de documentos`.
-
-### Pautas editoriales
-
-Consulte el archivo `STYLEGUIDE.md` para las pautas en el lenguaje y el uso.
-
-## Generar documentación con Node.js
-
-Ahora se podía ejecutar documentación usando Node.js en Windows o en Linux box.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Configuración de Node.js
-
- 1. Ir a Node.JS [descargas página](http://nodejs.org/download/)
- 2. Descargar e instalar el paquete para su sistema operativo.
- 3. Retirada este repositorio usando Git
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. Instalar dependencias. En la raíz de la carpeta clonada cordova-docs ejecutar
-
- npm install
-
-
- 5. Ahora usted es capaz de construir documentación localmente.
-
-### Vista previa rápida
-
-Al hacer modificaciones menores, es generalmente seguro simplemente prestar el editado de descuento a HTML. Muchos editores de código tienen plugins para hacer descuento a HTML y hay un puñado de [buenos](http://dillinger.io/) editores en línea.
-
-Actualmente, se utilizan un script de Node.JS y [joDoc-js](https://github.com/kant2002/jodoc-js) para generar la documentación HTML.
-
-## Generando una versión
-
-Hay una tarea de Rake para incrementar la versión, generar el directorio de versión y actualizar la documentación de borde.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/fr/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/fr/README.md b/doc/docs-README/fr/README.md
deleted file mode 100644
index bea3b67..0000000
--- a/doc/docs-README/fr/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Apache Cordova API Documentation
-
-La documentation de l'API JavaScript pour [Apache Cordova](http://cordova.io/).
-
-La documentation est disponible à [docs.cordova.io](http://docs.cordova.io/).
-
-## Format de documentation
-
-Toute la documentation [Apache Cordova](http://cordova.io/) est écrit avec [markdown](http://daringfireball.net/projects/markdown/syntax), un langage de balisage léger qui peut être composé au format HTML. Markdown offre un moyen simple et flexible pour documenter le noyau de Cordova API et API spécifique à la plateforme.
-
-## Structure des fichiers
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## Contribuer à la Documentation
-
-### Rapport ou résoudre un problème
-
-Nous utilisons [JIRA Apache](https://issues.apache.org/jira/browse/CB)
-
-Par ailleurs, vous bercer ! Merci de nous aider à améliorer la documentation !
-
-### À l'aide de Git
-
-Vous êtes nouveau sur Git ou contribuer sur GitHub ?
-
-Nous avons [écrit quelques Git tutoriaux](http://wiki.apache.org/cordova/ContributorWorkflow) pour vous aider à commencer à contribuer à la documentation.
-
-### Envoyer des demandes de Pull
-
-Requêtes d'extraction sont les bienvenus !
-
-Nous apprécions l'utilisation des branches du sujet.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### Ajout d'une langue
-
-Voulez-vous la documentation Apache Cordova, dans une autre langue ? Nous faisons aussi ! Avec le soutien de la plateforme de gestion de [Crowdin](http://crowdin.net/project/cordova), une traduction et de localisation, traducteurs peuvent vous connecter à l'outillage facile à utiliser et fournissent autant ou aussi peu d'assistance traduction comme ils le voudraient. Si vous connaissez une autre langue s'il vous plaît soutenir Cordova et contribuer. http://crowdin.net/project/cordova. Pour certaines meilleures pratiques pour utiliser l'outil Crowdin, veuillez consulter notre wiki http://wiki.apache.org/cordova/CordovaTranslations.
-
-Administrateurs de langue de Cordova, n'oubliez pas les étapes suivantes :
-
-**1. config.json**
-
-Pour chaque langue et chaque version, il y a un `config.json` qui définit le nom de la langue et comment fusionner les fichiers.
-
-**2. personnalisation de modèle HTML**
-
-Chaque langue peut remplacer le modèle par défaut dans le `template/docs/LANGUAGE`.
-
-### Règles éditoriales
-
-S'il vous plaît voir le fichier `STYLEGUIDE.md` pour connaître les instructions sur l'utilisation et de la langue.
-
-## Génération de Documentation avec Node.js
-
-Ce moment documentation pouvait être exécutée à l'aide de Node.js sur GNU / Linux ou sous Windows.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Mise en place de Node.js
-
- 1. Aller à Node.JS [téléchargements de page](http://nodejs.org/download/)
- 2. Téléchargez et installez le paquet pour votre système d'exploitation.
- 3. Commander ce référentiel à l'aide de Git
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. Installer les dépendances. Dans la racine du dossier clonés cordova-docs exécuter
-
- npm install
-
-
- 5. Maintenant vous en mesure de construire la documentation localement.
-
-### Aperçu rapide
-
-Lorsque vous effectuez des modifications mineures, il est généralement sans danger pour simplement rendre l'édité de Markdown au format HTML. De nombreux éditeurs de code ont plugins pour restituer Markdown en HTML et il ya une poignée de [bons](http://dillinger.io/) rédacteurs en ligne.
-
-Actuellement, un script de Node.JS et [joDoc-js](https://github.com/kant2002/jodoc-js) sont utilisés pour générer la documentation HTML.
-
-## Génération d'une Version Release
-
-Il y a une tâche de Rake pour incrémenter la version, générer le répertoire de version et mettre à jour la documentation de bord.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/it/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/it/README.md b/doc/docs-README/it/README.md
deleted file mode 100644
index 26e1a28..0000000
--- a/doc/docs-README/it/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Documentazione di Apache Cordova API
-
-La documentazione API JavaScript per [Apache Cordova](http://cordova.io/).
-
-La documentazione è disponibile presso [docs.cordova.io](http://docs.cordova.io/).
-
-## Formato della documentazione
-
-Tutta la documentazione di [Apache Cordova](http://cordova.io/) è scritto con [markdown](http://daringfireball.net/projects/markdown/syntax), un linguaggio di markup leggero che può essere impaginare in HTML. Markdown consente di documentare il nucleo di Cordova API e API specifiche della piattaforma in modo semplice e flessibile.
-
-## Struttura dei file
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## Contribuire alla documentazione
-
-### Segnalare o risolvere un problema
-
-Utilizziamo [Apache JIRA](https://issues.apache.org/jira/browse/CB)
-
-A proposito, è rock! Grazie per averci aiutato a migliorare la documentazione!
-
-### Uso di Git
-
-Sei nuovo a Git o contribuendo su GitHub?
-
-Abbiamo [scritto un paio di Git tutorial](http://wiki.apache.org/cordova/ContributorWorkflow) per aiutarvi a iniziare a contribuire alla documentazione.
-
-### L'invio di richieste di Pull
-
-Tirare le richieste sono benvenute!
-
-Apprezziamo l'uso dei rami di argomento.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### L'aggiunta di una lingua
-
-Vuoi che la documentazione di Apache Cordova in un'altra lingua? Lo facciamo anche noi! Con il supporto della piattaforma di gestione [Crowdin](http://crowdin.net/project/cordova), traduzione e localizzazione, traduttori collegarti alla lavorazione con utensili di facile da usare e fornire tanto o poichè poca assistenza di traduzione come vorrebbero. Se si conosce un'altra lingua si prega di sostenere Cordova e contribuire. http://crowdin.net/project/cordova. Per alcune procedure consigliate per l'utilizzo lo strumento Crowdin si prega di consultare il nostro wiki http://wiki.apache.org/cordova/CordovaTranslations.
-
-Gli amministratori di lingua di Cordova, non dimenticare questi passaggi:
-
-**1. config**
-
-Per ogni lingua e versione, c'è un `config` che definisce il nome della lingua e come unire i file.
-
-**2. personalizzazione del template HTML**
-
-Ogni lingua può sovrascrivere il template predefinito nella `Lingua/docs/modello`.
-
-### Direttive editoriali
-
-Vedere il file `STYLEGUIDE.md` per le linee guida sull'utilizzo e la lingua.
-
-## La generazione della documentazione con node. js
-
-In questo momento la documentazione potrebbe essere eseguito utilizzando node. js su Windows o su Linux box.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Configurazione di node. js
-
- 1. Vai a node. js [pagina downloads](http://nodejs.org/download/)
- 2. Scaricare e installare il pacchetto per il sistema di funzionamento.
- 3. Check-out questo repository utilizzando Git
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. Installare le dipendenze. Nella radice della cartella clonata cordova-docs eseguita
-
- npm install
-
-
- 5. Ora siete in grado di generare documentazione locale.
-
-### Anteprima rapida
-
-Quando si apportano le modifiche minori, è solitamente sicuro semplicemente rendere il modificato da Markdown a HTML. Molti editor di codice sono plugin per eseguire il rendering HTML Markdown e ci sono una manciata di [buoni](http://dillinger.io/) editor online.
-
-Attualmente, un node. js script e [joDoc-js](https://github.com/kant2002/jodoc-js) vengono utilizzati per generare la documentazione HTML.
-
-## Generazione di una rilascio di versione
-
-C'è un compito di Rake per incrementare il numero di versione, la directory della versione di generare e aggiornare la documentazione di bordo.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/ja/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/ja/README.md b/doc/docs-README/ja/README.md
deleted file mode 100644
index be95c11..0000000
--- a/doc/docs-README/ja/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Apache コルドバ API ドキュメント
-
-[Apache コルドバ](http://cordova.io/)の JavaScript API ドキュメント.
-
-マニュアルは、 [docs.cordova.io](http://docs.cordova.io/).
-
-## ドキュメントの形式
-
-すべての[Apache コルドバ](http://cordova.io/)ドキュメントは[値下げ](http://daringfireball.net/projects/markdown/syntax)HTML にタイプセットすることができます軽量マークアップ言語で書き込まれます。 値下げは、コルドバのコア API やプラットフォーム固有の Api を文書化する簡単かつ柔軟な方法を提供します。
-
-## ファイル構造
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## ドキュメントに貢献
-
-### 問題を修正または報告
-
-我々 は、 [Apache JIRA](https://issues.apache.org/jira/browse/CB)を使用してください。
-
-ところで、あなたは揺れ動きます!ドキュメントの改善にご協力いただきありがとうございます!
-
-### Git を使ってください。
-
-あなたは Git または GitHub に貢献する新しいですか。
-
-我々 が[書かれていくつかの Git チュートリアル](http://wiki.apache.org/cordova/ContributorWorkflow)ドキュメントに貢献を始めるため。
-
-### プル要求を送信します。
-
-プルリクエストは大歓迎です!
-
-トピック ブランチの使用お願い申し上げます。
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### 言語を追加します。
-
-別の言語で Apache コルドバ ドキュメントですか? 我々 はあまりにも行う! [Crowdin](http://crowdin.net/project/cordova)、翻訳およびローカリゼーション管理プラットフォームのサポート、翻訳は簡単に使用できるツールにログインし、彼らのようで、少し翻訳支援を提供できます。 場合してくださいコルドバをサポートし、貢献する別の言語を知っています。 http://crowdin.net/project/cordova. Crowdin ツールを使用してのいくつかのベスト プラクティスは、私たちの wiki の http://wiki.apache.org/cordova/CordovaTranslations を参照してください。
-
-コルドバ言語管理者は、これらの手順を忘れてはいけない。
-
-**1. config.json**
-
-各言語およびバージョン、言語とファイルをマージする方法の名前を定義する`config.json`があります。
-
-**2. HTML テンプレートをカスタマイズします。**
-
-各言語の`テンプレート/ドキュメント/言語`で既定のテンプレートをオーバーライドできます。.
-
-### 編集ガイドライン
-
-言語および使用に関するガイドラインの`STYLEGUIDE.md`ファイルを参照してください。
-
-## Node.js のドキュメントを生成します。
-
-今、Windows または Linux ボックスのいずれか、Node.js を使用してドキュメントを実行でした。
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Node.js を設定
-
- 1. Node.JS[のダウンロード ページ](http://nodejs.org/download/)へ
- 2. ダウンロードして、あなたの操作システムにパッケージをインストールします。
- 3. チェック アウトこのリポジトリは Git を使って
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. 依存関係をインストールします。実行クローン コルドバ docs フォルダーのルートに
-
- npm install
-
-
- 5. 今ローカルでドキュメントをビルドすることができます。
-
-### クイック プレビュー
-
-細部の編集の際、通常単に HTML に値下げから編集レンダリングしても安全です。 多くのコード エディターは、記法を HTML に表示するプラグインを持っているし、[良い](http://dillinger.io/)オンライン編集者の一握りがあります。
-
-現在、Node.JS スクリプトと[joDoc js](https://github.com/kant2002/jodoc-js)を使用して HTML ドキュメントを生成します。
-
-## バージョンのリリースを生成します。
-
-バージョンをインクリメント、バージョン、ディレクトリを生成し、エッジのマニュアルを更新する Rake タスクがあります。
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/66ea750c/doc/docs-README/ko/README.md
----------------------------------------------------------------------
diff --git a/doc/docs-README/ko/README.md b/doc/docs-README/ko/README.md
deleted file mode 100644
index fd20233..0000000
--- a/doc/docs-README/ko/README.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# 아파치 코르도바 API 설명서
-
-[아파치 Cordova](http://cordova.io/) 에 대 한 JavaScript API 설명서.
-
-설명서는 [docs.cordova.io](http://docs.cordova.io/) 에서 사용할 수.
-
-## 문서 형식
-
-모든 [아파치 코르도바](http://cordova.io/) 문서 [markdown](http://daringfireball.net/projects/markdown/syntax), HTML로 활자 수는 가벼운 마크업 언어와 함께 기록 됩니다. Markdown은 코르도바의 핵심 API 및 플랫폼 특정 Api를 문서화 하는 간단 하 고 유연한 방법을 제공 합니다.
-
-## 파일 구조
-
- docs/
- docs/LANGUAGE
- docs/LANGUAGE/VERSION
- docs/LANGUAGE/VERSION/cordova/
- docs/LANGUAGE/VERSION/guide/platforms/PLATFORMNAME/
-
-
-## 설명서에 기여
-
-### 신고 또는 문제 해결
-
-우리는 [아파치 JIRA](https://issues.apache.org/jira/browse/CB) 사용
-
-그건 그렇고, 당신은 바위! 설명서를 개선 하는 데 도움을 주셔서 감사!
-
-### Git를 사용 하 여
-
-당신은 새로운 자식 또는 GitHub에 기여?
-
-우리는 [몇 가지 Git 튜토리얼 작성](http://wiki.apache.org/cordova/ContributorWorkflow) 설명서에 기여와 함께 시작할 수 있도록.
-
-### 끌어오기 요청을 보내는
-
-끌어오기 요청은 환영 합니다!
-
-항목 지점의 사용 부탁 드립니다.
-
- git checkout -b issue_23
-
- # code
-
- git commit -m "Issue 23: Fix a bad bug."
-
- git push origin issue_23
-
- # send pull request from branch issue_23 to cordova:master
-
-
-### 언어 추가
-
-다른 언어에서 아파치 코르도바 설명서 보기 우리는 너무 해! [Crowdin](http://crowdin.net/project/cordova), 번역 및 로컬라이제이션 관리 플랫폼의 지원, 번역 수 사용 하기 쉬운 툴에 로그인 하 고 그들이 했던 것 처럼 작은 번역 지원을 제공. 당신이 알고 있다면 다른 언어 코르도바를 지원 하 고 기여 하십시오. http://crowdin.net/project/cordova. Crowdin 도구를 사용 하 여에 대 한 몇 가지 모범 사례에 대 한 우리의 위 키 http://wiki.apache.org/cordova/CordovaTranslations를 참조 하십시오.
-
-코르도바 언어 관리자는 다음이 단계를 잊지 마세요:
-
-**1입니다. config.json**
-
-각 언어 및 버전에 대 한 파일을 병합 하는 방법과 언어의 이름을 정의 하는 `config.json` 입니다.
-
-**2. 사용자 지정 HTML 서식 파일**
-
-각 언어 `서식 파일/문서/언어` 에서 기본 서식 파일을 재정의할 수 있습니다..
-
-### 광고문 안 가이드
-
-언어 및 사용에 대 한 `STYLEGUIDE.md` 파일을 참조 하십시오.
-
-## Node.js 함께 문서 생성
-
-지금 문서 Windows, 또는 리눅스 상자에 Node.js를 사용 하 여 실행할 수 있습니다.
-
- $ rm -r tmp public # Clear out old docs
- $ ./bin/genjs # compile all docs
- $ ./bin/genjs en edge # compile English Edge docs
- $ ./bin/genjs ru edge # compile Russian Edge docs
- $ ./bin/genjs es 3.5.0 # compile Spanish 3.5.0 docs
-
-
-### Node.js를 설정
-
- 1. Node.JS [다운로드 페이지](http://nodejs.org/download/) 이동
- 2. 다운로드 및 운영 체제에 대 한 패키지를 설치 합니다.
- 3. 체크 아웃 Git를 사용 하 여이 저장소
-
- git clone https://github.com/apache/cordova-docs
-
-
- 4. 종속성을 설치 합니다. 실행 복제 코르도바-오피스 폴더의 루트에
-
- npm install
-
-
- 5. 지금 당신은 로컬로 문서를 만들 수입니다.
-
-### 빠른 미리 보기
-
-사소한 편집 때, 그것은 일반적으로 간단 하 게 렌더링 하는 편집 Markdown에서 HTML로 안전입니다. 많은 코드 에디터는 Markdown HTML로 렌더링 하는 플러그인 그리고 [좋은](http://dillinger.io/) 온라인 편집자의 한 줌 있다.
-
-현재, Node.JS 스크립트와 [joDoc js](https://github.com/kant2002/jodoc-js) HTML 문서를 생성 하 데 사용 됩니다.
-
-## 생성 버전 출시
-
-버전 디렉터리를 생성 하 버전 증가 가장자리 설명서를 업데이트 레이크 작업이입니다.
-
- # generate version 4.1.0 for english.
- .\bin\incrementversion en 4.1.0
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org