From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] truetypefs(4)
Date: Fri, 7 Feb 2020 13:36:03 +0900 [thread overview]
Message-ID: <A0DB6C43DB57E96007E98E750F8C50B2@hera.eonet.ne.jp> (raw)
In-Reply-To: 5436B6CCE1EE21380668D6999134F1FA@hera.eonet.ne.jp
Ahahaha, if we use bit map font like lucisasans/unicode.8.font,
we cannot see what is the problem...
Kenji
> term% truetypefs
> term% font=/n/ttf/ipag.ttf.14/font
> を使って書いて見ました(wrote above settings)
>
> 練習です(this is exercise)
> 大阪(Osaka)
>
> hmmm, it's not easy what is the problem here...
> Meiryo.ttf has license problem, and I do not use it here.
>
> Kenji
next reply other threads:[~2020-02-07 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 4:36 kokamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-07 4:32 kokamoto
2020-02-07 4:25 kokamoto
2020-02-06 4:32 kokamoto
2020-02-06 9:13 ` Julius Schmidt
2020-02-06 4:19 kokamoto
2020-02-05 10:15 truetypefs(4) kokamoto
2020-02-05 11:31 ` [9front] truetypefs(4) Nicola Girardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A0DB6C43DB57E96007E98E750F8C50B2@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).