That's a sign that your .font file is wrong, for instance that it contains a loop or hole in its definition. In particular it's about the textual Plan 9 font file, not the subfont images.
But it should be easy to figure out: where does rune U+0000 map to, according to the font? I suspect the answer is "nowhere" and that's what's wrong. -rob On Tue, Jan 10, 2017 at 2:05 AM, Mathieu Lonjaret < mathieu.lonja...@gmail.com> wrote: > Hi, > > I've been using the Go fonts (in p9p acme) for a week now, and so far I > kind of like it, so thanks for making it. > > Anyway, I've just noticed this error message in the terminal from which I > launched acme, so I assume acme is the one complaining about it, but I > haven't dug any deeper. > > "stringwidth: bad character set for rune 0x0000 in /mnt/font/Go > Mono/11a/font" > > I don't know what it is I did to make it appear, and it looks more like a > warning, but given that I had never seen this message before with other > fonts, I figured I'd report it. > > Do you want me to grep into acme, or report a bug somewhere? Or is that an > expected warning you already know about? > > Regards, > Mathieu > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
