# Unicode: a bad idea, in general

**URL:** https://discourse.julialang.org/t/unicode-a-bad-idea-in-general/99897
**Category:** General Usage
**Created:** [June 5, 2023, 3:25pm UTC](https://discourse.julialang.org/t/unicode-a-bad-idea-in-general/99897 "2023-06-05T15:25:07Z")
**Posts on this page:** 1
**Showing post:** 76

<div class="post-metadata">

### Author: ![jar1](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jar1](https://discourse.julialang.org/u/jar1)
#### Post date: [June 7, 2023, 5:35am UTC](https://discourse.julialang.org/t/unicode-a-bad-idea-in-general/99897/76 "2023-06-07T05:35:21Z")

</div>

It seems like there is a setting to support UTF-8 input on the specific terminal mentioned in another thread.

> [@Source files with non-ascii names: how?](https://discourse.julialang.org/t/source-files-with-non-ascii-names-how/6827/4):
>
> In this day and age, it is perfectly reasonable to tell people use an editor that supports Unicode and the UTF-8 encoding. (Julia doesn’t even run on ancient systems where a lack of Unicode support might be hard to circumvent. And the only still-extant text editors I can find that don’t support unicode are ed and pico, and no sane programmer would use either of these…are there any other examples?) Correction: apparently there may be one popular programming text editor that still doesn’t prope…

---

_[View the full topic](https://discourse.julialang.org/t/unicode-a-bad-idea-in-general/99897)._