Index: gc_lang/fr/setup.py
==================================================================
--- gc_lang/fr/setup.py
+++ gc_lang/fr/setup.py
@@ -13,11 +13,11 @@
 # here = path.abspath(path.dirname(__file__))
 # with open(path.join(here, 'README.txt'), encoding='utf-8') as f:
 #     long_description = f.read()
 
 setup(
-    name='grammalecte',
+    name='Grammalecte-fr',
 
     # Versions should comply with PEP440.  For a discussion on single-sourcing
     # the version across setup.py and the project code, see
     # https://packaging.python.org/en/latest/single_source_version.html
     version='${version}',
@@ -87,18 +87,22 @@
 
     # If there are data files included in your packages that need to be
     # installed, specify them here.  If using Python 2.6 or less, then these
     # have to be included in MANIFEST.in as well.
     package_data={
-        'dictionary': ['_dictionaries/French.bdic'],
+        'grammalecte': ['_dictionaries/French.bdic', '*.txt'],
+        '': ['*.py', '*.txt', '*.ini']
     },
+    include_package_data=True,
 
     # Although 'package_data' is the preferred approach, in some case you may
     # need to place data files outside of your packages. See:
     # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
     # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
     # data_files=[('my_data', ['data/data_file'])],
+    data_files=[('', ['cli.py', 'server.py', 'bottle.py', 'README.txt', 'license.txt', \
+                      'server_options.fr.ini', 'server_options._global.ini'])],
 
     # To provide executable scripts, use entry points in preference to the
     # "scripts" keyword. Entry points provide cross-platform support and allow
     # pip to create the appropriate form of executable for the target platform.
     # entry_points={