Re: [Groff] Proper Small Caps.
On 8/1/24 19:49, G. Branden Robinson wrote: Nine years seems like long enough to wait to resurrect this thread. At 2015-01-20T19:57:25-0500, Doug McIlroy wrote: > ... I recoil from text infected with capital pox, and don't see small caps as much improvement. They do make sense in all-caps text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. I agree with Branden, especially as there are a number of good quality type1 font families that have a "proper" small caps font. I think that a long time ago groff moved on from being purely a method of typesetting technical documents. Why should we munge small caps from standard fonts (and earn Doug's ire) when there are genuine small caps that we should be using when we need them. Of course, Gaius Mulley's superb dropcaps macro would need revision. :-) Robert Thorsby
Re: [Groff] Proper Small Caps.
Nine years seems like long enough to wait to resurrect this thread. At 2015-01-20T19:57:25-0500, Doug McIlroy wrote: > [Ralph Corderoy wrote:] > > Thought it might be of interest given troff's long-time S\s-2MALL\s0 > > C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis > > Ritchie said they did it because the CAT gave them the possibility, but > > it was regretted for the UNIX/Unix confusion it caused. > > I think this is urban legend. Small caps were not used in UNIX manuals or > in the Bell System Technical Journal articles about UNIX. Fairly early on, > we in the Unix lab began to treat Unix as a proper noun, but the lawyers > had trademarked the uppercase name and got their way in many publications, > including the books by Kernighan and Ritchie and Kernighan and Pike. > U\s-2NIX\s0 was very rare, if it ever happened at all. I have found a 48-year-old instance of it in the wild! Al Kossow just this week uploaded his copy of a printed Sixth Edition manual to Bitsavers. The mixed-case-but-still-small-caps (mis-)usage occurs in only place that I can see, on page 3. This page of the manual was not produced by the CSRC, but by "AT SPCS", and/or "the Unix Operating System Generic, PGC-1C300, Issue 2". So presumably C. D. Perez, who appears to claim responsibility for that version of the document, was not familiar with the typographical conventions of the Unix lab. https://bitsavers.org/pdf/att/unix/6th_Edition/UNIX_Programmers_Manual_197601.pdf > I recoil from text infected with capital pox, and don't see small caps as > much improvement. They do make sense in all-caps text, but sporadic > S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. Regards, Branden signature.asc Description: PGP signature
Re: [Groff] Proper Small Caps.
(Commentary) http://xkcd.com/1167/ -- Mike Bianchi
Re: [Groff] Proper Small Caps.
I am very interested in your opinion on what is best, given the trade off between how many days to keep, how many to do each day (6, I think) and how much space there is on the drive. I wonder whether it would be practical to gradually thin nbackup coverage going back in time, to make older files available without taking up more storage. A natural thing to do would be to coalesce groups of adjacent dumps when they get to a certain age, keeping just one version of each file that changed more than once. I find from poking around that each dump covers somewhat more than 24 hours, so there is a lot of duplication to profit from. I don't know, though, how storage is allocated for dumps. That could make it hard to recycle storage for thinning. And of course thinning would take time, too. Incidentally, the reason I stumbled on the 7-day limit is that I left some untested code changes just before a 10-day vacation, and they were wrong. Questionable practice not to keep a working copy. Will I every learn? Doug
Re: [Groff] Proper Small Caps.
Hi Doug and Eric,
Ralph wrote:
IIRC, Dennis Ritchie said they did it because the CAT gave them
the possibility, but it was regretted for the UNIX/Unix confusion
it caused.
Doug wrote:
I think this is urban legend. Small caps were not used in UNIX
manuals or in the Bell System Technical Journal articles about UNIX.
Fairly early on, we in the Unix lab began to treat Unix as a proper
noun, but the lawyers had trademarked the uppercase name and got
their way in many publications, including the books by Kernighan and
Ritchie and Kernighan and Pike. U\s-2NIX\s0 was very rare, if it
ever happened at all.
Eric wrote:
Thank you for clearing that up. It's a minor point, never worth
bothering you about, but I've been wondering about it for decades.
I've done a little digging, wondering if I could find dmr saying this.
The closest, and probably were I learnt it, is (Eric's) _The Jargon
File_.
http://www.catb.org/jargon/html/U/Unix.html
Some people are confused over whether this word is appropriately
‘UNIX’ or ‘Unix’; both forms are common, and used interchangeably.
Dennis Ritchie says that the ‘UNIX’ spelling originally happened in
CACM's 1974 paper The UNIX Time-Sharing System because “we had a new
typesetter and troff had just been invented and we were intoxicated
by being able to produce small caps.” Later, dmr tried to get the
spelling changed to ‘Unix’ in a couple of Bell Labs papers, on the
grounds that the word is not acronymic. He failed, and eventually
(his words) “wimped out” on the issue.
Eric, perhaps your private data might show the source of those quotes.
I used Debian Code Search, a newish very handy tool to search Debian's
source base now that Google have taken down Russ Cox's Google Code
Search. That turned up definitions for UX and Ux in package 9base.
That's part of Russ Cox's plan9port; Plan 9's commands on Unix.
9base's troff/tmac/tmac.soft has UX as \s-2UNIX\s0 and Ux was
U\s-2NIX\s0, but that's been commented out and replaced by \s-2UNIX\s0.
http://sources.debian.net/src/9base/1:6-6/troff/tmac/tmac.soft/#L607
.de UX
.ie \\n(GA0 \\$2\s-2UNIX\s0\\$1
.el \{\
.if n \\$2UNIX\(dg\\$1
.if t \\$2\s-2UNIX\s0\(dg\\$1
.FS
\(dg \s-2UNIX\s0 is a registered trademark of X/Open.
.FE
.nr GA 1\}
..
.de Ux \ cap-small cap, not used
.\ .ie \\n(GA0 \\$2U\s-2NIX\s0\\$1
.ie \\n(GA0 \\$2\s-2UNIX\s0\\$1
.el \{\
.if n \\$2UNIX*\\$1
.\.if t \\$2U\s-2NIX\s0*\\$1
.if t \\$2\s-2UNIX\s0*\\$1
.FS
* \s-2UNIX\s0 is a registered trademark of X/Open.
.FE
.nr GA 1\}
..
Going to Plan 9, http://www.plan9.bell-labs.com/wiki/plan9/tmac/ says
tmac.soft is macros from mel…, not documented - perhaps for SOFTWARE -
Practice and Experience. tmac.soft at
http://plan9.bell-labs.com/sources/plan9/sys/lib/tmac/tmac.soft also has
U\s-2NIX\s0, but commented out.
Another historical branch, Unix International, an ancestor of X/Open,
formed by ATT and Sun, amongst others, turns up these few strings.
http://sources.debian.net/src/dwarfutils/20120410-2/libdwarf/dwarf.v2.mm/?hl=58#L58
.ds aX U\s-2NIX\s+2
.ds iX \*(aX International
.ds uL \s-2ATT\ USL\s+2
Lastly, 7th Ed. Unix from
http://minnie.tuhs.org/Archive/PDP-11/Distributions/research/Henry_Spencer_v7/v7.tar.gz
gives
$ grep -r 'U\\.*NIX' .
./usr/doc/tbl:``The U\s-2NIX\s0 Time-Sharing System,''
./usr/doc/tbl:Typing Documents on U\s-2NIX\s0,
./usr/doc/tbl:Computer Typesetting of Technical Journals on U\s-2NIX\s0,
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Time-Sharing System: Document
Preparation
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Time-Sharing System: The
Programmer's Workbench
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Time-Sharing System: U\s-2NIX\s0 on
a Microprocessor
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Time-Sharing System: The
U\s-2NIX\s0 Shell
./usr/dict/papers/Rv7man:%T M\s-2UNIX\s0, A Multiprocessing Version of
U\s-2NIX\s0
./usr/dict/papers/Rv7man:%T The U\s-2NIX\s0 Time-Sharing System
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Programmer's Man\ual
./usr/dict/papers/Rv7man:%T The U\s-2NIX\s0 Command Language
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Time-Sharing System: Portability of
C Programs and the U\s-2NIX\s0 System
./usr/dict/papers/Rv7man:%T U\s-2NIX\s0 Programmer's Manual
./usr/dict/papers/Rv7man:%T The Network U\s-2NIX\s0 System
$
tbl is Mike Lesk's paper on his program. Rv7man is refer input for
Unix/v7-related papers. Lesk also wrote refer so probably put together
those references. Perhaps he's the source of U\s-2NIX\s0? (Unless it's
that Eric Schmidt chipping in; whatever happened to him? :-)
Mike wrote -ms too IIRC, but it does \s-2UNIX\s0.
$ sed -n '/^\.de UX/,/^\.\.$/p' usr/lib/tmac/tmac.s
.de UX
.ie \\n(GA0 \\$2\s-2UNIX\s0\\$1
.el \{\
.if n \\$2UNIX\\$1*
.if t
Re: [Groff] Proper Small Caps.
My recollection from Bell Labs (Naperville location in the mid-80's) was that the lawyers hadcome up with some scheme where UNIX had to be all caps plus in a unique font. These werethe days of nroff/mmx and the nascent times of device-independent troff so we used the smallerall-caps UNIX string to meet those criteria. Our style was to make any all-caps string 1-pointsize smaller than the other text just because it looked better so we had to go to \s-2UNIX\s+2. But I don't remember us using the U\s-2NIX\s+2 string. meg From: Eric S. Raymond e...@thyrsus.com To: Doug McIlroy d...@cs.dartmouth.edu Cc: groff@gnu.org Sent: Tuesday, January 20, 2015 5:26 PM Subject: Re: [Groff] Proper Small Caps. Doug McIlroy d...@cs.dartmouth.edu: Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. I think this is urban legend. Small caps were not used in UNIX manuals or in the Bell System Technical Journal articles about UNIX. Fairly early on, we in the Unix lab began to treat Unix as a proper noun, but the lawyers had trademarked the uppercase name and got their way in many publications, including the books by Kernighan and Ritchie and Kernighan and Pike. U\s-2NIX\s0 was very rare, if it ever happened at all. Thank you for clearing that up. It's a minor point, never worth bothering you about, but I've been wondering about it for decades. -- a href=http://www.catb.org/~esr/;Eric S. Raymond/a
Re: [Groff] Proper Small Caps.
Thanks for the amplification, Meg. That convention was used in Kernighan's books, and in a few places (but not everywhere) in the manuals.
Re: [Groff] Proper Small Caps.
Yes, there were a lot of writers working on those documents and some were morerigorous in sticking to the standard than others. There was some editting and wehad typesetters who looked for such things but I know that things slipped through.I was mostly working on the more technical docs -- a lot of the style standards wereset by people whose hearts were in end-user documentation and they voted in stuffthat we didn't care for. We quickly figured out that, if we rigorously adhered to thestandards for the first few pages, the style-enforcers got bored reading our docs andwould leave us alone ;-) From: Doug McIlroy d...@cs.dartmouth.edu To: e...@thyrsus.com; dreidellh...@yahoo.com; d...@cs.dartmouth.edu Cc: groff@gnu.org Sent: Tuesday, January 20, 2015 6:10 PM Subject: Re: [Groff] Proper Small Caps. Thanks for the amplification, Meg. That convention was used in Kernighan's books, and in a few places (but not everywhere) in the manuals.
Re: [Groff] Proper Small Caps.
Doug McIlroy d...@cs.dartmouth.edu: Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. I think this is urban legend. Small caps were not used in UNIX manuals or in the Bell System Technical Journal articles about UNIX. Fairly early on, we in the Unix lab began to treat Unix as a proper noun, but the lawyers had trademarked the uppercase name and got their way in many publications, including the books by Kernighan and Ritchie and Kernighan and Pike. U\s-2NIX\s0 was very rare, if it ever happened at all. Thank you for clearing that up. It's a minor point, never worth bothering you about, but I've been wondering about it for decades. -- a href=http://www.catb.org/~esr/;Eric S. Raymond/a
Re: [Groff] Proper Small Caps.
Steve Izma si...@golden.net wrote: On Tue, Jan 20, 2015 at 07:57:25PM -0500, Doug McIlroy wrote: I recoil from text infected with capital pox, and don't see small caps as much improvement. They do make sense in all-caps text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. I agree with the sentiment; titles, phrases, or quotations (etc.) in all-caps sound like the Emperor inscribing diktats on walls in order to intimidate the plebs. The vast majority of book covers today are in all-caps since subtlety is antithetical to marketing. I rarely have any influence over the covers for the books I typeset, but I swear that when I have the opportunity to design a cover I will never set the title in capitals. The only place I need small caps for my typesetting needs (I handle formatting for a publishing co-op) is on title pages or chapter headings. In those limited cases, I think they look good. I was going to try neatroff, but the compile failed on OS X. I might try Tadziu’s cfftot1 technique next. — Larry
Re: [Groff] Proper Small Caps.
On Tue, Jan 20, 2015 at 07:57:25PM -0500, Doug McIlroy wrote: Subject: Re: [Groff] Proper Small Caps. I recoil from text infected with capital pox, and don't see small caps as much improvement. They do make sense in all-caps text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. I agree with the sentiment; titles, phrases, or quotations (etc.) in all-caps sound like the Emperor inscribing diktats on walls in order to intimidate the plebs. The vast majority of book covers today are in all-caps since subtlety is antithetical to marketing. I rarely have any influence over the covers for the books I typeset, but I swear that when I have the opportunity to design a cover I will never set the title in capitals. Nonetheless, especially in scholarly and political publishing, acronyms are frequently needed. Setting them in small caps lessens their obtrusiveness in the text, I feel. A style that I see in some British publications (e.g., London Review of Books -- maybe it's more commonly accepted) is that if an acronym is pronouceable it's rendered as a proper noun, as Doug mentions about Unix. Large-and-small caps, I think, can work for authors' names or running heads in text sizes smaller than the regular text without seeming to be shouting. -- Steve -- Steve Izma - Home: 35 Locust St., Kitchener N2H 1W6p:519-745-1313 Work: Wilfrid Laurier University Pressp:519-884-0710 ext. 6125 E-mail: si...@golden.net or st...@press.wlu.ca A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [Groff] Proper Small Caps.
When I was working on HP-UX, deriving our content from ATT documents, acronyms and words consisting of uppercase letters were coded by ATT as \s-1HP-UX\s+1, etc. It subdued the overbearing appearance of the uppercase words so they blended better with normal font. I don't recall ever seeing small-cap words anywhere in Unix documents. Clarke On 01/20/2015 05:57 PM, Doug McIlroy wrote: Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. I think this is urban legend. Small caps were not used in UNIX manuals or in the Bell System Technical Journal articles about UNIX. Fairly early on, we in the Unix lab began to treat Unix as a proper noun, but the lawyers had trademarked the uppercase name and got their way in many publications, including the books by Kernighan and Ritchie and Kernighan and Pike. U\s-2NIX\s0 was very rare, if it ever happened at all. I recoil from text infected with capital pox, and don't see small caps as much improvement. They do make sense in all-caps text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. Doug
Re: [Groff] Proper Small Caps.
Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. I think this is urban legend. Small caps were not used in UNIX manuals or in the Bell System Technical Journal articles about UNIX. Fairly early on, we in the Unix lab began to treat Unix as a proper noun, but the lawyers had trademarked the uppercase name and got their way in many publications, including the books by Kernighan and Ritchie and Kernighan and Pike. U\s-2NIX\s0 was very rare, if it ever happened at all. I recoil from text infected with capital pox, and don't see small caps as much improvement. They do make sense in all-caps text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like it is not a cure for the pox. Doug
Re: [Groff] Proper Small Caps.
Which raises the point, does anyone know of a way to extract just the small caps from an OpenType font that has them? Not sure if this is really helpful, but since I have not yet arrived in the OpenType era I use cfftot1 to convert OpenType fonts to Type 1 and then simply use different font encoding vectors to display text either with upper and lower case letters or with caps and small caps. (The conversion preserves the exact letter shapes, but you lose the fancy OpenType code that does all those funky character replacements for you, so you must do that manually.)
Re: [Groff] Proper Small Caps.
Tadziu -- On Mon, Jan 19, 2015, Tadziu Hoffmann wrote: Which raises the point, does anyone know of a way to extract just the small caps from an OpenType font that has them? Not sure if this is really helpful, but since I have not yet arrived in the OpenType era I use cfftot1 to convert OpenType fonts to Type 1 and then simply use different font encoding vectors to display text either with upper and lower case letters or with caps and small caps. (The conversion preserves the exact letter shapes, but you lose the fancy OpenType code that does all those funky character replacements for you, so you must do that manually.) Interesting. Thanks. I'll look into this. -- Peter Schaffter http://www.schaffter.ca
Re: [Groff] Proper Small Caps.
I'm fond of smallcaps, but I don't like the faked version, not even the OpenType smallcaps. Whenever possible, I always advise getting a designer-cut smallcaps font. I don't understand. Aren't the small caps of OpenType fonts that support this feature supposed to be real, designer-cut small caps? Like those in the expert sets of traditional Type-1 fonts, but additionally with matching punctuation etc.?
Re: [Groff] Proper Small Caps.
Tadziu -- On Mon, Jan 19, 2015, Tadziu Hoffmann wrote: I'm fond of smallcaps, but I don't like the faked version, not even the OpenType smallcaps. Whenever possible, I always advise getting a designer-cut smallcaps font. I don't understand. Aren't the small caps of OpenType fonts that support this feature supposed to be real, designer-cut small caps? Like those in the expert sets of traditional Type-1 fonts, but additionally with matching punctuation etc.? I think you are right. My confusion comes from statements like this: InDesign: Small Caps: This command, which can be accessed from the Character panel, will convert only the lowercase in selected text to small caps – either to true-drawn versions that are available with some OpenType fonts, or to fake, scaled-down ones for fonts that don't have the real thing. [fonts.com] This is actually a statement about how InDesign handles small caps, not a statement about OpenType small caps management. A tad misleading. Thanks for pointing out my error. Which raises the point, does anyone know of a way to extract just the small caps from an OpenType font that has them? -- Peter Schaffter http://www.schaffter.ca
Re: [Groff] Proper Small Caps.
Ralph Corderoy ra...@inputplus.co.uk wrote: http://2d.laboratorium.net/post/108351875900/small-caps-big-problem complains about small caps from Word, etc., compared with small caps designed by the designer. Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. Heirloom troff, http://heirloom.sourceforge.net/doctools.html, says Mechanisms for typesetting small capitals, old-style numerals, and arbitrary ligatures e.g. using Type 1 “expert” or OpenType fonts are provided. Don't know what the other various troff's support for proper small caps is, e.g. plucking them from the OpenType font? For OpenType fonts that define such a feature (usually called smcp), in neatroff (as in Heirloom troff) it can be enabled as follows: .fp 1 R LinLibertineO \ LinuxLibertine has smcp .ff R +smcp \ equivalent to Heirloom's .ffeat Text in small caps. The attached sample uses LinLibertine. Ali smcp.pdf Description: Adobe PDF document
[Groff] Proper Small Caps.
Hi, http://2d.laboratorium.net/post/108351875900/small-caps-big-problem complains about small caps from Word, etc., compared with small caps designed by the designer. Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. Heirloom troff, http://heirloom.sourceforge.net/doctools.html, says Mechanisms for typesetting small capitals, old-style numerals, and arbitrary ligatures e.g. using Type 1 “expert” or OpenType fonts are provided. Don't know what the other various troff's support for proper small caps is, e.g. plucking them from the OpenType font? Cheers, Ralph.
Re: [Groff] Proper Small Caps.
On 18-Jan-2015 11:15:05 Ralph Corderoy wrote: Hi, http://2d.laboratorium.net/post/108351875900/small-caps-big-problem complains about small caps from Word, etc., compared with small caps designed by the designer. Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. Heirloom troff, http://heirloom.sourceforge.net/doctools.html, says Mechanisms for typesetting small capitals, old-style numerals, and arbitrary ligatures e.g. using Type 1 âexpertâ or OpenType fonts are provided. Don't know what the other various troff's support for proper small caps is, e.g. plucking them from the OpenType font? Cheers, Ralph. For what it's worth, here's what I do (with example usage at end): .\## .de smallcaps .nr .sc.ps (\\n[.s]*80/100) .nr .cap.PS \\n[.s] .nr .scsh (\\n[.ps]/100) .char a\s[\\n[.sc.ps]]\Z'A'\h'\\n[.scsh]s'A\s[\\n[.cap.PS]] .char b\s[\\n[.sc.ps]]\Z'B'\h'\\n[.scsh]s'B\s[\\n[.cap.PS]] .char c\s[\\n[.sc.ps]]\Z'C'\h'\\n[.scsh]s'C\s[\\n[.cap.PS]] .char d\s[\\n[.sc.ps]]\Z'D'\h'\\n[.scsh]s'D\s[\\n[.cap.PS]] .char e\s[\\n[.sc.ps]]\Z'E'\h'\\n[.scsh]s'E\s[\\n[.cap.PS]] .char f\s[\\n[.sc.ps]]\Z'F'\h'\\n[.scsh]s'F\s[\\n[.cap.PS]] .char g\s[\\n[.sc.ps]]\Z'G'\h'\\n[.scsh]s'G\s[\\n[.cap.PS]] .char h\s[\\n[.sc.ps]]\Z'H'\h'\\n[.scsh]s'H\s[\\n[.cap.PS]] .char i\s[\\n[.sc.ps]]\Z'I'\h'\\n[.scsh]s'I\s[\\n[.cap.PS]] .char j\s[\\n[.sc.ps]]\Z'J'\h'\\n[.scsh]s'J\s[\\n[.cap.PS]] .char k\s[\\n[.sc.ps]]\Z'K'\h'\\n[.scsh]s'K\s[\\n[.cap.PS]] .char l\s[\\n[.sc.ps]]\Z'L'\h'\\n[.scsh]s'L\s[\\n[.cap.PS]] .char m\s[\\n[.sc.ps]]\Z'M'\h'\\n[.scsh]s'M\s[\\n[.cap.PS]] .char n\s[\\n[.sc.ps]]\Z'N'\h'\\n[.scsh]s'N\s[\\n[.cap.PS]] .char o\s[\\n[.sc.ps]]\Z'O'\h'\\n[.scsh]s'O\s[\\n[.cap.PS]] .char p\s[\\n[.sc.ps]]\Z'P'\h'\\n[.scsh]s'P\s[\\n[.cap.PS]] .char q\s[\\n[.sc.ps]]\Z'Q'\h'\\n[.scsh]s'Q\s[\\n[.cap.PS]] .char r\s[\\n[.sc.ps]]\Z'R'\h'\\n[.scsh]s'R\s[\\n[.cap.PS]] .char s\s[\\n[.sc.ps]]\Z'S'\h'\\n[.scsh]s'S\s[\\n[.cap.PS]] .char t\s[\\n[.sc.ps]]\Z'T'\h'\\n[.scsh]s'T\s[\\n[.cap.PS]] .char u\s[\\n[.sc.ps]]\Z'U'\h'\\n[.scsh]s'U\s[\\n[.cap.PS]] .char v\s[\\n[.sc.ps]]\Z'V'\h'\\n[.scsh]s'V\s[\\n[.cap.PS]] .char w\s[\\n[.sc.ps]]\Z'W'\h'\\n[.scsh]s'W\s[\\n[.cap.PS]] .char x\s[\\n[.sc.ps]]\Z'X'\h'\\n[.scsh]s'X\s[\\n[.cap.PS]] .char y\s[\\n[.sc.ps]]\Z'Y'\h'\\n[.scsh]s'Y\s[\\n[.cap.PS]] .char z\s[\\n[.sc.ps]]\Z'Z'\h'\\n[.scsh]s'Z\s[\\n[.cap.PS]] .char \(i. \s[\\n[.sc.ps]]\Z'I'\h'\\n[.scsh]s'I\s[\\n[.cap.PS]] .. .de /smallcaps .\\c .rchar a b c d e f g h i j k l m n o p q r s t u v w x y z \(i. .rr .sc.ps .rr .cap.PS .rr .scsh .. .smallcaps Here Is An Example Of Smallcaps ./smallcaps .\## Note the over-printing to slightly fatten the reduced-size capitals. NB That this is oriented towards PS output! Best wishes to all, Ted. - E-Mail: (Ted Harding) ted.hard...@wlandres.net Date: 18-Jan-2015 Time: 12:22:07 This message was sent by XFMail -
Re: [Groff] Proper Small Caps.
Rather than shrinking, squash the fake small caps, eg: S\H'\n[.s]*5/7'MALL\H'0' C\H'\n[.s]*5/7'APS\H'0' (the 5/7 should approximate to the x-height of the font). This works better because more of the heavy strokes in a western font are upright, and this keeps the weight of those. As Matthew Butterick says If you want real small caps, you'll have to buy them I have such a set, but the newer version contains OpenType faces and I haven't had time to work out how to use these with groff. The small cap glyphs are named something like A_sc -- tricky. I have a macro analogous to the .B, .BI macros of man pages: .SC ..., but it works differently to Ted's ingenious solution, involving .substr. Denis On Sun, 18 Jan 2015 12:22:10 - (GMT) (Ted Harding) ted.hard...@wlandres.net wrote: On 18-Jan-2015 11:15:05 Ralph Corderoy wrote: Hi, http://2d.laboratorium.net/post/108351875900/small-caps-big-problem complains about small caps from Word, etc., compared with small caps designed by the designer. Thought it might be of interest given troff's long-time S\s-2MALL\s0 C\s-2APS\s0, especially used in the formatting of Unix. IIRC, Dennis Ritchie said they did it because the CAT gave them the possibility, but it was regretted for the UNIX/Unix confusion it caused. Heirloom troff, http://heirloom.sourceforge.net/doctools.html, says Mechanisms for typesetting small capitals, old-style numerals, and arbitrary ligatures e.g. using Type 1 ___expert__ or OpenType fonts are provided. Don't know what the other various troff's support for proper small caps is, e.g. plucking them from the OpenType font? Cheers, Ralph. For what it's worth, here's what I do (with example usage at end): .\## .de smallcaps .nr .sc.ps (\\n[.s]*80/100) .nr .cap.PS \\n[.s] .nr .scsh (\\n[.ps]/100) .char a\s[\\n[.sc.ps]]\Z'A'\h'\\n[.scsh]s'A\s[\\n[.cap.PS]] .char b\s[\\n[.sc.ps]]\Z'B'\h'\\n[.scsh]s'B\s[\\n[.cap.PS]] .char c\s[\\n[.sc.ps]]\Z'C'\h'\\n[.scsh]s'C\s[\\n[.cap.PS]] .char d\s[\\n[.sc.ps]]\Z'D'\h'\\n[.scsh]s'D\s[\\n[.cap.PS]] .char e\s[\\n[.sc.ps]]\Z'E'\h'\\n[.scsh]s'E\s[\\n[.cap.PS]] .char f\s[\\n[.sc.ps]]\Z'F'\h'\\n[.scsh]s'F\s[\\n[.cap.PS]] .char g\s[\\n[.sc.ps]]\Z'G'\h'\\n[.scsh]s'G\s[\\n[.cap.PS]] .char h\s[\\n[.sc.ps]]\Z'H'\h'\\n[.scsh]s'H\s[\\n[.cap.PS]] .char i\s[\\n[.sc.ps]]\Z'I'\h'\\n[.scsh]s'I\s[\\n[.cap.PS]] .char j\s[\\n[.sc.ps]]\Z'J'\h'\\n[.scsh]s'J\s[\\n[.cap.PS]] .char k\s[\\n[.sc.ps]]\Z'K'\h'\\n[.scsh]s'K\s[\\n[.cap.PS]] .char l\s[\\n[.sc.ps]]\Z'L'\h'\\n[.scsh]s'L\s[\\n[.cap.PS]] .char m\s[\\n[.sc.ps]]\Z'M'\h'\\n[.scsh]s'M\s[\\n[.cap.PS]] .char n\s[\\n[.sc.ps]]\Z'N'\h'\\n[.scsh]s'N\s[\\n[.cap.PS]] .char o\s[\\n[.sc.ps]]\Z'O'\h'\\n[.scsh]s'O\s[\\n[.cap.PS]] .char p\s[\\n[.sc.ps]]\Z'P'\h'\\n[.scsh]s'P\s[\\n[.cap.PS]] .char q\s[\\n[.sc.ps]]\Z'Q'\h'\\n[.scsh]s'Q\s[\\n[.cap.PS]] .char r\s[\\n[.sc.ps]]\Z'R'\h'\\n[.scsh]s'R\s[\\n[.cap.PS]] .char s\s[\\n[.sc.ps]]\Z'S'\h'\\n[.scsh]s'S\s[\\n[.cap.PS]] .char t\s[\\n[.sc.ps]]\Z'T'\h'\\n[.scsh]s'T\s[\\n[.cap.PS]] .char u\s[\\n[.sc.ps]]\Z'U'\h'\\n[.scsh]s'U\s[\\n[.cap.PS]] .char v\s[\\n[.sc.ps]]\Z'V'\h'\\n[.scsh]s'V\s[\\n[.cap.PS]] .char w\s[\\n[.sc.ps]]\Z'W'\h'\\n[.scsh]s'W\s[\\n[.cap.PS]] .char x\s[\\n[.sc.ps]]\Z'X'\h'\\n[.scsh]s'X\s[\\n[.cap.PS]] .char y\s[\\n[.sc.ps]]\Z'Y'\h'\\n[.scsh]s'Y\s[\\n[.cap.PS]] .char z\s[\\n[.sc.ps]]\Z'Z'\h'\\n[.scsh]s'Z\s[\\n[.cap.PS]] .char \(i. \s[\\n[.sc.ps]]\Z'I'\h'\\n[.scsh]s'I\s[\\n[.cap.PS]] .. .de /smallcaps .\\c .rchar a b c d e f g h i j k l m n o p q r s t u v w x y z \(i. .rr .sc.ps .rr .cap.PS .rr .scsh .. .smallcaps Here Is An Example Of Smallcaps ./smallcaps .\## Note the over-printing to slightly fatten the reduced-size capitals. NB That this is oriented towards PS output! Best wishes to all, Ted. - E-Mail: (Ted Harding) ted.hard...@wlandres.net Date: 18-Jan-2015 Time: 12:22:07 This message was sent by XFMail - --
Re: [Groff] Proper Small Caps.
On Sun, Jan 18, 2015, Ralph Corderoy wrote: Hi, http://2d.laboratorium.net/post/108351875900/small-caps-big-problem complains about small caps from Word, etc., compared with small caps designed by the designer. I'm fond of smallcaps, but I don't like the faked version, not even the OpenType smallcaps. Whenever possible, I always advise getting a designer-cut smallcaps font. That said, and against my better judgment, I'm adding .SMALLCAPS to mom in the next release (within a couple of weeks). It's similar to Ted's macro, but allows for changing the size of smallcaps (as a user-settable percentage of the current point size) as well as their weight (by fattening them a user-settable percentage of their point size). -- Peter Schaffter http://www.schaffter.ca
