Follow-up Comment #28, bug #63354 (project groff):

[comment #27 comment #27:]
> [colorful metaphor excised]
> I feel I must simply solicit a patch from you at this point.

OK.  As a preliminary step (for my own benefit, or anyone else's who decides
to take this and run with it), I'll update the to-do list from comment #15.

First I'll summarize what's already been done.  Items below marked *solved* or
*ameliorated* refer to changes made in the commit cited in comment #20.
1. reorder file: no action taken
2. consistently comment file: no action taken
3. \[u200B]: *ameliorated*: awaiting fix for bug #58958
4. \[u2010]: mostly *solved*, but see comment #25
5. \[u2011]: *ameliorated*: awaiting fix for bug #63360
6. \[u2012]: *ameliorated* (using comment #18 patch), but has issue explained
in comment #22.
7. \[u2016]: *solved*
8. \[u2018], \[u2019], \[u201C], \[u201D]: *ameliorated*: awaiting fix for bug
#59932
9. \[u2026]: proposed action not taken: see comment #19.
10. \[u202F]: no action taken
11. \[u203D]: no action taken
12. \[u2052]: no action taken

So for the purposes of _this_ ticket, we can cross off *solved* items, and
ones *ameliorated* but awaiting fixes for other tickets.  This creates the new
to-do list for this ticket below.  (I've retained the slots for the *done*
items so the numbering won't change, to stave off potential confusion if
subsequent comments refer to item numbers.)
1. reorder file ([comment #0 original submission])
2. consistently comment file ([comment #0 original submission])
3. *done*
4. \[u2010]: remove misleading line (comment #25)
5. *done*
6. \[u2012]: fix comment #22 issue (comment #23, comment #26)
7. *done*
8. *done*
9. \[u2026]: potentially remove (comment #19, comment #24, comment #27)
10. \[u202F]: add a fallback (comment #4)
11. \[u203D]: give an nroff fallback (comment #9, as amended by comment #12)
12. \[u2052]: refine definition for robustness ([comment #0 original
submission])
These are not all of equal importance, nor should they all be done in the same
commit (1, 2, and 4, for instance, are only refactors, so should be done
separately from actual code changes).  So at least two patches will follow.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63354>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/


Reply via email to