Skip to main content

让LaTeX支持utf8

买了直通车,可以下到cyberbit.ttf了,于是想试试utf-8的LaTeX

步骤是:

1.到http://www.unruh.de/DniQ/latex/unicode/下载安装unicode.tgz
这一步我没有做,我是用apt装的latex-ucs

2.到ftp://ftp.netscape.com/pub/communicator/extras/fonts/windows/ 下个cyberbit.ttf
copy至/usr/share/texmf/fonts/truetype/CJK

3.下载http://edt1023.sayya.org/tex/ipeucs/cyberb.sh,放在临时目录下,并把cyberbit.ttf也拷过来,运行cyberb.sh

4.依下表将生成的文件/目录拷到对应位置
tfm /usr/share/texmf/fonts/tfm/CJK/cyberb
enc /usr/share/texmf/pdftex/enc
cyberb.map /usr/share/texmf/pdftex/config/cyberb.map

注意,第一行表示把生成的tfm目录中的所有文件拷到/usr/.../cyberb/中去,第二行类似

5.在/usr/share/texmf/pdftex/config/cyberb.map末尾加上一句
map +cyberb.map

6.好像需要在/usr/share/texmf下运行texhash,不知道是否是必需的。

这样就弄完了

本来ucs的doc中说使用方法是
\usepackage{ucs}
\usepackage[utf8]{inputenc}
然后文档中直接打中文就行了
但是我这不行

我发现CJK的utf8可以用了,方法是
\usepackage{CJK}

...

\begin{CJK}{UTF8}{song}
中文
\end{CJK}

当然了,tex文档要以utf8编码保存

字体还行吧,我对字体美观程度要求还不算高。
以后再研究研究怎么弄ucs

Comments

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...