Change 13984 by jhi@alpha on 2001/12/31 16:19:13

        Slight comment tweakage.

Affected files ...

.... //depot/perl/ext/I18N/Langinfo/Langinfo.t#13 edit

Differences ...

==== //depot/perl/ext/I18N/Langinfo/Langinfo.t#13 (text) ====
Index: perl/ext/I18N/Langinfo/Langinfo.t
--- perl/ext/I18N/Langinfo/Langinfo.t.~1~       Mon Dec 31 09:30:05 2001
+++ perl/ext/I18N/Langinfo/Langinfo.t   Mon Dec 31 09:30:05 2001
@@ -20,17 +20,20 @@
 print "1..1\n"; # We loaded okay.  That's about all we can hope for.
 print "ok 1\n";
 exit(0);
+
 # Background: the langinfo() (in C known as nl_langinfo()) interface
-# is supposed a to be a portable way to fetch various language dependent
-# constants like "the first day of the week" or "the decimal separator".
-# Give a portable (numeric) constant, get back a language-specific string.
-# That's a comforting fantasy.  Now tune in for blunt reality:
-# vendors seem to have implemented for those constants whatever they
-# felt like defining.  The UNIX standard says that one should have
-# the RADIXCHAR constant for the decimal separator.  Not so for many
-# Linux and BSD implementations.  One should have the CODESET constant
-# for returning the current codeset (say, ISO 8859-1).  Not so.
-# --jhi
+# is supposed to be a portable way to fetch various language/country
+# (locale) dependent constants like "the first day of the week" or
+# "the decimal separator".  Give a portable (numeric) constant,
+# get back a language-specific string.  That's a comforting fantasy.
+# Now tune in for blunt reality: vendors seem to have implemented for
+# those constants whatever they felt like implementing.  The UNIX
+# standard says that one should have the RADIXCHAR constant for the
+# decimal separator.  Not so for many Linux and BSD implementations.
+# One should have the CODESET constant for returning the current
+# codeset (say, ISO 8859-1).  Not so.  So let's give up any real
+# testing (leave the old testing code here for old times' sake,
+# though.) --jhi
 
 my %want =
     (
End of Patch.

Reply via email to