Article View: comp.lang.postscript
Article #3591Re: concat strings
From: Woody Baker Eagle Signal
Date: Thu, 08 Nov 1990 00:42
Date: Thu, 08 Nov 1990 00:42
23 lines
1440 bytes
1440 bytes
In article <F2s7R1w163w@phoenix.com>, stanley@phoenix.com (John Stanley) writes: > > glenn@heaven.woodside.ca.us (Glenn Reid) writes: > > In article <DAVIS.90Oct31164243@pacific.mps.ohio-state.edu> davis@pacific.mps > Is the font information stored with a string, or does the font No it is not carried with the strings. > > follow will produce the one resultant string in one font. In other words, > you could NOT concatenate two strings of two different fonts to produce > one string of two fonts. This is correct. You would have to create a partial path in 1 font, and append it to a partial path in the second font. A somewhat simpler way, is to create a procedure that takes a string, and looks for some escape sequence in the string. If it is found, then isolate a command code, and execute a procedure to change the fonts. This is the way most printer emulators written in postscript would work. It is a bit slower, but allows you to mix fonts freely. Cheers Woody
Technical Details
Message-ID:
<1679@chinacat.Unicom.COM>Path:
arc1-ca.pugleaf.net!utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!chinacat!woodyReferences:
<312@heaven.woodside.ca.us> <F2s7R1w163w@phoenix.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!chinacat!woody From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal) Newsgroups: comp.lang.postscript Subject: Re: concat strings Message-ID: <1679@chinacat.Unicom.COM> Date: 8 Nov 90 00:42:38 GMT References: <312@heaven.woodside.ca.us> <F2s7R1w163w@phoenix.com> Organization: a guest of Unicom Systems Development, Austin Lines: 23