From @eb@meyer @end|ng |rom |@u@de  Thu Oct 10 22:04:47 2024
From: @eb@meyer @end|ng |rom |@u@de (Sebastian Meyer)
Date: Thu, 10 Oct 2024 22:04:47 +0200
Subject: [Rd] Typo in DateTimeClasses.Rd
In-Reply-To: <f4eddfe6-0d5d-42f4-bb3c-23e71492faba@sapo.pt>
References: <f4eddfe6-0d5d-42f4-bb3c-23e71492faba@sapo.pt>
Message-ID: <4c909c1a-c520-40c0-8be0-c7429517c8b9@fau.de>

Thanks, fixed in the trunk.

	Sebastian Meyer


Am 10.10.24 um 21:53 schrieb Rui Barradas:
> Hello,
> 
> When following a thread that started today [1], I read the documentation
> for DateTimeClasses {base} more carefully and noticed a typo in the
> "Details on POSIXlt" section, in the paragraph right after the
> components list.
> 
> The original and corrected are "he" instead of "the".
> 
> 
>   From earlier versions of R, he last two components will not be present
> for times in UTC and are platform-dependent.
> 
>   From earlier versions of R, the last two components will not be present
> for times in UTC and are platform-dependent.
> 
> 
> 
> 
> --- datetimeclasses.rd	2024-03-26 23:02:03.000000000 +0000
> +++ datetimeclasses_2.rd	2024-10-10 20:39:16.496162900 +0100
> @@ -198,7 +198,7 @@
>      }
>      The components must be in this order: that was only minimally checked
>      prior to \R 4.3.0.  All objects created in \R 4.3.0 have the optional
> -  components.  From earlier versions of \R, he last two components will
> +  components.  From earlier versions of \R, the last two components will
>      not be present for times in UTC and are platform-dependent.  Currently
>      \code{gmtoff} is set on almost all current platforms: those based on
>      BSD or \code{glibc} (including Linux and macOS) and those using the
> 
> 
> Hope this helps,
> 
> Rui Barradas
> 
>



[Rd] Typo in DateTimeClasses.Rd
Sebastian Meyer