svn commit: r359504 - head/lib/libc/locale

[Rodney W. Grimes]

> Author: 0mp (doc,ports committer)
> Date: Wed Apr  1 09:01:35 2020
> New Revision: 359504
> URL: https://svnweb.freebsd.org/changeset/base/359504
> 
> Log:
>   Use proper mdoc(7) macros for literal text and do not use Tn
>   
>   Tn is deprecated and upsets linters.
>   

I know I am way late to the game on this, but those of us who have
actually produced phototype output using groff of the man pages in
the past value the .Tn macro.  I can not phantom what would
of been so hard to implement that this had to be depricated by mdoc
simply render the argument as standard characters as groff did in
the past when the output device was of type ascii.

>   MFC after:	3 days
> 
> Modified:
>   head/lib/libc/locale/big5.5
> 
> Modified: head/lib/libc/locale/big5.5
> ==============================================================================
> --- head/lib/libc/locale/big5.5	Wed Apr  1 07:28:31 2020	(r359503)
> +++ head/lib/libc/locale/big5.5	Wed Apr  1 09:01:35 2020	(r359504)
> @@ -24,7 +24,7 @@
>  .\"
>  .\" $FreeBSD$
>  .\"
> -.Dd September 12, 2019
> +.Dd April 1, 2020
>  .Dt BIG5 5
>  .Os
>  .Sh NAME
> @@ -39,9 +39,8 @@ encoding for Traditional Chinese text
>  .Dq Big Five
>  is a standard for encoding Traditional Chinese text.
>  Each character is represented by either one or two bytes.
> -Characters from the
> -.Tn ASCII
> -character set are represented as single bytes in the range 0x00 - 0x7F.
> +Characters from the ASCII character set are represented as
> +single bytes in the range 0x00 - 0x7F.
>  Traditional Chinese characters are represented by two bytes:
>  the first in the range 0xA1 - 0xFE, the second in the range
>  0x40 - 0xFE.
> @@ -51,7 +50,11 @@ the first in the range 0xA1 - 0xFE, the second in the 
>  .Xr utf8 5
>  .Sh BUGS
>  The range of the second byte overlaps some ASCII characters, including
> -0x5C (`\\') and 0x7C (`|') which may cause problems in program execution or
> +0x5C
> +.Pq Ql \e
> +and 0x7C
> +.Pq Ql |
> +which may cause problems in program execution or
>  display.
>  Big5 is considered a legacy standard and only preserved for backward
>  compatibility reason.
> 

-- 
Rod Grimes                                                 rgrimes at freebsd.org