Documentation: french translation of import_export

1 files changed, 18 insertions, 16 deletions

diff --git a/docs/import_export.rst b/docs/import_export.rst
index 1032804..3574a66 100644
--- a/docs/import_export.rst
+++ b/docs/import_export.rst
@@ -36,12 +36,13 @@ Common fields
 - **Name by default**: if no name can be identified to the newly imported object
   this is the name that will be used. If this field is empty the name of the
   associated category will be use.
-- **SRID**: Chimère will try to identify automatically the correct projection
-  from the given source. But sometimes the information is not present or cannot
-  be guessed (for instance a shapefile that uses non standard proj file). In
-  this case Chimère will use WGS84 by default (the classic latitude/longitude)
-  but it is not always correct. If you experience problems with items
-  localisation you should put here the SRID associated to the projection of
+- **SRID**: Chimère will try to identify automatically the correct coordinate
+  system from the given source. But sometimes the information is not present or
+  cannot be guessed (for instance a Shapefile that uses non standard proj file).
+  In this case Chimère will use WGS84 by default (the classic
+  latitude/longitude) but it is not always correct. If you experience problems
+  with items localisation you should put here the `SRID
+  <https://en.wikipedia.org/wiki/SRID>`_ associated to the coordinate system of
   your source.
 - **Origin**: if not null this field will be associated to each item imported in
   order to easily identify where the item came from. For OSM import the source
@@ -71,9 +72,9 @@ Shapefile import
 .. image:: _static/chimere_admin_import_shapefile.png
 
 
-- **Web address/source file (mandatory)**: your shapefile could be distant or a 
+- **Web address/source file (mandatory)**: your Shapefile could be distant or a 
   local file. You'll have to fill one of the two fields.
-- **Zipped file**: only zipped shapefiles are accepted so this checkbox has to be
+- **Zipped file**: only zipped Shapefiles are accepted so this checkbox has to be
   checked.
 
 GeoRSS import
@@ -97,8 +98,8 @@ By the way because of the geometry of the item this format is not very
 convenient to add new content but could be handy to update informations.
 
 .. Warning::
-   If you mean to update existing data by this import, do *not* modify the 
-   geometry column.
+   If you mean to update existing data by this import, unless you know how to
+   edit WKT do *not* modify the geometry column.
 
 .. image:: _static/chimere_admin_import_CSV.png
 
@@ -151,9 +152,10 @@ Managing imported data
 **********************
 
 All new imported items have the state **Imported**. To make them available on
-the map you'll have to validate them. If you don't want some items to be visible on
-the map, instead of deleting them it is recommended to set them to the state
-**Disabled**.
+the map you'll have to validate them. If you don't want some items to be visible
+on the map, instead of deleting them it is recommended to set them to the state
+**Disabled**. So on the next update from the source, rather than appear as new
+items they remain disabled.
 
 .. Warning::
    Be careful with duplicates between your existing data and imported data. This
@@ -210,10 +212,10 @@ to determine:
 The OSM export in Chimère is designed to be the more preservative possible in
 regards to OSM database. That's why before any export an import is done. If
 the new import has updated data, these new data will overload data in your
-Chimère (if you don't want that: don't do export). All pending imported items
-should have been treated before doing an export.
+Chimère (if you don't want that: don't do re-imports so dont do exports). All
+pending imported items should have been treated before doing an export.
 
-To launch an export select the appropriate Import object in the imports list.
+To launch an export select the appropriate *Import* object in the imports list.
 Then select the **Export to OSM** action and validate.
 Then you'll be asked for your OSM username and password and the API you want to
 use. If you regularly use Chimère to do export, it is recommended to create an