Skip to main content

ubuntu 7.04 latex 中文支持

ubuntu升级到7.04后，我的latex突然不能用了，出现

undefined control sequence: ..

后来发现编译英文的没问题，说明还是中文的事

一开始重装了几遍，都没用，然后我怒了，把tetex*, latex-cjk*等包都删掉，然后把/usr/share/texmf,
/usr/share/texmf-tetex等目录删掉，再重装上面那些包。不过配置时出现了错误。

运行了几次dpkg --configure
-a后发现问题出在updmap-sys上，进一步发现说找不到"cjk.map"，仔细想了想，这应该是上次我手工添加中文字体留下来的文件，查了若干资料后发现应该问题醋在/etc/texmf/updmap.d/10local.cfg,
我这里应该清空它。

然后configure就通过了。

然而，这之后编译以前的文件仍是不认中文，又查了半天资料，原来我装的那些字体的字体名不是song, kai等，而是gbsn, gkai，改过来就好了。

因此现在ubuntu下配置中文latex再也不用像从前那样麻烦了（好像其实以前也有字体包，是我没发现或不会用吧-_-b,另外如果想装自己的ttf，可能还要像前面的文章说的那样折腾一次。不过注意记住改了哪些文件，以免发生今天这种情况）

看看了这些包的帮助,对CJK三国文字支持的都不错,支持的编码页很多,GBK,Bg5,UTF8样样行,让我眼前一亮.(当然CJK本身就行,我这是因为终于装好了)

不错

Labels:

Comments

Post a Comment

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 ...
Post a Comment
Read More »

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...
Post a Comment
Read More »

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...
Post a Comment
Read More »