Template talk:Calendar articles

From NovaRoma
(Difference between revisions)
Jump to: navigation, search
m (ease of use comments)
 
m
Line 2: Line 2:
  
 
For ease of use, it seems to me it might be better, in future years, to amend the naming conventions for the [[Fasti MMDCCLXIII|annual calendar]], from ''Fasti '''year (AUC) in Roman numerals''''' (e.g. ''Fasti MMDCCLV'') to ''Fasti '''year (CE) in Arabic numerals''''' (e.g. ''Fasti 2011'').  This would allow, in this template, use of the ''CURRENTYEAR'' function, which would prevent the need to continually update this template every year.  Has anyone else any thoughts on this?  ''[[User:Quintus Caecilius Metellus Pius Postumianus|Q Caecilius Metellus Postumianus]] 00:56, 15 May 2010 (CEST)''
 
For ease of use, it seems to me it might be better, in future years, to amend the naming conventions for the [[Fasti MMDCCLXIII|annual calendar]], from ''Fasti '''year (AUC) in Roman numerals''''' (e.g. ''Fasti MMDCCLV'') to ''Fasti '''year (CE) in Arabic numerals''''' (e.g. ''Fasti 2011'').  This would allow, in this template, use of the ''CURRENTYEAR'' function, which would prevent the need to continually update this template every year.  Has anyone else any thoughts on this?  ''[[User:Quintus Caecilius Metellus Pius Postumianus|Q Caecilius Metellus Postumianus]] 00:56, 15 May 2010 (CEST)''
 +
 +
:Good point about the ability to use CURRENTYEAR. We can also work this up from parserfunctions though. The upside to this is the old issue that we have had from the beginning: tho what ectent do we try to educate people through our standardization on Roman rather than modern forms? We can easily make a template, let's call is "AUC" that takes a Gregorian year in Arabic form and pops out an AUC year in Roman numerals. Coding it up in a fully generalized form would take a bit of effort, and we could even add it as an extension, but initially it could just be a look-up table.
 +
 +
:I see that we already have this: [[Template:AUC]] and it simply adds 753 to the CURRENTYEAR value, thusly: {{AUC}}. So if we add a switch and if we can find a Roman numeral converter, we'll be set. That converter would be handy to have anyway.  /\⁄\ |_  ⁄·\

Revision as of 23:17, 14 May 2010

Fasti

For ease of use, it seems to me it might be better, in future years, to amend the naming conventions for the annual calendar, from Fasti year (AUC) in Roman numerals (e.g. Fasti MMDCCLV) to Fasti year (CE) in Arabic numerals (e.g. Fasti 2011). This would allow, in this template, use of the CURRENTYEAR function, which would prevent the need to continually update this template every year. Has anyone else any thoughts on this? Q Caecilius Metellus Postumianus 00:56, 15 May 2010 (CEST)

Good point about the ability to use CURRENTYEAR. We can also work this up from parserfunctions though. The upside to this is the old issue that we have had from the beginning: tho what ectent do we try to educate people through our standardization on Roman rather than modern forms? We can easily make a template, let's call is "AUC" that takes a Gregorian year in Arabic form and pops out an AUC year in Roman numerals. Coding it up in a fully generalized form would take a bit of effort, and we could even add it as an extension, but initially it could just be a look-up table.
I see that we already have this: Template:AUC and it simply adds 753 to the CURRENTYEAR value, thusly: 2772. So if we add a switch and if we can find a Roman numeral converter, we'll be set. That converter would be handy to have anyway. /\⁄\ |_ ⁄·\
Personal tools