<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<oembed>
  <author_name>derwind</author_name>
  <author_url>https://blog.hatena.ne.jp/derwind/</author_url>
  <blog_title>らんだむな記憶</blog_title>
  <blog_url>https://randommemory.hatenablog.com/</blog_url>
  <categories>
    <anon>font</anon>
  </categories>
  <description>T1_SPEC.pdf p.8 に Type 1 BuildChar begins by using the character code as an index into the Encoding array in the font dictionary to obtain the name of the character to be built. This step is explained in the PostScript Language Reference Manual; among other advantages, it enables a user to re-encode…</description>
  <height>190</height>
  <html>&lt;iframe src=&quot;https://hatenablog-parts.com/embed?url=https%3A%2F%2Frandommemory.hatenablog.com%2Fentry%2F2022%2F01%2F11%2F212208&quot; title=&quot;Type 1 フォント (4) - らんだむな記憶&quot; class=&quot;embed-card embed-blogcard&quot; scrolling=&quot;no&quot; frameborder=&quot;0&quot; style=&quot;display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;&quot;&gt;&lt;/iframe&gt;</html>
  <image_url></image_url>
  <provider_name>Hatena Blog</provider_name>
  <provider_url>https://hatena.blog</provider_url>
  <published>2022-01-11 21:22:08</published>
  <title>Type 1 フォント (4)</title>
  <type>rich</type>
  <url>https://randommemory.hatenablog.com/entry/2022/01/11/212208</url>
  <version>1.0</version>
  <width>100%</width>
</oembed>
