Follow-up Comment #4, bug #61371 (project groff):

diff -dpru --unidirectional-new-file groff/src/preproc/tbl/tbl.1.man
new-groff/src/preproc/tbl/tbl.1.man
--- groff/src/preproc/tbl/tbl.1.man     2021-10-31 00:03:10.000000000 +0000
+++ new-groff/src/preproc/tbl/tbl.1.man 2021-10-31 00:10:16.000000000 +0000
@@ -157,7 +157,7 @@ Each cell in a column is classified by b
 centered,
 left-aligned,
 numeric
-(aligned to a decimal point),
+(aligned to a decimal separator),
 and so on.
 .
 This specification can have several lines,
@@ -214,7 +214,7 @@ extension).
 .
 .TP
 .BI decimalpoint( c )
-Set the character to be recognized as the decimal point in numeric
+Set the character to be recognized as the decimal separator in numeric
 columns
 (GNU
 .I tbl \" exception
@@ -417,10 +417,11 @@ Numerically justify item in the column;
 that is,
 align columns of numbers vertically at the units place.
 .
-If there are one or more dots adjacent to a digit,
+If there are one or more decimal separators adjacent to a digit,
 use the rightmost one for vertical alignment.
 .
-If there is no dot, use the rightmost digit for vertical alignment;
+If there is no decimal separator,
+use the rightmost digit for vertical alignment;
 otherwise, center the item within the column.
 .
 Alignment can be forced to a certain position using \[oq]\[rs]&\[cq];
@@ -1141,16 +1142,16 @@ sees the input earlier than
 .IR \%@g@troff .
 .
 For example,
-number formatting with vertically aligned decimal points fails if those
-numbers are passed on as macro parameters because decimal point
-alignment is handled by
+number formatting with vertically aligned decimal separators fails
+if those numbers are passed on as macro parameters
+because decimal separator alignment is handled by
 .I \%@g@tbl
 itself:
 it only sees
 .BR \[rs]$1 ,
 .BR \[rs]$2 ,
 etc.,
-and therefore can't recognize the decimal point.
+and therefore can't recognize the decimal separator.
 .
 .
 .\" ====================================================================


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61371>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/


Reply via email to