WIP: Renaming to PrusaSlicer.

Removed the obsolte icons.

CMakeLists.txt

@@ -331,7 +331,7 @@ set(L10N_DIR "${SLIC3R_RESOURCES_DIR}/localization")
 add_custom_target(pot
     COMMAND xgettext --keyword=L --add-comments=TRN --from-code=UTF-8 --debug
         -f "${L10N_DIR}/list.txt"
-        -o "${L10N_DIR}/Slic3rPE.pot"
+        -o "${L10N_DIR}/PrusaSlicer.pot"
     WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
     COMMENT "Generate pot file from strings in the source tree"
 )

README.md

@@ -1,16 +1,18 @@
 
-![Slic3rPE logo](/resources/icons/Slic3r.png?raw=true)
+![PrusaSlicer logo](/resources/icons/PrusaSlicer.png?raw=true)
 
-# Slic3r Prusa Edition
+# PrusaSlicer
 
-Prebuilt Windows, OSX and Linux binaries are available through the [git releases page](https://github.com/prusa3d/Slic3r/releases).
+Prebuilt Windows, OSX and Linux binaries are available through the [git releases page](https://github.com/prusa3d/PrusaSlicer/releases).
 
-Slic3r takes 3D models (STL, OBJ, AMF) and converts them into G-code
+PrusaSlicer takes 3D models (STL, OBJ, AMF) and converts them into G-code
 instructions for FFF printers or PNG layers for mSLA 3D printers. It's
 compatible with any modern printer based on the RepRap toolchain, including all
 those based on the Marlin, Prusa, Sprinter and Repetier firmware. It also works
 with Mach3, LinuxCNC and Machinekit controllers.
 
+PrusaSlicer is based on [Slic3r](https://github.com/Slic3r/Slic3r) by Alessandro Ranelucci and the RepRap community.
+
 See the [project homepage](https://www.prusa3d.com/slic3r-prusa-edition/) and
 the [documentation directory](doc/) for more information.
 
@@ -18,12 +20,12 @@ the [documentation directory](doc/) for more information.
 
 All user facing code is written in C++, and some legacy code as well as unit
 tests are written in Perl. Perl is not required for either development or use
-of Slic3r.
+of PrusaSlicer.
 
 The slicing core is the `libslic3r` library, which can be built and used in a standalone way.
 The command line interface is a thin wrapper over `libslic3r`.
 
-### What are Slic3r's main features?
+### What are PrusaSlicer's main features?
 
 Key features are:
 
@@ -46,7 +48,7 @@ Other major features are:
 * several infill patterns including honeycomb, spirals, Hilbert curves
 * support material, raft, brim, skirt
 * **standby temperature** and automatic wiping for multi-extruder printing
-* [customizable **G-code macros**](https://github.com/prusa3d/Slic3r/wiki/Slic3r-Prusa-Edition-Macro-Language) and output filename with variable placeholders
+* [customizable **G-code macros**](https://github.com/prusa3d/PrusaSlicer/wiki/Slic3r-Prusa-Edition-Macro-Language) and output filename with variable placeholders
 * support for **post-processing scripts**
 * **cooling logic** controlling fan speed and dynamic print speed
 
@@ -61,18 +63,14 @@ these documentation pages:
 ### Can I help?
 
 Sure! You can do the following to find things that are available to help with:
-* Add an [issue](https://github.com/prusa3d/Slic3r/issues) to the github tracker if it isn't already present.
-* Look at [issues labeled "volunteer needed"](https://github.com/prusa3d/Slic3r/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22volunteer+needed%22)
+* Add an [issue](https://github.com/prusa3d/PrusaSlicer/issues) to the github tracker if it isn't already present.
+* Look at [issues labeled "volunteer needed"](https://github.com/prusa3d/PrusaSlicer/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22volunteer+needed%22)
 
-### What's Slic3r license?
+### What's PrusaSlicer license?
 
-Slic3r PE is licensed under the _GNU Affero General Public License, version 3_.
-The Prusa Edition is originally based on Slic3r by Alessandro Ranellucci.
+PrusaSlicer is licensed under the _GNU Affero General Public License, version 3_.
+The PrusaSlicer is originally based on Slic3r by Alessandro Ranellucci.
 
-The [Silk icon set](http://www.famfamfam.com/lab/icons/silk/) used in Slic3r is
-licensed under the _Creative Commons Attribution 3.0 License_.
-The author of the Silk icon set is Mark James.
+### How can I use PrusaSlicer from the command line?
 
-### How can I use Slic3r PE from the command line?
-
-Please refer to the [Command Line Interface](https://github.com/prusa3d/Slic3r/wiki/Command-Line-Interface) wiki page.
+Please refer to the [Command Line Interface](https://github.com/prusa3d/PrusaSlicer/wiki/Command-Line-Interface) wiki page.

doc/Localization_guide.md

@@ -1,6 +1,6 @@
 # Localization and translation guide
 
-The purpose of this guide is to describe how to contribute to the Slic3rPE translations. We use GNUgettext for extracting string resources from the project and PoEdit for editing translations.
+The purpose of this guide is to describe how to contribute to the PrusaSlicer translations. We use GNUgettext for extracting string resources from the project and PoEdit for editing translations.
 
 Those can be downloaded here: 
 -    https://sourceforge.net/directory/os:windows/?q=gnu+gettext GNUgettext package contains a set of tools to extract strings from the source code and to create the translation Catalog.
@@ -13,40 +13,40 @@ Full manual for GNUgettext can be seen here: http://www.gnu.org/software/gettext
 
 ### Scenario 1. How do I add a translation or fix an existing translation
 1. Get PO-file from corresponding folder here:
-https://github.com/prusa3d/Slic3r/tree/master/resources/localization
+https://github.com/prusa3d/PrusaSlicer/tree/master/resources/localization
 2. Open this file in PoEdit as "Edit a translation"
 3. Apply your corrections to the translation
-4. Push changed Slic3rPE.po and Slic3rPE.mo (will create automatically after saving of Slic3r.po in PoEdit) back to to the enter folder.
+4. Push changed PrusaSlicer.po and PrusaSlicer.mo (will create automatically after saving of PrusaSlicer.po in PoEdit) back to to the enter folder.
 
 ### Scenario 2. How do I add a new language support
-1. Get file Slic3rPE.pot here :
-https://github.com/prusa3d/Slic3r/tree/master/resources/localization
+1. Get file PrusaSlicer.pot here :
+https://github.com/prusa3d/PrusaSlicer/tree/master/resources/localization
 2. Open it in PoEdit for "Create new translation"
 3. Select Translation Language (for example French).
 4. As a result you will have fr.po - the file containing translation to French.
 Notice. When the translation is complete you need to:
-    - Rename the file to Slic3rPE.po
-    - Click "Save file" button. Slic3rPE.mo will be created immediately
-    - Both Slic3rPE.po and Slic3rPE.mo have to be saved here:
-https://github.com/prusa3d/Slic3r/tree/master/resources/localization/fr
+    - Rename the file to PrusaSlicer.po
+    - Click "Save file" button. PrusaSlicer.mo will be created immediately
+    - Both PrusaSlicer.po and PrusaSlicer.mo have to be saved here:
+https://github.com/prusa3d/PrusaSlicer/tree/master/resources/localization/fr
 ( name of folder "fr" means "French" - the translation language). 
 
-### Scenario 3. How do I add a new text resource when implementing a feature to Slic3rPE
-Each string resource in Slic3rPE available for translation needs to be explicitly marked using L() macro like this:
+### Scenario 3. How do I add a new text resource when implementing a feature to PrusaSlicer
+Each string resource in PrusaSlicer available for translation needs to be explicitly marked using L() macro like this:
 ```C++
 auto msg = L("This message to be localized")
 ```
 To get translated text use one of needed macro/function (`_(s)` or `_CHB(s)` ).
 If you add new file resource, add it to the list of files containing macro `L()`
 
-### Scenario 4. How do I use GNUgettext to localize my own application taking Slic3rPE as an example
+### Scenario 4. How do I use GNUgettext to localize my own application taking PrusaSlicer as an example
 
 1.  For convenience create a list of files with this macro `L(s)`. We have 
-https://github.com/prusa3d/Slic3r/tree/master/resources/localization/list.txt.
+https://github.com/prusa3d/PrusaSlicer/tree/master/resources/localization/list.txt.
 
 2.  Create template file(*.POT) with GNUgettext command:
     ```
-        xgettext --keyword=L --add-comments=TRN --from-code=UTF-8 --debug -o Slic3rPE.pot -f list.txt
+        xgettext --keyword=L --add-comments=TRN --from-code=UTF-8 --debug -o PrusaSlicer.pot -f list.txt
     ```
 
     Use flag `--from-code=UTF-8` to specify that the source strings are in UTF-8 encoding