[PD] unicode symbols and Pd

[Ingo]

> IOhannes m zmölnig wrote:
>
> in the meantime you could start by installing a couple of fonts (preferably
> ones that have the missing symbols) on your system and then restart Pd.

I already have DejaVu and Helvetica installed that has all fonts that I need.
If I'm not completely off these should be distributed with Pd and be the same 
on all platforms, right?

If all characters were in the DejaVu / Helvetica fonts I should be able to 
display the alternative # (8983) with UTF-8.
It works on Windows with both older and newer software versions of Pd. Thus 
these characters should be there.
If they are not in the DejaVu font but elswhere how do I know what to install?

It would be soooooo easy to edit one single unused character of the fonts if I 
knew where they were.
Unfortunately I do not expect myself to be able to read through the entire Pd 
source code to find out.
The default font locations of Debian don't seem to do anything - at least not 
for me on Pd in Debian.

Ingo



> -----Original Message-----
> From: Pd-list [mailto:pd-list-bounces at lists.iem.at] On Behalf Of IOhannes m
> zmölnig
> Sent: Monday, January 18, 2021 12:43 PM
> To: pd-list at lists.iem.at
> Subject: Re: [PD] unicode symbols and Pd
>
> On 1/18/21 11:14 AM, Ingo wrote:
> > This means I probably have to wait another few years until someone
> > will fix the [canvas] issue for displaying a sharp "#".
>
> in the meantime you could start by installing a couple of fonts (preferably
> ones that have the missing symbols) on your system and then restart Pd.
>
> i'm using Debian for a couple of years, and i cannot remember any problems
> in the last decade.
>
> afaik, the only thing that does not work  are emojis. while they are 
> technically
> just unicode symbols, it seems that i cannot enter them (although they are
> displayed correctly, if you get them into the patch "by other means", like 
> [list
> tosymbol] or by editing the patch)
>
> fgmdsar
> IOhannes
>
>
>   apart from '#' in iemguis; but i think this has been covered extensively 
> in this
> thread during the last days.