[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20885 [Core Tor/Tor]: Portions of the tor.1 man page and html doc formatted incorrectly
#20885: Portions of the tor.1 man page and html doc formatted incorrectly
--------------------------+------------------------------------
Reporter: jryans | Owner: jryans
Type: defect | Status: needs_review
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: man doc | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Changes (by jryans):
* status: needs_information => needs_review
Comment:
Sorry, I should have explained that up front!
These "fake" sections were the only way I could see to have a paragraph be
indented in the style of a first-level list item when it comes after a
second-level / nested list item. All the other approaches I attempted led
to the paragraph glued onto the content of the last second-level list item
or formatted as a code sample, both of which are not what's intended.
(There seems to be no explicit way to "end" the second-level list, so you
have to find some way to trigger that implicitly. asciidoc is strange.)
I noticed there is a pre-existing usage of this technique with
`OtherSocksPortFlags`. So anyway, these sections could really be named
anything, since they don't appear in the output. Any suggestions for less
confusing names, or do they seem okay?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20885#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs