[Tag search]

tikzpeopleで新しいキャラ

Tuesday 12 December 2017, 14:59

これは TeX & LaTeX Advent Calendar 2017 の 13 日目の記事です。 昨日は tattsan さんでした。 明日は p_typo さんです。 外の年も記事を書きました。 2014 2015 2016

Nils Fleishhacker さんからのパケージ『tikzpeople』は、 人のノードを書きできます。 マイクロソフトビジオのようを持ちます。 たとえば暗号プロトコルので便利です。 だから Alice と Bob の名前あります。

今日新しいキャラを上げましょう。 トトロとカッパと四人の JK です。

Circuit-Macrosで回路図を書いて

Wednesday 14 December 2016, 10:34

僕の新しい仕事がアナログシンセのデザインです。 LaTeXでユーザーマニュアルを作りたいです。 ドキュメントの中で回路図を書きたいです。 今日、Circuit-Macrosで回路図を書き方の勉強しましょう。 よろしくお願いします。

これはTeX & LaTeX Advent Calendar 2016に僕の寄贈です。昨日はmarimo-nekomimiさんの日です。 明日、Yasuhide Minodaさんの日です。

LaTeXで文章の空白の植字をしましょう

Thursday 10 December 2015, 13:09

日本語が分かっても、時々英語で植字をしなければならないです。 英語では文章と言葉の中で、いつも空白あります。 LaTeXを使えば、もしかしたら文章と言葉の空白が難しいです。 今日本件の勉強をしましょう。

これはTeX & LaTeX Advent Calendar 2015に僕の寄贈です。

Notes on notes on the plane

Sunday 2 August 2015, 04:09

I have posted a detailed set of notes (PDF file) describing the theory behind my Black Swan Suite, detailing the endless chase of Elmer and Daffy across Penrose, pinwheel, and other nonperiodic tilings of the plane. Fans of music and computational geometry may find the document interesting. At the very least, it was fun to typeset.

lilypond-bookとLaTeXで音楽の植字

Friday 5 December 2014, 23:15

数学と理学ではLaTeXが有名です。 論文を書ければいつもLaTeXを使っています。 でもLaTeXではいろいろな文書ができます。 今日LaTeXとlilypond-bookで音楽の書くことを見ましょう。

[音楽]

これはTeX & LaTeX Advent Calendar 2014に僕の寄贈です。

TikZでマック・ペイントの床しいタイリングを描きましょう

Friday 13 December 2013, 13:09

TeXとLaTeXで画を書いたらTikZは便利とポピュラーです。 みんなはきれいなグラフィクスを作っています。 たとえば、これがtexample.netから一つのクリスマスツリーです。

[クリスマスツリー]

しかし、ただのグラフィクスには興味ありません。 今日は1984年からノスタルジックの画を書きましょう。 マック・ペイントを思い出しませんか? そう…

プリティプリントの試作

Saturday 7 December 2013, 10:07

今年「TeX & LaTeX Advent Calendar」に入りました。 14日に私の書き込みを書きます。 それ前このサーバにGeSHiと言うプリティプリントソフトを備え付けています。 この書き込みはGeSHiのテスト・ポストです。

Where do I draw the line?

Monday 21 January 2013, 14:49

It's a very common pattern in the Han writing system that a character will be made of two parts that are themselves characters, or at least elements resembling characters, placed one above the other or one next to the other. For instance, 音 (sound) can be split into 立 (stand up) above 日 (day); and 村 (village) can be split into 木 (tree) next to 寸 (inch). This kind of structure can be nested, as in 語 (language). One can do a sort of gematria with the meanings, (what exactly is the deep significance of "village = tree + inch"?) but that's not the direction I'm interested in going today. Here's the thing: in the Tsukurimashou project, these two ways of constructing characters each correspond to a piece of code that's invoked many times throughout the system, and I thought it would be interesting to look at how often the different parameter values are used.

Ideographic Description Sequences: some thoughts

Monday 19 December 2011, 15:14

I went through a bit of a crunch to get Tsukurimashou 0.5 out the door before my year-end vacation. With that done, and at least 99 kanji to do before the next planned release, I have a chance to sit back and think about some longer-term and spin-off projects. Here are some ideas on kanji searching.

UPDATE: A prototype implementation of the system described here now exists as part of the Tsukurimashou project, and you can check it out via SVN from there. Packaged releases will be available eventually.

"Grimoire" fonts

Sunday 26 June 2011, 10:15

Here's a project that provides, among other things, free vector fonts of magical glyphs from the Lesser and Greater Keys of Solomon. I found it by way of sourceforge.jp's flagging it as a similar project to Tsukurimashou.

Chinese Seal Script fonts

Friday 25 February 2011, 06:51

Here's a page of Chinese fonts including a few for the Seal Script. Could come in handy...

Typographical history of the TTC

Tuesday 18 January 2011, 11:42

Here's a Web log article, with several links and a couple of posters for sale, on something I've wondered about before: the unique typeface used for station names and some other signage on the TTC.

Electric kerning

Thursday 9 December 2010, 20:57

It's not like I don't have enough projects to work on already. Nonetheless, I had an idea I thought was pretty cool, and I'm going to at least describe it here, whether I end up implementing it or not.

Okay, so: kerning. If you're setting type, you need to know where to put each glyph in relation to the previous one. In the old old days, it was easy because each glyph came on a little metal block and you'd just set them right next to each other and clamp them in place. But a computer (and, earlier, a phototypesetting machine) has the opportunity to make a decision. And if you just have a fixed bounding box for each glyph and set them side by side, you run into problems when you have situations like a capital A next to a capital V. "AV". Using the bounding boxes that would be correct for those letters in other contexts, you end up putting too much space between them. You need to squeeze them together so that part of the V projects into the space that the A, if it were next to something else, would reserve for itself. This squeezing together is called "kerning."

The Terrible Secret of OpenType Glyph Substitution

Monday 6 December 2010, 13:18

I was up until 3 this morning trying to figure out how to make OpenType glyph substitution work. That, in itself, is not news. Anyone who has tried to write substitution rules for OpenType fonts has probably gone through something similar. What is unusual, though, is that I not only succeeded, but also figured out the undocumented underlying principle so that I can predictably succeed in the future; as far as I can tell, the more usual practice is to just try things at random until one eventually either gets it working by accident, or gives up, without having learned anything useful either way.

The purpose of this entry is to provide the important information that I wasn't able to find on the Net and wish I had had. There is one important point I call the Terrible Secret, which makes all the difference to getting it to work; but rather than jump to that immediately I'm going to give the needed background first. I'll be using the terms that make sense to me, rather than the "easy" but uselessly vague simplified style used by all existing documentation I found.