Re: [go-nuts] Re: error message with Go fonts

2017-01-10 Thread Mathieu Lonjaret
Ah thanks, I had forgotten to try reading that one. Here goes: $ 9p read 'font/Go Mono/11/font' 16 13 0x 0x001f x.bit 0x0020 0x003f x0020.bit ... On 10 January 2017 at 17:13, andrey mirtchovski wrote: > > Sorry, I don't understand what you mean

Re: [go-nuts] Re: error message with Go fonts

2017-01-10 Thread andrey mirtchovski
> Sorry, I don't understand what you mean by the textual Plan 9 font file. do $ 9p read 'font/Go Mono/11/font' instead. the second line should point to the glyph file for runes 0x0 to 0xff, something like: 0x 0x00ff x.bit -- You received this message because you are subscribed to the

[go-nuts] Re: error message with Go fonts

2017-01-10 Thread Mathieu Lonjaret
Sorry, I don't understand what you mean by the textual Plan 9 font file. The actual font is installed at /usr/share/fonts/truetype/go/Go-Mono.ttf , and I think acme accesses it through fontsrv. If I do $ 9p ls 'font/Go Mono/11/' I get: font x.bit x0020.bit x0040.bit ... x2660.bit xf800.bit

[go-nuts] Re: error message with Go fonts

2017-01-09 Thread Rob Pike
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+ map to, according to the font? I suspect the