SF.net SVN: docutils:[9590] trunk
grubert--- via Docutils-checkins <[email protected]>
| Newsgroups | gmane.text.docutils.cvs |
|---|---|
| Message-ID | <[email protected]> |
Revision: 9590
http://sourceforge.net/p/docutils/code/9590
Author: grubert
Date: 2024-03-25 13:15:31 +0000 (Mon, 25 Mar 2024)
Log Message:
-----------
move manpage problems from docs/user to sandbox
Modified Paths:
--------------
trunk/docutils/docs/user/manpage.txt
trunk/sandbox/manpage-writer/TODO.txt
Modified: trunk/docutils/docs/user/manpage.txt
===================================================================
--- trunk/docutils/docs/user/manpage.txt 2024-03-25 13:07:08 UTC (rev 9589)
+++ trunk/docutils/docs/user/manpage.txt 2024-03-25 13:15:31 UTC (rev 9590)
@@ -146,51 +146,4 @@
.B #include <stdio.h>
-Questions and Answers
-'''''''''''''''''''''
-
-* How to typeset command/man page names in text.
-
- Subsection "Font style macros" of *groff_man_style*\(7) has advice.
-
-* Line ends around email or web addresses in texts.
-
- The ``UE`` and ``ME`` macros accept an argument, which is appended to
- the link text without intervening space.
-
-TODO - Open issues
-''''''''''''''''''
-
-* How to escape double quotes in macro arguments?
-
- Use the escape sequence ``\[dq]``. ``rst2man`` has to generate this
- when populating a macro's argument list.
-
-* How to distinguish something is inline or not in the writer
- so to maybe put long urls after the current paragraph ?
-
-* How to write long syntax lines.
-
- In *roff*, a backslash followed by a newline will continue the input
- line. Will ``rst2man`` pass that through or require its doubling?
-
-* Images and equations are discouraged.
-* Lists in admonitions are not intended.
-* Encoding declaration ``'\" t -*- coding: ISO-8859-1 -*-``
- in first line.
-
- The part after ``t`` is a GNU Emacs convention. A *groff* program
- called *preconv*\(1) understands it, but GNU *troff*\(1) itself does
- not.
-
- The ``t`` is part of a *man*\(1) convention; GNU *troff*\(1) doesn't
- understand it, either (but since *tbl*\(1) is a *roff* preprocessor,
- it's too late by the time ``troff`` sees the input anyway).
-
-* BUT if UTF-8 is declared tables are no longer processed.
-
-* BUT we have a comment there and the macros following it
-
-* Input and output encoding are problematic at least.
-
.. _Docutils: https://docutils.sourceforge.io/
Modified: trunk/sandbox/manpage-writer/TODO.txt
===================================================================
--- trunk/sandbox/manpage-writer/TODO.txt 2024-03-25 13:07:08 UTC (rev 9589)
+++ trunk/sandbox/manpage-writer/TODO.txt 2024-03-25 13:15:31 UTC (rev 9590)
@@ -3,6 +3,25 @@
:Date: $Date$
+* Images and equations are discouraged.
+* Lists in admonitions are not intended.
+* Encoding declaration ``'\" t -*- coding: ISO-8859-1 -*-``
+ in first line.
+
+ The part after ``t`` is a GNU Emacs convention. A *groff* program
+ called *preconv*\(1) understands it, but GNU *troff*\(1) itself does
+ not.
+
+ The ``t`` is part of a *man*\(1) convention; GNU *troff*\(1) doesn't
+ understand it, either (but since *tbl*\(1) is a *roff* preprocessor,
+ it's too late by the time ``troff`` sees the input anyway).
+
+* BUT if UTF-8 is declared tables are no longer processed.
+
+* BUT we have a comment there and the macros following it
+
+* Input and output encoding are problematic at least.
+
* input/optionstoo.txt:23: (ERROR/3) Unexpected indentation.
is what it is ... leave it so.
@@ -92,8 +111,11 @@
* Line ends around email or web addresses in texts.
-groff_man_style(7) explains.
+ The ``UE`` and ``ME`` macros accept an argument, which is appended to
+ the link text without intervening space.
+ groff_man_style(7) explains.
+
\c End a text line without inserting space or attempting a
break. Normally, if filling is enabled, the end of a text
line is treated like a space; an output line may be broken
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.