ietf-tools / ietf-tools/xml2rfc

set <date> to currmonth and curryear

Open
#656 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: v3 vocabulary minor under_review
Dominant language
HTML
Stars
124
Forks
79
Avg merge
6h 30m
Merged PRs (30d)
3

Description

type_enhancement | by arusso@amsl.com


Request for the ability to get current month and current year in the rendered files using or similar.

Would be used during editorial processing as a document moves through the queue. Would use within and well as within a that is moving through the queue simultaneously, i.e., a cluster. (Using empty is not preferred because there's zero output in the case.)

Example (where this reference appears in a document that will be published simultaneously):

<reference anchor='RFCnnnn' target='https://www.rfc-editor.org/info/rfcnnnn'>
  <front>
    <title>Foo Protocol</title>
    <author initials='J' surname='Doe' fullname='Jane Doe'>
      <organization />
    </author>
    <date month='currmonth' year='curryear' />
  </front>
  <seriesInfo name='RFC' value='nnnn'/>
  <seriesInfo name='DOI' value='10.17487/RFCnnnn'/>
</reference>

where <date month='currmonth' year='curryear' /> would yield "July 2021" today.


Issue migrated from trac:656 at 2022-02-08 07:16:24 +0000

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no implementation files or tests. Start by tracing how date elements are rendered in xml2rfc and how dates inside references are handled. Done means a current month and year can be requested with the proposed date syntax and the rendered output matches the processing date.

Written by the indexing model from the issue text.

Assessment

Tech stack
xml
Domain
documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.