Lines Matching full:groff
74 # understood by groff's preconv. Encode doesn't care about hyphens or
79 # groff preconv prefers iso-8859-1, but also understands iso-latin-1, so
162 return $encoding ne 'roff' && $encoding ne 'groff';
217 $$self{ENCODING} = 'groff';
222 . ' falling back to groff escapes');
224 $$self{ENCODING} = 'groff';
487 # Except in <Data> blocks, if groff or roff encoding is requested and
493 if ($$self{ENCODING} eq 'groff') {
669 # Solaris 2.6 nroff (not present in GNU groff) where the sequence
682 # groff works; \fBfoo\f(CWbar still prints bar in bold. Therefore, we force
1060 # groff's preconv script will use this line to correctly determine the
1576 .\" Escape single quotes in literal strings from groff's Unicode transform.
1585 .\" Avoid warning from groff about undefined register 'F'.
1715 work with the B<man> program on systems that use B<groff> (most Linux
1758 values C<roff> or C<groff>. The default on non-EBCDIC systems is UTF-8.
1765 If the C<encoding> option is set to the special value C<groff> (the default on
1769 of the *roff language, but are supported by B<groff> and B<mandoc> and thus by
1782 to anything other than C<groff> or C<roff> will be ignored and no encoding
1875 [5.00] Add commands telling B<groff> that the input file is in the given
1877 B<groff> provides supplemental configuration, such as C<ja> (for Japanese) or
1886 specified language. Without these commands, groff may not know how to add
1894 Unfortunately, the commands added with this option are specific to B<groff>
2060 should work correctly on any modern system that uses either B<groff> (most
2072 marginally nicer results on older UNIX versions that do not use B<groff> or
2095 The modern implementations, B<groff> (used in most Linux distributions) and
2119 many Unicode characters have no standard troff name. B<groff> has the largest
2120 list, but if one is willing to assume B<groff> is the formatter, the next
2125 Convert characters to groff C<\[uNNNN]> escapes. This is implemented as the
2126 C<groff> encoding for those who want to use it, and is supported by both
2127 B<groff> and B<mandoc>. However, it is no better than UTF-8 output for
2149 Here is the results of testing C<encoding> values of C<utf-8> and C<groff> on
2151 in the current directory, copy F<encoding.utf8> or F<encoding.groff> from the
2163 OS UTF-8 groff
2190 Unicode characters were shown as the body of the groff escape rather than the
2197 Solaris 10. Using C<groff -k -man -Tutf8> to format the page produced the
2202 PostScript and PDF output using groff on a Debian 12 system do not support
2244 C<groff> without complaining to standard error. This environment variable is
2320 most B<troff> implementations, but groff does as an extension. It would be