groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 01/02: BRANCH-TODO: Add "acceptance criteria".


From: G. Branden Robinson
Subject: [groff] 01/02: BRANCH-TODO: Add "acceptance criteria".
Date: Sun, 18 Apr 2021 01:52:43 -0400 (EDT)

gbranden pushed a commit to branch dev-gropdf-boxes
in repository groff.

commit f5d37ff4337eafda031838ff213c2747941ac55f
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Apr 18 15:26:29 2021 +1000

    BRANCH-TODO: Add "acceptance criteria".
---
 BRANCH-TODO | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/BRANCH-TODO b/BRANCH-TODO
new file mode 100644
index 0000000..ea6f3dc
--- /dev/null
+++ b/BRANCH-TODO
@@ -0,0 +1,36 @@
+Keep this branch up to date with 'master'.
+
+$ git checkout $THIS_BRANCH
+$ git rebase master
+
+Resolve the following issues.
+
+* Get it building with 'make distcheck'.
+* Style-tweak the new document msboxes.pdf.
+  - Use BI in title.
+  - Recast language to time-proof it (avoid "recent").
+  - Use correct \[aq] glyphs in code literals.
+  - The font is wrong outside the box once the document source is
+    presented (headers and footnotes are in Courier on pp. 3-4).
+* Update gropdf(1) to document \X'pdf: background'.
+* Decide on a place in the existing ms name space definition for the new
+  macros.  "BoxStart" and "BoxStop" are in the part we say we won't use.
+  Maybe "BOXSTART" and "BOXSTOP" or "BOX1" and "BOX2".  ("B1" and "B2"
+  already exist and are similar, with much less functionality.)
+* Does sboxes need to be in contrib?  gropdf isn't.  Can we put it in
+  tmac?
+* Should we opportunistically load sboxes.tmac from s.tmac?  The user
+  would then not need to specify an "-msboxes" argument to groff.
+  (AT&T troff did this to modularize ms with
+  tmac.s{cover,disp,keep,refs}.)
+* Fix copyright notices.  This is piping fresh 2021 stuff.
+
+When commits have been to the branch resolving all of the above, delete
+this file and rebase the branch onto master.
+
+$ git checkout master
+$ git rebase $THIS_BRANCH
+
+If this branch was kept up to date, there should be no problems.
+
+GBR, 2021-04-18



reply via email to

[Prev in Thread] Current Thread [Next in Thread]