🚀 go-pugleaf

I recently asked here:

> When I do a Print Merge in Word 4, it complains if it finds unmatched
> merge quotes (the option-backslash and shift-option-backslash characters).
> Reasonable enough, but what do I do if I want to use those characters as
> characters, rather than as merge command delimiters?

I received a reply from someone at Microsoft, saying it isnt possible
(but that a future version of Word may let you specify which characters
to use as merge quotes).  Ah well.

One work-around is to find another font with the glyphs you want, but
associated with different character codes.  The ones I want are set-union
and set-intersection, which the Symbol font has as the merge-quotes, hence
my problem.  But I have another mathematical font with much the same glyphs
at different character codes.

If you want the actual << and >> glyphs, these are the merge-quote characters
of all the fonts which have them that I looked at.  But you can fake them
with:

        <\D\BA1()<
or
        <\D\BA2()<

Here '<' is not the less-than character, but shift-option-3, which is
present in all the alphabetic PostScript fonts I looked at (but is missing
from all the standard bitmap-only fonts, including New York, Geneva, and
Monaco) and prints almost identically to half a merge quote.  '\' is the
command-option-backslash formula character.

Alternatively, two shift-option-3 characters, the first with Compressed
1.75 character style.  Strangely, whether or not I use Fractional Widths,
this prints identically to <\D\BA1()<, even though it should surely be
0.75pt narrower.

Use shift-option-4 to fake the close merge quote.

--
Richard Kennaway          SYS, University of East Anglia, Norwich, U.K.
Internet:  jrk@sys.uea.ac.uk            uucp:  ...mcvax!ukc!uea-sys!jrk