Home
last modified time | relevance | path

Searched hist:"72 f211f7" (Results 1 – 17 of 17) sorted by relevance

/openbsd/usr.bin/mandoc/
H A Dmain.h72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dterm_ps.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dterm_ascii.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dchars.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dlibmandoc.h72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dterm.h72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dhtml.h72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dcgi.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dhtml.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dterm.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dread.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dman_term.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dmandocdb.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dmandoc.h72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dmdoc_term.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Droff.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
H A Dmain.c72f211f7 Tue Oct 28 17:35:42 GMT 2014 schwarze <schwarze@openbsd.org> Make the character table available to libroff so it can check the
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.