Thanks, David,
We abandoned the charent.cf file a long time ago because it was not
foolproof. I do not know if it has since been fixed, but there was a time
when Arbortext could not guarantee that the charent.cf file would "fire"
only at the end of the content pipeline just before applying the print
stylesheet ... when it fired prematurely, the character mapping did not
necessarily survive subsequent parsings resulting in unpredictable final
output.
I'll keep this option in mind though ... if nothing else works (and we
can't convince our authors to accept similar but not identical glyphs), I
may have to give that another try.
On Tue, Jul 31, 2012 at 6:17 AM, Taylor, David S. <
david.s.taylor@nrc-cnrc.gc.ca> wrote:
> What has worked for me is using a charent.cf file in the custom/lib
> directory. The file only needs to contain the characters you want to
> re-map, as follows:****
>
> ** **
>
>
> #*******************************************************************************************
> ****
>
> #Description: This file contains character mappings for specific
> character entities ****
>
> # that don't have glyphs in the regular Codes fonts. See
> the main****
>
> # charent.cf file in the 'lib' directory of the
> Arbortext Editor****
>
> # installation tree for an explanation of how this file
> works****
>
> #****
>
>
> #*******************************************************************************************
> ****
>
> accents: # ENTITIES IN THIS SECTION ARE OF TYPE "accent"****
>
> ** **
>
> windowsonly:****
>
> ** **
>
> macr - - unicode 0x2C9 =****
>
> ** **
>
> endwindowsonly:****
>
> ** **
>
> ** **
>
> chars: # THE REMAINDER OF THE ENTITIES IN THE FILE ARE OF TYPE "char"**
> **
>
> ** **
>
> puncsp - - unicode 0x2008 current "\hmode\kern.2em|"***
> *
>
> ** **
>
> windowsonly:****
>
> ** **
>
> check "Arial Unicode MS" 0x2713 unicode 0x2713 "Arial Unicode
> MS" 0x2713****
>
> ** **
>
> endwindowsonly:****
>
> ** **
>
> #****
>
> ** **
>
> I don't need to put any special character handling in the FOSI. ****
>
> ** **
>
> Would this perhaps work for you?****
>
> ** **
>
> David****
>
> ** **
>
> *David S. Taylor*
>
>
> *Project Manager, *Production and Marketing
> Codes and Evaluations | *NRC Construction Portfolio*
> National Research Council Canada
> Building M-23A, Room 239 | 1200 Montreal Road | Ottawa, ON | K1A 0R6****
>
> Telephone: +1.613.990.2731 | Fax: +1.613.952.4040
> David.S.Taylor@nrc-cnrc.gc.ca****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Paul Nagai [
> problem in my FOSI. I am currently trying to replace two characters I
> previously pulled from a Za...
> <charsubset charsubsetref="zapf">
> <usetext source="\&x10132;\" placemnt="before">
> <subchars ...
