Is this something we want to fix?
/Simon
doc/parse-datetime.texi:459:@cindex beginning of time, for @acronym{POSIX}
doc/parse-datetime.texi:460:@cindex epoch, for @acronym{POSIX}
doc/parse-datetime.texi:462:an epoch---a well-defined point of time. On
@acronym{GNU} and
doc/parse-datetime.texi:463:@acronym{POSIX} systems, the epoch is 1970-01-01
00:00:00 @sc{utc}, so
doc/parse-datetime.texi:465:00:00:01 @sc{utc}, and so forth. @acronym{GNU} and
most other
doc/parse-datetime.texi:466:@acronym{POSIX}-compliant systems support such
times as an extension
doc/parse-datetime.texi:467:to @acronym{POSIX}, using negative counts, so that
@samp{@@-1}
doc/parse-datetime.texi:495:For example, with the @acronym{GNU} @command{date}
command you can
doc/parse-datetime.texi:519:Gateway}. A few n...@acronym{gnu} hosts require a
colon before a
doc/parse-datetime.texi:526:using a n...@acronym{gnu} host that does not
support the @samp{tz}
doc/parse-datetime.texi:527:database, you may need to use a @acronym{POSIX}
rule instead. Simple
doc/parse-datetime.texi:528:@acronym{POSIX} rules like @samp{UTC0} specify a
time zone without
maint.mk: found use of Texinfo @acronym{}
make: *** [sc_texinfo_acronym] Fel 1
