Thank you for your report.

The bug with the basic text view for a feature is fixed in rev#100788 of EiffelStudio 17.11 intermediate release.

We were able to reproduce the issue with the Search-Replace tool and printing, but there is no fix yet.

As to documentation generation, there is no quick fix because it requires changes to the current infrastructure. The documentation is generated using so called filters. You can find them in the directory .../studio/filters of you EiffelStudio installation. Everything is plain text and EiffelStudio does not know how to encode non-ASCII characters (if any). At the moment it relies on the current system encoding to encode non-ASCII. Therefore, there is no easy way to improve it under Windows because it does not allow for using UTF-8 as a system code page. But on Linux (and MacOS) it should be possible to specify a suitable locale and to run EiffelStudio with this environment setting. The appropriate locale is set with the commands

   export LC_ALL=en_US.UTF-8
   export LANG=en_US.UTF-8
   export LANGUAGE=en_US.UTF-8

If this does not work, you can try en_US.utf-8 instead. If running EiffelStudio in such an environment changes generated HTML files, you may also need to add a tag "meta" in the HTML filter to specify character encoding "UTF-8". Please, tell us if this helps or if you encounter any other issues.

The trick with system encoding might work only with certain filters, such as HTML or XML, but not with all of them. For example, RTF encodes non-ASCII character in a special way, postscript uses a fairly sophisticated scheme to reference glyphs, etc. The current text filter-based scheme cannot handle these cases.