You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the following piece of code, the BibEntry function assumes the Date field of a package info record is in the "dd/mm/yyyy"-format (or dd@mm@yyyy with any choice of separator @ really).
However, I think the current recommendation is for dates to be in the "yyyy-mm-dd" format. This causes trouble for GitHubPagesForGAP, which relies on BibEntry to get its information for citing a package - see e.g. the GitHub page for the Example package, which has:
[NGK20]
Nickel, W., Gamble, G. and Konovalov, O.,
Example,
Example/Template of a GAP Package,
Version 4.4.0 (1-20) (GAP package),
https://gap-packages.github.io/example.
Here, the citekey should be NGK24 and the year should be 2024, of course. The mistakes stem from BibEntry assuming that the last 4 characters of the string 2024-11-20 represent the year. By contrast, in the same function, the date of GAP itself is assumed to be in the "yyyy-mm-dd"-format:
What may complicate things, is that when GAP reads package metadata on startup, it seems to automatically convert dates to "dd/mm/year"-format before storing it in GAPInfo.PackagesInfo, whereas no such conversion happens when calling GAPInfo.PackageInfoCurrent. If I am working in Example's base directory:
[...]/example$ echo "Print(GAPInfo.PackagesInfo.example[1].Date,\"\n\");QuitGap();" | gap -A -q
20/11/2024
[...]/example$ echo "Read(\"PackageInfo.g\");Print(GAPInfo.PackageInfoCurrent.Date,\"\n\");QuitGap();" | gap -A -q
2024-11-20
The text was updated successfully, but these errors were encountered:
In the following piece of code, the
BibEntry
function assumes theDate
field of a package info record is in the "dd/mm/yyyy"-format (or dd@mm@yyyy with any choice of separator @ really).gap/lib/package.gi
Lines 2936 to 2948 in 0d29d4b
However, I think the current recommendation is for dates to be in the "yyyy-mm-dd" format. This causes trouble for GitHubPagesForGAP, which relies on
BibEntry
to get its information for citing a package - see e.g. the GitHub page for theExample
package, which has:Here, the citekey should be
NGK24
and the year should be2024
, of course. The mistakes stem from BibEntry assuming that the last 4 characters of the string2024-11-20
represent the year. By contrast, in the same function, the date ofGAP
itself is assumed to be in the "yyyy-mm-dd"-format:gap/lib/package.gi
Lines 2880 to 2891 in 0d29d4b
What may complicate things, is that when GAP reads package metadata on startup, it seems to automatically convert dates to "dd/mm/year"-format before storing it in
GAPInfo.PackagesInfo
, whereas no such conversion happens when callingGAPInfo.PackageInfoCurrent
. If I am working inExample
's base directory:The text was updated successfully, but these errors were encountered: