<h3>Avoid naming <code>.gcode</code> files with non-ASCII characters</h3>
<em>(this includes <a href="https://en.wikipedia.org/wiki/Extended_ASCII" rel="nofollow noreferrer">EASCII</a>)</em>
<p>I know of no firmware on a printer that can handle files that have characters not present in the set of 95 non-control <a href="https://www.w3schools.com/charsets/ref_html_ascii.asp" rel="nofollow noreferrer">American Standard Code for Information Interchange characters</a> by default. Marlin, for example, can't process the characters <code>ä</code> <code>ö</code> <code>ü</code> &amp; <code>€</code> as these all are missing in the ASCII.</p>
<h3>Avoid having more than one <code>.</code></h3>
<p>Nowadays the <code>.</code> is no longer a fully reserved character in file names, so a file can be named <code>0.5mm Gauge Block.stl</code> on Windows without problems.</p>
<p>Ultimaker Cura will <strong>cut</strong> the name at the <code>.</code> before the extension when generating the <code>.gcode</code>. This is mainly done to prevent tons of errors that could crop up in firmware that might not be able to deal with it. Remember that this behavior can lead to overwriting files - our <code>0.5mm Gauge Block.stl</code> would generate <code>0.gcode</code>, as would <code>0.1.5 Penholder.stl</code> (that follows a version naming convention).</p>
<h3>Avoid reserved characters</h3>
<p>Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, <code>/</code> <code>\</code> <code>:</code> <code>?</code> <code>*</code>.</p>

CC BY-SA 4.0
2019-02-25T15:46:49.730Z
Agreed - I always convert "my_part_reduce0.5" to "my_part_reduce0p5" for that reason.
Carl Witthoft
CC BY-SA 4.0
2019-02-24T20:16:47.207Z
2019-02-25T15:18:59.797Z
2020-06-18T08:29:41.667Z
Trish
<p>Special characters like <code>Ä</code> <code>Ö</code> or <code>Ü</code> in the stl-filename resulted in Ultimaker Cura creating a comment of the filename in the g-code that read like </p>

<pre><code>;MESH:Loki_hörner_v2.stl
</code></pre>

<p>This apparently could not be parsed by the Anet A8, leading to an error and halt.</p>

CC BY-SA 4.0
2019-02-25T12:32:33.963Z
It's great that you found and shared the answer. Did you get it to work by removing the character with umlauts?
Davo
CC BY-SA 4.0
2019-03-06T08:56:01.053Z
@Davo yes, after removing/replacing the umlaut in the stl-filename, reslicing it, it works. (i did not test to manually remove the umlauts from the gcode manually, but I have a strong believe that this would work too)
Horitsu
CC BY-SA 4.0
2019-02-24T21:13:49.370Z
2019-02-25T15:20:19.893Z
2019-02-25T15:20:19.893Z
Horitsu
<p>I have an issue with my Anet A8 printer and how it interlocks with Ultimaker Cura. </p>

<p>I want to print this file named <code>Loki_hörner_v2.stl</code>and Cura slices it fine, but when it comes to printing all the preheat happens, but then it stops, not going on at all. What might be wrong here?</p>

<ultimaker-cura><anet-a8><troubleshooting><print-failure><bug>
Anet A8 stops printing
Horitsu
# Anet A8 stops printing

(Asked by: username_0 on 2019-02-24)

I have an issue with my Anet A8 printer and how it interlocks with Ultimaker Cura.

I want to print this file named `Loki_hörner_v2.stl`and Cura slices it fine, but when it comes to printing all the preheat happens, but then it stops, not going on at all. What might be wrong here?

**Tags:** ultimaker-cura, anet-a8, troubleshooting, print-failure, bug


---

## 2 answers

### Answer by username_0 on 2019-02-24. Score: 5 | Accepted answer

Special characters like `Ä` `Ö` or `Ü` in the stl-filename resulted in Ultimaker Cura creating a comment of the filename in the g-code that read like

```
;MESH:Loki_hörner_v2.stl

```

This apparently could not be parsed by the Anet A8, leading to an error and halt.

> **Comments:**
> **username_3**: It's great that you found and shared the answer. Did you get it to work by removing the character with umlauts?  
> **username_0**: @username_3 yes, after removing/replacing the umlaut in the stl-filename, reslicing it, it works. (i did not test to manually remove the umlauts from the gcode manually, but I have a strong believe that this would work too)  

---

### Answer by username_1 on 2019-02-24. Score: 4

### Avoid naming `.gcode` files with non-ASCII characters

*(this includes [EASCII](https://en.wikipedia.org/wiki/Extended_ASCII))*

I know of no firmware on a printer that can handle files that have characters not present in the set of 95 non-control [American Standard Code for Information Interchange characters](https://www.w3schools.com/charsets/ref_html_ascii.asp) by default. Marlin, for example, can't process the characters `ä` `ö` `ü` & `€` as these all are missing in the ASCII.

### Avoid having more than one `.`

Nowadays the `.` is no longer a fully reserved character in file names, so a file can be named `0.5mm Gauge Block.stl` on Windows without problems.

Ultimaker Cura will **cut** the name at the `.` before the extension when generating the `.gcode`. This is mainly done to prevent tons of errors that could crop up in firmware that might not be able to deal with it. Remember that this behavior can lead to overwriting files - our `0.5mm Gauge Block.stl` would generate `0.gcode`, as would `0.1.5 Penholder.stl` (that follows a version naming convention).

### Avoid reserved characters

Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, `/` `\` `:` `?` `*`.

> **Comments:**
> **username_2**: Agreed - I always convert "my_part_reduce0.5" to "my_part_reduce0p5" for that reason.  

---

