[9fans] lucidasans and 日本語表示

[k***@hera.eonet.ne.jp]

Acme uses default font of lucidasans/euro.8.font, and it has
no ハンカク数字、全角数字etc, which make me trouble to
show Japanese mails from other systems. So, please add the
line to the bottom of /font/lib/bit/lucidasans/euro.8.font
as bellow:

.....
.....
0x9a01 0x9bf5 ../shinonome/k14.9a01
0x9c04 0x9dfd ../shinonome/k14.9c04
0x9e1a 0x9fa0 ../shinonome/k14.9e1a
0xff01 0xffe5 ../shinonome/k14.ff01 <---- this line
0xFFFD 0xFFFD 0x80 lsr.14

Kenji

[Rob Pike]

That font is called euro because it does not have the Asian ideographs
and is cheaper to load. Use unicode.8.font if you want them; I have
set font=unicode.9.font since the beginning.

The real question is what the default font should be; I leave that
decision to others.

-rob

[Benjamin Huntsman]

> The real question is what the default font should be

Not that my opinion counts for anything, but changing the font to latin1.7.font (or sometimes typelatin1.7.font) is usually the first thing I do on a fresh Plan 9 install.
It's very readable, and you can fit a whole lot more on an average window the the current default pelm.

-Ben

[k***@hera.eonet.ne.jp]

> The real question is what the default font should be; I leave that
> decision to others.

You mean change the hardcoded font name
in /sys/src/cmd/acme/acme.c?
By the way, I'll follow your suggestion to add 日本語
to unicode.8.font.

Kenji

[Steven Stallion]

On Sat, Apr 28, 2012 at 9:42 PM, <***@hera.eonet.ne.jp> wrote:
>> The real question is what the default font should be; I leave that
>> decision to others.
>
> You mean change the hardcoded font name
> in /sys/src/cmd/acme/acme.c?
> By the way, I'll follow your suggestion to add 日本語
> to unicode.8.font.

Hi Kenji,

Something that I've found useful is to define the following in your profile:

fixedfont=/path/to/my/font
fn acme {builtin acme -f $fixedfont $*}

HTH,

Steve

[erik quanstrom]

> font = /lib/font/bit/fixed/unicode.7x13.font
> fn acme {builtin acme -f $font $*}
>
> to your lib/profile. This will set your acme and rio fonts to
> unicode.7x13.font. Substitute the pathname to your preferred font file,
> then reboot your terminal.

or plumb the string
Local font = /lib/font/bit/fixed/unicode.7x13.font; fn acme {builtin acme -f $font $*}
instead of rebooting.

- erik

[Lyndon Nerenberg]

> You mean change the hardcoded font name
> in /sys/src/cmd/acme/acme.c?

No, add something like:

font = /lib/font/bit/fixed/unicode.7x13.font
fn acme {builtin acme -f $font $*}

to your lib/profile. This will set your acme and rio fonts to
unicode.7x13.font. Substitute the pathname to your preferred font file,
then reboot your terminal.

--lyndon

[Rob Pike]

On Sun, Apr 29, 2012 at 2:55 PM, Lyndon Nerenberg <***@orthanc.ca> wrote:
>> You mean change the hardcoded font name
>> in /sys/src/cmd/acme/acme.c?
>
>
> No, add something like:
>
> font = /lib/font/bit/fixed/unicode.7x13.font
> fn acme {builtin acme -f $font $*}

You don't need to do the second line. Acme uses $font automatically.

-rob

[k***@hera.eonet.ne.jp]

> You don't need to do the second line. Acme uses $font automatically.

Yes, I just added ../shinonome/k.14.xxxx to /lib/font/bit/lucidasans/unicode.8.font,
such as:
0x3000 0x30fe ../shinonome/k14.3000
0x4e00 0x4ffe ../shinonome/k14.4e00
0x5005 0x51fe ../shinonome/k14.5005
0x5200 0x53fa ../shinonome/k14.5200
0x5401 0x55fe ../shinonome/k14.5401
0x5606 0x57fc ../shinonome/k14.5606
....
0x961c 0x97ff ../shinonome/k14.961c
0x9801 0x99ff ../shinonome/k14.9801
0x9a01 0x9bf5 ../shinonome/k14.9a01
0x9c04 0x9dfd ../shinonome/k14.9c04
0x9e1a 0x9fa0 ../shinonome/k14.9e1a
0xfb1e 0xfb1e ../lucida/Althebrew.7.0
0xff01 0xffe5 ../shinonome/k14.ff01

and set font=/lib/font/bit/lucidasans/unicode.8.font. It works charm.
Thank you very much all.

Kenji

[k***@hera.eonet.ne.jp]

I lied.

I forgot to delete the ../shinonome lines from euro.8.font file.
Then, I found the the "fn acme {builtin acme -f $font $*}" line
is neccessary on my version of acme.

Kenji

>> You don't need to do the second line. Acme uses $font automatically.
>
> Yes, I just added ../shinonome/k.14.xxxx to /lib/font/bit/lucidasans/unicode.8.font,
> such as:
> 0x3000 0x30fe ../shinonome/k14.3000
> 0x4e00 0x4ffe ../shinonome/k14.4e00
> 0x5005 0x51fe ../shinonome/k14.5005
> 0x5200 0x53fa ../shinonome/k14.5200
> 0x5401 0x55fe ../shinonome/k14.5401
> 0x5606 0x57fc ../shinonome/k14.5606
> ....
> 0x961c 0x97ff ../shinonome/k14.961c
> 0x9801 0x99ff ../shinonome/k14.9801
> 0x9a01 0x9bf5 ../shinonome/k14.9a01
> 0x9c04 0x9dfd ../shinonome/k14.9c04
> 0x9e1a 0x9fa0 ../shinonome/k14.9e1a
> 0xfb1e 0xfb1e ../lucida/Althebrew.7.0
> 0xff01 0xffe5 ../shinonome/k14.ff01
>
> and set font=/lib/font/bit/lucidasans/unicode.8.font. It works charm.
> Thank you very much all.
>
> Kenji

[Lyndon Nerenberg]

On 2012-04-29, at 1:30 AM, Rob Pike wrote:

> You don't need to do the second line. Acme uses $font automatically.

Only the p9p version of acme. The native plan9 acme doesn't.

[Rob Pike]

That's odd but easy to change.

-rob

[Lyndon Nerenberg]

On 2012-04-29, at 3:38 PM, Rob Pike wrote:

> That's odd but easy to change.

After chasing down and reading Presotto's rant about proportional fonts in acme? I will live happily ever after with acme's current default behaviour, just to honour one of the best flames of all time :-)

--lyndon

[Matthew Veety]

On 04/29/12 18:45, Lyndon Nerenberg wrote:
>
> On 2012-04-29, at 3:38 PM, Rob Pike wrote:
>
>> That's odd but easy to change.
>
> After chasing down and reading Presotto's rant about proportional fonts in acme? I will live happily ever after with acme's current default behaviour, just to honour one of the best flames of all time :-)
>
> --lyndon
>
>

Well either way I fixed that shit. Hit me up if you want me to post the
patch.

On another note: why does p9p's acme work as expected but not plan9's?

--
Matthew Veety

[Lyndon Nerenberg]

On 2012-04-29, at 4:38 PM, Matthew Veety wrote:

> Well either way I fixed that shit. Hit me up if you want me to post the patch.

Fuck that – repost the flame!

The acme fix is trivial in comparison ;-)