Re: [Groff] Scope of .char, .fchar, .schar?

[Dorai Sitaram]

Found a solution! In the sourced file, instead of
.char ∖ \[u005C]
use
.char \[u2216] \[u005C]
--d 

     On Monday, March 2, 2015 2:56 PM, "address@hidden" <address@hidden> wrote:
   
 

 Dorai Sitaram <address@hidden> wrote:

> I had the following 
> .char ? \[u005C]
> in a file (the first ? is U+2216, or set-minus) and used set-minus within
> the same file, and it works fine.
> However, when I place the .char call in a different file, and source it via
> .so or .mso, occurrences of set-minus in the sourcing file don't translate.
> This happenis only when the first argument of .char is non-ascii Unicode. 
> Is this expected behavior?
> Thanks,--d

If you put preconv after soelim it should not matter if the file is included or 
not:

soelim files ... | preconv | troff ...