Bug 9231 - Problems with /usr/lib/units.lib
Summary: Problems with /usr/lib/units.lib
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: units   
(Show other bugs)
Version: 5.2
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL: lnx72@ncep.noaa.gov
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-02-08 17:03 UTC by Bert B. Katz
Modified: 2014-03-17 02:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-08 17:07:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Bert B. Katz 2000-02-08 17:03:16 UTC
Some misspellings I detected in /usr/lib/units.lib:

   (1) The prefix "zepto-" was misspelled as "zopto-"
on lines 34 and 56.

   (2) "netherlandsguilder" was misspelled as
"netherlandguilder" on line 264.

   (3) "southafricarand" was misspelled as
"southamericarand" on line 275.

   (4) "perunewsol" was misspelled as "perusol" on
line 292.

   (5) The definition of Boltzmann's Constant "k"
on line 541 should be 1.38047e-16 erg/K instead of
1.38047e-16 erg/degC.  At this point, "degC" has
not yet been defined, but "K" has been.

   (6) The definition of "bohrradius" on line 566
should be 1|8.988e9 hbar2-C2/N-m2-e2-electronmass.
This is similar to the given definition, but follows
the conventions for the units.lib file more closely.
In particular, one of the "bugs" in the man page for
"units" states:

   The user must use | to indicate division of
numbers and / to indicate division of symbols.

   A file with all these corrections is in
lnx72@ncep.noaa.gov:/disk1/bbkatz/units.lib .

Comment 1 Bill Nottingham 2000-02-08 17:07:59 UTC
I believe all of these are fixed in the currently shipping units
package.


Note You need to log in before you can comment on or make changes to this bug.