| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
cexp.3p, cpow.3p, drand48.3p, exp2.3p, expm1.3p, hypot.3p, initstate.3p, ldexp.3p, logb.3p, pow.3p, rand.3p, remquo.3p, scalbln.3p: Use '**' to indicate power-of
In the original sources, power-of is represented using superscripts.
Of course, this does not render meaningfully on a terminal.
So, instead, use a fictional '**' to represent power-of, adding
parentheses to expressions where necessary.
Unfortunately, an automated fix is not so simple. There was at
least one case (od.1p) where this fix was not correct (i.e.,
superscripting was not being used to mean power-of). Plus there
was at least one case where a long line needed to be manually
wrapped (cksum.1p). Plus, sometimes the \u..\d was used in
conjunction with font-size change markup (\s-N...\s+N) that was
variously inside or outside the \u...\d. Plus, sometimes
parentheses needed to be added around the superscript value. All
of it is probably solvable with some (slightly complicated)
scripting, but for now the manual edit just seemed much faster.
Reported-by: Xeno Antares <xenoantares@gmx.net>
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
$ man 7 uri 2>/dev/null \
|sed -n '/Writing a URI/,/^$/p';
Writing a URI
When written, URIs should be placed inside double quotes
(e.g., "http://www.kernel.org"), enclosed in angle brack‐
ets (e.g., <http://lwn.net>), or placed on a line by
themselves. A warning for those who use double-quotes:
never move extraneous punctuation (such as the period
ending a sentence or the comma in a list) inside a URI,
since this will change the value of the URI. Instead,
use angle brackets instead, or switch to a quoting system
that never includes extraneous characters inside quota‐
tion marks. This latter system, called the 'new' or
'logical' quoting system by "Hart's Rules" and the "Ox‐
ford Dictionary for Writers and Editors", is preferred
practice in Great Britain and hackers worldwide (see the
Jargon File's section on Hacker Writing Style,
⟨http://www.fwi.uva.nl/~mes/jargon/h
/HackerWritingStyle.html⟩, for more information). Older
documents suggested inserting the prefix "URL:" just be‐
fore the URI, but this form has never caught on.
Enclose URIs in .UR/.UE,
which encloses the URIs in between <> (or similar characters).
It is especially important in this case,
as the URIs are followed by '.'.
This also fixes the extraneous space that was used to
separate the URIs from the final period.
In some cases, the period ended in a line of its own.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
|
|
|
|
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
The POSIX source uses a mixture of "-" and "\(mi" for minus signs.
Formerly (2013 edition), only (or mainly) "\(mi" was used. But this has
the problem that cut and pasting code/command snippets from a page
rendered on a terminal gived the wrong glyph (not an ASCII MINUS).
Subsequently, POSIX has switched to the use of "-" in code examples
and other contexts where cut-and-paste might be used. However, many
other instances of hyphens (in descriptive text) still use "\(mi",
which renders differently in a terminal. Instead, let's use "\-"
to get an ASCII minus. This doesn't render quite right in a PDF
(since "-" and "\-" produce different glyphs), but the assumption
is that people won't be rendering the POSIX pages as PDFs, since,
after all, the standard is itself available in PDF form.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
I'm not sure why there was boldfacing here, but it doesn't
seem to match the formatting in the PDF version of the
standard, so remove it.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
The first part of the text in the COPYRIGHT section comes from
the grant letter provided IEEE/TOG.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
This is a mapping file that maps name strings to references to other
sections of the [POSIX.1] standard. In the 2013 iteration, this file
was called ",xrefs.6"; now it is called ",xrefs.5".
From Felix Janda's 2015 description:
[...] there are (naturally) a lot of references to other sections of
the POSIX.1-2008 standard. Sections, tables and lists are labeled with
lines starting with ".xR" and referenced using lines starting with
".cX". I don't have the sources for the many references to the Base
Definitions volume, the System Interfaces volume and the Shell and
Utilities volume of POSIX.1-2008. It would be very helpful to have
these sources in order to read of the Section/Table/List titles and
possibly to figure out their numbers.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
From my 2013 mail:
In the .mm files, there are various strings of the
form
\*(mn
where "mn" are arbitrary characters. My rough grepping tells me that
there are around 130 or so such strings, and in the handful that I
have looked at, these translate into fixed string expansions. For
example, "\*(Z3" maps to "ISO C standard".
Now, we could manually work out all of the mappings, but I am hoping
that [they] might all sit in a small file that TOG has. Would it be
possible to obtain that mapping file?
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
|
