%%% ==================================================================== %%% @TeX-font-metrics-file{ %%% author = "Alan Jeffrey and Ulrik Vieth and %%% Lars Hellstr{\"o}m", %%% version = "1.923", %%% date = "2003-03-29", %%% time = "16:25:58 +01:00", %%% filename = "ltpunct.mtx", %%% email = "fontinst@tug.org", %%% URL = "http://www.tug.org/applications/fontinst/", %%% checksum = "", %%% codetable = "ISO/ASCII", %%% keywords = "metrics, TeX, PostScript", %%% supported = "yes", %%% abstract = "This is a font metrics file, for use with %%% the fontinst utility. It deals with the %%% punctuation characters needed for the most %%% common latin font encodings.", %%% package = "fontinst", %%% dependencies = "fontinst.sty, fontdoc.sty", %%% } %%% ==================================================================== \relax \documentclass[twocolumn]{article} \usepackage{fontdoc}[2002/03/01] \showbranches \title{Latin punctuation} \author{Alan Jeffrey\and Ulrik Vieth\and Lars Hellstr\"om} \date{7 January 2003\\Version 1.923} \begin{document} \maketitle \metrics \needsfontinstversion{1.902} \usemtxpackage{ltcmds} \ProvidesMtxPackage{ltpunct} \begincomment \section{Punctuation} \subsection{Unfakable characters} \endcomment \unfakable{ampersand} \unfakable{asciicircum} \unfakable{asciitilde} \unfakable{asterisk} \unfakable{at} \unfakable{backslash} \unfakable{bar} \unfakable{braceleft} \unfakable{braceright} \unfakable{bracketleft} \unfakable{bracketright} \unfakable{colon} \unfakable{comma} \unfakable{dollar} \unfakable{emdash} \unfakable{endash} \unfakable{equal} \unfakable{exclamdown} \unfakable{exclam} \unfakable{greater} \unfakable{guillemotleft} \unfakable{guillemotright} \unfakable{guilsinglleft} \unfakable{guilsinglright} \unfakable{hyphen} \unfakable{less} \unfakable{numbersign} \unfakable{parenleft} \unfakable{parenright} \unfakable{percent} \unfakable{period} \unfakable{perthousandzero} \unfakable{plus} \unfakable{questiondown} \unfakable{question} \unfakable{quotedblbase} \unfakable{quotedblleft} \unfakable{quotedblright} \unfakable{quotedbl} \unfakable{quoteleft} \unfakable{quoteright} \unfakable{section} \unfakable{semicolon} \unfakable{slash} \unfakable{sterling} \unfakable{underscore} \begincomment \subsection{Fakable characters} \endcomment \setglyph{space} \ifisglyph{space-not}\then \movert{\width{space-not}} \Else\ifisglyph{i}\then \movert{\width{i}} \Else \movert{333} \Fi\Fi \endsetglyph \setglyph{compwordmark} \glyphrule{0}{\int{xheight}} \endsetglyph \setint{compwordmark-spacing}{0} \setglyph{quotesinglbase} \glyph{comma}{1000} \endsetglyph \setglyph{visiblespace} \moveup{\neg{\int{visiblespacedepth}}} \movert{\int{visiblespacesurround}} \glyphrule {\int{underlinethickness}} {\int{visiblespacedepth}} \glyphrule {\int{visiblespacewidth}} {\int{underlinethickness}} \glyphrule {\int{underlinethickness}} {\int{visiblespacedepth}} \movert{\int{visiblespacesurround}} \moveup{\int{visiblespacedepth}} \endsetglyph \setleftrightkerning{visiblespace}{space}{1000} \comment{The matter of whether a \texttt{visiblespace} should kern like a \texttt{space} has never been satisfactory resolved.} \begincomment \subsection{Some special dashes} \texttt{rangedash} and \texttt{punctdash} are mostly two traditional aliases for \texttt{endash} and \texttt{emdash}. The problem with the latter two ``original'' glyphs is that they in monowidth fonts usually are much shorter than one would expect, whereas the hyphen combinations look quite good. \endcomment \setglyph{rangedash} \ifisint{monowidth}\then \glyph{hyphen}{1000} \Else \glyph{endash}{1000} \Fi \endsetglyph \setglyph{punctdash} \ifisint{monowidth}\then \glyph{hyphen}{1000} \glyph{hyphen}{1000} \Else \glyph{emdash}{1000} \Fi \endsetglyph \setglyph{hyphenchar} \glyph{hyphen}{1000} \resetwidth{\half{\width{hyphen}}} \comment{Unlike the normal \texttt{hyphen}, this glyph is only meant to be used at the right end of a line of text. This means it can be a ``hanging hyphen'' which significantly extends outside the character box.} \setleftkerning{hyphenchar}{hyphen}{1000} \comment{\TeX\ does consider kerning (and ligatures) between a hyphenchar and what preceeds it on the line, but there is nothing after the hyphenchar.} \endsetglyph \begincomment \subsection{More monowidth specialities} \endcomment % only with monospaced fonts. (WaS) \ifisint{monowidth}\then \resetglyph{asterisk} \moveup{\sub{\int{vaxis}}{\half{\sub{\height{asterisk}}{\depth{asterisk}}}}} \glyph{asterisk}{1000} \resetdepth{0} \endresetglyph \Fi \begincomment \section{Digits} The traditional coding here has been that all digits are considered to be unfakable. An obvious alternative is however to fake \texttt{zerooldstyle} with \texttt{zero}, \texttt{oneoldstyle} with \texttt{one}, etc., or vice versa. \endcomment \unfakable{zero} \unfakable{one} \unfakable{two} \unfakable{three} \unfakable{four} \unfakable{five} \unfakable{six} \unfakable{seven} \unfakable{eight} \unfakable{nine} \unfakable{zerooldstyle} \unfakable{oneoldstyle} \unfakable{twooldstyle} \unfakable{threeoldstyle} \unfakable{fouroldstyle} \unfakable{fiveoldstyle} \unfakable{sixoldstyle} \unfakable{sevenoldstyle} \unfakable{eightoldstyle} \unfakable{nineoldstyle} \endmetrics \section{Changes} The original version of this file was created in February 2003, although it is based on code from the traditional \texttt{latin.mtx}. The changes that have been made after that are as follows. 2003/03/15: The asterisk in monowidth fonts is vertically centered, to make it more useful for computer listings. Suggested by Walter Schmidt. \end{document}