[image] Can you find the \rho? And not confuse it with p?

Python version: [Captura de Tela 2023-06-06 às 20.40.20] UTF-8 really makes those equation more easy to follow.

My point is that an ascii-only campaign comes at a cost and that having a realistic model of one’s audience is key in making decisions about readability. If there are lots of people using Julia without the ability to render Unicode, for example, I’d like to know about them and their circumstances; …

Thanks for clarifying. Well, as I said, I don’t have strong feelings about it one way or another. I certainly prefer unicode, but there also are enough people out there in the ecosystem who have repeatedly voiced their concerns and opposition to unicode-only APIs that I think it’s not such a big de…

[image] PetrKryslUCSD: people with dyslexia people with low vision people with lower reading levels and abilities people with learning difficulties non-native English speakers people with limited time or attention span I can’t speak to dyslexia or low vision. But I don’t see how using rho …

There are some examples of symbols in this thread that I find much less clear than the ASCII transcription of them. To a degree that may be a function of the screen resolution that is available for the display of the character, of course. But, when sticking to ASCII, one may be sure that “what you s…

[image] PetrKryslUCSD: But, when sticking to ASCII, one may be sure that “what you see is what you get”. Not so with many Unicode characters. That’s a fair point. I am sometimes surprised by what shows up on github. And even using the excellent JuliaMono, some character combinations appear …

[image] jar1: My point is that an ascii-only campaign comes at a cost Here’s a little anecdata: my project is 3,597 lines of code (in src, plus another 1,730 in docs+test), of which ~30 particularly easy-to-write lines are devoted to this API translation. It doesn’t feel like much cost to me…

[image] moble: Note that a Unicode API won’t just “encourage”, it will require users to use Unicode. That might be enough to discourage the particularly lazy Julia user, but also make it literally impossible to use even slightly fancy Unicode from python. Unicode is fine within code where i…

[image] ChrisRackauckas: clusters which do not support Unicode inputs Do you happen to have a reference to these clusters? I haven’t seen that restriction myself.

Lots of older clusters like the XSEDE ones had this restriction. It can greatly dependent on the terminal that is used too, where newer terminal versions support it on “standard” hardware, but as you get to other hardware or more legacy systems you tend to have more issues with unicode.

Unicode: a bad idea, in general

General Usage

jar1 June 7, 2023, 5:35am 76

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

Topic		Replies	Views
Warning against Unicode confusables Internals & Design unicode	51	2461	January 13, 2024
Syntax: Escape hatch for unicode haters Internals & Design syntax , unicode	128	5684	January 16, 2024
Naming: Remove all underscores to matter what? General Usage	123	7923	January 28, 2018
Unicode \epsilon\_y New to Julia	33	6076	October 10, 2019
Fonts in VS Code VS Code	26	4028	August 29, 2022

Unicode: a bad idea, in general

Related topics