Displaying 2 results from an estimated 2 matches for "_dates_".
Did you mean:
_dated_
2025 Jan 16
2
Weird and changed as.roman() behavior
...in more than one sense:
1. as.roman(3899:3999) # works fine
not producing any NA
2. I think, e.g., "MMMM"
is a pretty unique representation of 4000.
Also, one piece of other software (online)
https://www.rapidtables.com/convert/number/date-to-roman-numerals.html
does convert _dates_ up to the year 4999, see,
https://www.rapidtables.com/convert/number/date-to-roman-numerals.html?msel=January&dsel=1&year=4999&fmtsel=MM.DD.YYYY
giving MMMMCMXCIX for 4999.
Hence, I also think we should enlarge the valid range from current
{1 .. 3999} to
{1 .. 4999}
Martin
2025 Jan 15
1
Weird and changed as.roman() behavior
Well, the real issue then seems to be that .roman2numeric uses an invalid regular expression:
>> grepl("^M{,3}D?C{,4}L?X{,4}V?I{,4}$", cc)
> [1] TRUE TRUE TRUE TRUE TRUE
or
>> grepl("^I{,2}$", c("II", "III", "IIII"))
> [1] TRUE TRUE FALSE
Both the TRE and the PCRE specification only allow repetition quantifiers of the