From 3495f78d7735f88f11ddf548955d8b57f1ddd020 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicolas=20L=C5=93uillet?= Date: Sat, 20 Feb 2016 08:39:08 +0100 Subject: French translation for documentation --- docs/en/developer/docker.rst | 6 +++--- docs/en/developer/translate.rst | 35 ++++++++++++++++++++++++++-------- docs/en/index.rst | 4 ++++ docs/en/user/configuration.rst | 42 ++++++++++++++++++++++++++--------------- 4 files changed, 61 insertions(+), 26 deletions(-) (limited to 'docs/en') diff --git a/docs/en/developer/docker.rst b/docs/en/developer/docker.rst index aece2984..8816cbcf 100644 --- a/docs/en/developer/docker.rst +++ b/docs/en/developer/docker.rst @@ -15,11 +15,11 @@ your system and up to date. Switch DBMS ----------- -By default, wallabag will start with a sqlite database. +By default, wallabag will start with a SQLite database. Since wallabag provides support for Postgresql and MySQL, docker containers are also available for these ones. -In ``docker-compose.yml``, for the chosen DBMS uncomment : +In ``docker-compose.yml``, for the chosen DBMS uncomment: - the container definition (``postgres`` or ``mariadb`` root level block) @@ -27,7 +27,7 @@ In ``docker-compose.yml``, for the chosen DBMS uncomment : - the container env file in the ``php`` container In order to keep running Symfony commands on your host (such as -``wallabag:install``), you also should : +``wallabag:install``), you also should: - source the proper env files on your command line, so variables like ``SYMFONY__ENV__DATABASE_HOST`` will exist. diff --git a/docs/en/developer/translate.rst b/docs/en/developer/translate.rst index 85cf2563..33b0ebdb 100644 --- a/docs/en/developer/translate.rst +++ b/docs/en/developer/translate.rst @@ -1,31 +1,38 @@ Translate wallabag ================== +wallabag web application +------------------------ + Translation files ------------------ +~~~~~~~~~~~~~~~~~ .. note:: - As wallabag is mainly developed by a French team, please consider that french translation is the most updated one and please copy it to create your own translation. + As wallabag is mainly developed by a French team, please consider that french + translation is the most updated one and please copy it to create your own translation. You can find translation files here: https://github.com/wallabag/wallabag/tree/v2/src/Wallabag/CoreBundle/Resources/translations. -You have to create ``messages.CODE.yml`` and ``validators.CODE.yml``, where CODE is the the ISO 639-1 code of your language (`see wikipedia `__). +You have to create ``messages.CODE.yml`` and ``validators.CODE.yml``, where CODE +is the ISO 639-1 code of your language (`see wikipedia `__). Other files to translate: - https://github.com/wallabag/wallabag/tree/v2/app/Resources/CraueConfigBundle/translations. - https://github.com/wallabag/wallabag/tree/v2/app/Resources/FOSUserBundle/translations. -You have to create ``CraueConfigBundle.CODE.yml``. +You have to create ``THE_TRANSLATION_FILE.CODE.yml`` files. Configuration file ------------------- +~~~~~~~~~~~~~~~~~~ You have to edit `app/config/config.yml -`__ to display your language on Configuration page of wallabag (to allow users to switch to this new translation). +`__ to display +your language on Configuration page of wallabag (to allow users to switch to this new translation). -Under the ``wallabag_core.languages`` section, you have to add a new line for with your translation. For example +Under the ``wallabag_core.languages`` section, you have to add a new line with +your translation. For example: :: @@ -36,6 +43,18 @@ Under the ``wallabag_core.languages`` section, you have to add a new line for wi fr: 'Français' -For the first column (``en``, ``fr``, etc.), you have to add the ISO 639-1 code of your language (see above). +For the first column (``en``, ``fr``, etc.), you have to add the ISO 639-1 code +of your language (see above). For the second column, it's the name of your language. Just that. + +wallabag documentation +---------------------- + +.. note:: + + Contrary to the web application, the main language for documentation is english. + +Documentation files are stored here: https://github.com/wallabag/wallabag/tree/v2/docs + +You need to respect the ``en`` folder structure when you create your own translation. diff --git a/docs/en/index.rst b/docs/en/index.rst index acd9b383..85c764da 100644 --- a/docs/en/index.rst +++ b/docs/en/index.rst @@ -8,6 +8,10 @@ wallabag documentation **wallabag** is a read-it-later application: it saves a web page by keeping content only. Elements like navigation or ads are deleted. +.. note:: + + This documentation is about wallabag v2. If you want to read documentation for wallabag v1, `please have a look here `__. + The main documentation for this application is organized into a couple sections: * :ref:`user-docs` diff --git a/docs/en/user/configuration.rst b/docs/en/user/configuration.rst index 369c977a..70d960ff 100644 --- a/docs/en/user/configuration.rst +++ b/docs/en/user/configuration.rst @@ -3,7 +3,8 @@ Configuration Now you're logged in, it's time to configure your account as you want. -Click on ``Config`` menu. You have five tabs: ``Settings``, ``RSS``, ``User information``, ``Password`` and ``Tagging rules``. +Click on ``Config`` menu. You have five tabs: ``Settings``, ``RSS``, +``User information``, ``Password`` and ``Tagging rules``. Settings -------- @@ -11,7 +12,9 @@ Settings Theme ~~~~~ -wallabag is customizable. You can choose your prefered theme here. You can also create a new one, a chapter is dedicated for this. The default theme is ``Material``, it's the theme used in the documentation screenshots. +wallabag is customizable. You can choose your prefered theme here. You can also +create a new one, a chapter will be dedicated for this. The default theme is +``Material``, it's the theme used in the documentation screenshots. Items per page ~~~~~~~~~~~~~~ @@ -21,7 +24,8 @@ You can change the number of articles displayed on each page. Language ~~~~~~~~ -You can change the language of wallabag interface. +You can change the language of wallabag interface. You need to logout for this change +to take effect. RSS --- @@ -43,41 +47,49 @@ You can change your name, your email address and enable ``Two factor authenticat Two factor authentication ~~~~~~~~~~~~~~~~~~~~~~~~~ - Two-factor authentication (also known as 2FA) is a technology patented in 1984 that provides identification of users by means of the combination of two different components. + Two-factor authentication (also known as 2FA) is a technology patented in 1984 + that provides identification of users by means of the combination of two different components. https://en.wikipedia.org/wiki/Two-factor_authentication -If you enable 2FA, each time you want to login to wallabag, you'll receive a code by email. You have to put this code on the following form. +If you enable 2FA, each time you want to login to wallabag, you'll receive +a code by email. You have to put this code on the following form. .. image:: ../../img/user/2FA_form.png - :alt: Two factor authentication - :align: center + :alt: Two factor authentication + :align: center -If you don't want to receive a code each time you want to login, you can check the ``I'm on a trusted computer`` checkbox: wallabag will remember you for 15 days. +If you don't want to receive a code each time you want to login, you can check +the ``I'm on a trusted computer`` checkbox: wallabag will remember you for 15 days. Password -------- -You can change your password here. +You can change your password here (8 characters minimum). Tagging rules ------------- -If you want to automatically assign a tag to new articles, this part of the configuration is for you. +If you want to automatically assign a tag to new articles, this part +of the configuration is for you. What does « tagging rules » mean? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ They are rules used by wallabag to automatically tag new entries. -Each time a new entry is added, all the tagging rules will be used to add the tags you configured, thus saving you the trouble to manually classify your entries. +Each time a new entry is added, all the tagging rules will be used to add +the tags you configured, thus saving you the trouble to manually classify your entries. How do I use them? ~~~~~~~~~~~~~~~~~~ -Let assume you want to tag new entries as *« short reading »* when the reading time is inferior to 3 minutes. -In that case, you should put « readingTime <= 3 » in the **Rule** field and *« short reading »* in the **Tags** field. +Let assume you want to tag new entries as *« short reading »* when +the reading time is inferior to 3 minutes. +In that case, you should put « readingTime <= 3 » in the **Rule** field +and *« short reading »* in the **Tags** field. Several tags can added simultaneously by separating them by a comma: *« short reading, must read »*. -Complex rules can be written by using predefined operators: if *« readingTime >= 5 AND domainName = "github.com" »* then tag as *« long reading, github »*. +Complex rules can be written by using predefined operators: +if *« readingTime >= 5 AND domainName = "github.com" »* then tag as *« long reading, github »*. Which variables and operators can I use to write rules? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -96,4 +108,4 @@ language The entry's language != Not equal mimetype The entry's mime-type OR One rule or another readingTime The estimated entry's reading time, in minutes AND One rule and another domainName The domain name of the entry matches Tests that a subject is matches a search (case-insensitive). Example: title matches "football" -=========== ============================================== ======== ========== \ No newline at end of file +=========== ============================================== ======== ========== -- cgit v1.2.3