summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/fonts/xq/README
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/fonts/xq/README')
-rw-r--r--Master/texmf-dist/doc/fonts/xq/README56
1 files changed, 56 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/fonts/xq/README b/Master/texmf-dist/doc/fonts/xq/README
new file mode 100644
index 00000000000..5469b94687a
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/xq/README
@@ -0,0 +1,56 @@
+readme for the xq-package
+
+
+this style is made for writing about chinese chess. Unfortunately, it has become a real monster, but i did
+not find a better way to get what i wanted - which is probably due to the fact, that i never wrote something
+like this before - so dont mind me my rather "simple" solution.
+
+
+xq is under the LaTeX project public license
+
+
+
+The package contains:
+
+the style file - xq.sty
+basefont - xqbase.mf
+hint file needed by xqbase - hints.mf
+font files for "normal" sized boards - xqnormal.mf
+font files for "large" sized boards - xqlarge.mf
+an example file demonstrating the abilities of the style - xqexample.tex
+the example file in pdf format for taking a quick look - xqexample.pdf
+and finally this readme file - README
+
+
+
+On my local tree it works with the files copied to the following places:
+
+/texmf/tex/latex/xq/xq.sty
+
+/texmf/fonts/source/public/xq/xqbase.mf + xqnormal.mf + xqlarge.mf + hints.mf
+
+
+
+If problems occur, that the fonts are not loadable, put everything in one folder with the input file and
+run latex. That produces the .tfm then copy these to:
+
+/texmf/fonts/tfm/public/xq/xqnormal.tfm + xqlarge.tfm
+
+
+
+
+Problems:
+
+There are small gaps between pieces and boardlines in the diagrams, this is due to the font. You can avoid
+this by putting the unit length for the picture in the style file a little smaller. However, i found it
+looks better like it is now.
+
+The boards are sometimes set a bit unclean on a pdf output file. I solved the problem by producing a pdf
+via dvi and ps. After that procedure i always had a clean output in acroread.
+
+
+
+I hope everything works like it should, if not, please let me know...
+
+Stephan Weinhold, 09/2006
+stewei@surfeu.de