chiark - git - ian - xfonts-traditional.git/log

unfuzzy the translations

git-checkout 51f936cff73344e45074614799cd1ffcb2a62ec4
debconf-updatepo
cp templates.pot templates.pot.orig
git-checkout master
debconf-updatepo
git-checkout *.po
msguntypot -o templates.pot.orig -n templates.pot *.po
rm templates.pot.orig
git-commit -a

undo English changes

exactly as found in #660965 message 34

English l10n improvements

changelog: add an item and finalise

debian/control: add missing libsys-cpu-perl dependency

fix wrong bug# (oops!) (again)

fix wrong bug# (oops!)

support --always-reprocess

tolerate pcf2bdf crashing

processpcfgz: completely revamped subprocess data structures and error handling

processfontdir: better message for failures

bdftopcf: special-case "no bdf data" return

fix message ("none") return value s from processbdf and hence processpcfgz

changelog: mention parallelism

update-xfonts-traditional: process fonts in parallel

Exploit multicore systems to speed up the runtime when processing
needs to be done.

Some timing results on a dual-core 1.50GHz Atom N550 laptop:

-j1
  real    0m43.035s
  user    0m43.319s
  sys     0m37.830s

-j2
  real    0m23.113s
  user    0m40.643s
  sys     0m30.486s

-j3
  real    0m21.910s
  user    0m43.707s
  sys     0m30.674s

-j4
  real    0m22.038s
  user    0m44.695s
  sys     0m31.058s

This system has hyperthreading so looks like 4 cores.  Based on this
I have set the number of processing threads to the number of cpus.

debian/copyright: Explain the origin and copyright status of 6x13O.

Provide 6x13O as a BDF source and generate a PCF from it at build time.

Just in case we feel the need to edit it later. Also, BDF is slightly
closer to a `preferred form for modification'.

Support for bold and oblique versions of 6x13.

There is no traditional version of 6x13O, so I just hacked the font
so that it looks like an italicized version of trad 6x13 rather than
Kuhn 6x13.

Signed-off-by: Mark Wooding <mdw@distorted.org.uk>

mkrules: Correct handling of multiple foundry mappings.

If multiple PCFs request the same mapping, only write it once; if
they induce inconsistent mappings, report an error. Make sure
there's a newline between foundry mapping entries.

Signed-off-by: Mark Wooding <mdw@distorted.org.uk>

mkrules: Handle multiple files with the same metrics.

If we had two PCF files with the same metrics previously, we'd overwrite
the rules file from the first with a new file from the second. Keep
track of which files we've written during the run, and append to them if
we've already started writing. Finish them all up at the end.

Signed-off-by: Mark Wooding <mdw@distorted.org.uk>

Makefile: Make sure the `rules' directory exists.

Git won't create it so we must do so here.

Signed-off-by: Mark Wooding <mdw@distorted.org.uk>