If Now-Date has variables that contain text (%a,%A,%b,%B,%p), they might not get matched properly...
1: If a now-name begins with any date-text (like July), the date-text cant be matched.
-- (but with at least 1-character before the date-text, its recognized and converted).
2: If a now-name has any date-text (like May), but with extra-letters and no separators (like Mayor),
-- then the extra-letters are considered as part of the date (and get removed with any conversion).
Examples of matching custom-date-formats in now-names...
July 04, 2023 -------------> %B %d, %Y is not recognized (since now-name starts with date-text).
aJuly 04, 2023 ------------> %B %d, %Y conducts properly (since at least 1-char precedes date-text).
2023-04-JulyInSweden ---> InSweden is considered part of date-text (and gets removed with any date-conversion)
............................... Even something like %Y %d %B>%Y-%d-%B (to change separators) still removes InSweden.
===========================
Some examples of "Reformat Date" without specifying date-formats, so these are probably not bugs?...
7890123.txt ----------> 7890-12-03.txt (seems correct, if users prefer matching years >20##, and there can be 1-digit-days)
67890123.txt ---------> 6789-01-23.txt (seems correct, if users prefer matching years >20##)
678901234.txt --------> 6789-01-234.txt (seems correct, if users prefer more numbers can follow the date)
1234567890123 -------> (not converted) (seem correct, if uses prefer more numbers should not precede the date)
202490123.txt --------> (not converted) (seems correct if users prefer 2-digit-months) (so dont covert to 2024-09-0123)