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

[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 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 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.

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

[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 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.

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

[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
xfb00.bit

and it does not seem like any of these are textual representations.
(they're probably the subfont images you're talking about?).


On 9 January 2017 at 20:44, Rob Pike  wrote:

> 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 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 0x 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.

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

[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 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 0x 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.