I've had some success sending a single-page HTML to my Kindle. The Kindle will
only accept HTML pages that have no dependencies on external files, i.e., no
external CSS, and no external image files, both of which problems can be
solved. HTML is obviously nicer than PDF on the Kindle because the
"Pointage"? Like mileage, footage, poundage ...
--d
Sent from Yahoo Mail on Android
On Sun, Apr 18, 2021 at 9:39 PM, Bjarni Ingi Gislason
wrote: Bug #60403 (closed) unified the writing of "point-size" to "point
size".
The problem is,
that this coinage does not make sense.
The "poin
\N'num' takes a number num and typesets the glyph corresponding to the code
point num in the prevailing font. Currently, num can only be in decimal format.
Is there a downside to allowing hex numbers, with the usual distinguishing
prefix 0x?
--d
d the list because what I have to ask you is
important. I used to work in software licensing compliance
professionally, so perhaps I am extra paranoid.
At 2021-01-14T06:05:41+0000, Dorai Sitaram via wrote:
> Absolutely, do add whatever license is needed; and modify what I have
> (bo
Absolutely, do add whatever license is needed; and modify what I have (both
code and documentation) to suit groff's standards. My repo is purely temporary
and meant to ferry the code to you better than email can.
--d
On Thursday, January 14, 2021, 12:32:19 AM EST, G. Branden Robinson
wro
Lauther wrote:
> > On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> > > groff pretty much forces one to use two spaces after
> > > sentence-ending punctuation, unless it's at the end of a source
> > > line.
> >
> > In my opinion it
Thanks, John! Just what I was looking for (but didn't know how to search for).
--d
On Friday, January 8, 2021, 05:19:12 AM EST, John A.
wrote:
On 2021-01-08, Dorai Sitaram wrote:
> What's a good way to put a bit of text in the left margin of the
> "current&quo
sentence-final periods?
Ricky
> On Jan 6, 2021, at 11:44 AM, Dorai Sitaram via wrote:
>
> Thanks, Doug! I've updated https://gitlab.com/ds26gte/groff1345 to include
> your suggestions 2 and 3.
>
> I am not at all confident that the man page I've added hits the rig
Thanks, Doug! I've updated https://gitlab.com/ds26gte/groff1345 to include
your suggestions 2 and 3.
I am not at all confident that the man page I've added hits the right notes or
even uses the correct terminology, but the community can easily correct it to
meet its standards.
--d
O
tence in
1999, but the rouble...?
I've added these into the latest https://gitlab.com/ds26gte/groff1345
--d
On Monday, January 4, 2021, 10:43:53 PM EST, Dorai Sitaram via
wrote:
To avoid emailing updated versions of rfc1345.tmac, I've created a temporary
Git repo
htt
On Monday, January 4, 2021, 03:12:42 PM EST, Dorai Sitaram via
wrote:
Indeed it doesn't. (TBH, I've never warmed to the single-character ellipsis
as it seems too narrow in most fonts.)
I notice Vim's digraph system (which is based on RFC 1345) uses the digraph ,.
(comma-follow
ng that it is not in
groff either considering groff was originally written by a British
person.
It is available as \N'188' in the symbol font or as \[u2026].
Denis
On Mon, 4 Jan 2021 05:20:26 + (UTC)
Dorai Sitaram via wrote:
> Enclosed is my draft for does.tmac.
>
>
&g
Enclosed is my draft for rfc1345.tmac.
--d
On Sunday, January 3, 2021, 09:27:06 PM EST, Dorai Sitaram via
wrote:
I'll be happy to write up an rfc1345.tmac and send it to you. I don't think
it requires a tremendous amount of maintenance, as the list of mnemonics
appe
At 2020-12-14T19:07:06+0000, Dorai Sitaram via wrote:
> s.tmac defines a bunch of strings to display extra glyphs if the user
> calls the .AM macro. Most of these glyphs are already available with
> standard glyph names, and, as far as I can tell, the only new glyph
> defined is the ho
t
really need to re-train, or re-re-train, myself. I've been able to configure my
text editor so it will insert the extra space if I missed it, but only for
groff input. And, no, it's not too difficult to develop a heuristic for when to
insert that second space. In Vim, for instance
r edit it to save my life. L*rd knows I've tried.
--d
On Saturday, December 19, 2020, 01:17:02 PM EST, Peter Schaffter
wrote:
On Sat, Dec 19, 2020, Ulrich Lauther wrote:
> On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> > groff pretty much forces one to
groff pretty much forces one to use two spaces after sentence-ending
punctuation, unless it's at the end of a source line. Is there a way to avoid
this, so that the space is uniform regardless of whether the ending punctuation
occurs mid- or end-line? (I could resign myself to always type 2 spa
Thank you, Keith!
--d
On Thursday, December 17, 2020, 12:48:35 PM EST, Keith Marshall
wrote:
On 17/12/2020 14:37, Dorai Sitaram via wrote:
> Wow, this (Oliver's suggestion) actually works. ...
I don't know why I even bother!
https://lists.gnu.org/archive/html/
do not know whether the
safe/unsafe setting will impact reading from stdin.
Oliver.
On 17/12/2020 15:05, Colin Watson wrote:
> On Wed, Dec 16, 2020 at 08:30:33PM -0600, Dave Kemper wrote:
>> On 12/15/20, Dorai Sitaram wrote:
>>> Thanks Dave, for the suggestion. That doesn'
Thanks Dave, for the suggestion. That doesn't seem to be the problem, however,
on my machine (Ubuntu 20.10). No-argument cat works as expected.
--dOn Tuesday, December 15, 2020, 04:50:01 PM EST, Dave Kemper
wrote:
On 12/15/20, Oliver Corff wrote:
> I have no other version at hand so
he request .rd works as expected.
Oliver.
On 15/12/2020 19:59, Dorai Sitaram via wrote:
> groff.texi mentions the request .rd that's supposed to read user input
> mid-run, but I can't seem to get it work at all. No prompt, just quite
> ignoration.
>
>
> --d
>
groff.texi mentions the request .rd that's supposed to read user input mid-run,
but I can't seem to get it work at all. No prompt, just quite ignoration.
--d
s.tmac defines a bunch of strings to display extra glyphs if the user calls the
.AM macro. Most of these glyphs are already available with standard glyph
names, and, as far as I can tell, the only new glyph defined is the hooked o,
(equivalent to Latin small letter o with ogonek). Both a string
Is the problem here really an error in syntax highlighting? I don't know the
intricacies of -mom, but it seems rather that the incorrect style of comment
(the one that eats a newline) was being used here. Eschewing syntax
highlighting would have brought the author no closer to recognizing thi
The 5/6 may be a relatively recent consensus based on peer monitoring. UTP
doesn't mention 5/6, for instance. It has its own (slightly less) strange
fraction though: 11/12 (see p. 606). When it came to FL, it was a Wild West out
there back then, I tell ya.
--d
On Sunday, November 15, 20
Is there a recent version of the script 'fixmp' mentioned in the MetaPost
documentation? (It allows groff to accept MP-generated PS files.)
Google points me back to these archives for a 2006 version that no longer works.
Thanks--d
UTP strongly hints that the -ms macros have the end-of-input trap .em pre-set
to a defined macro called .EM, with the implication that if the user wants to
affect end-of-input behavior they can append or prepend to this macro rather
than messing with .em directly. However groff's s.tmac sets its
Is there a way to change the text used for the section header inserted by
'refer' before the accumulated references? By default, it is "References".
Hopefully it isn't hardcoded.
--d
I have GROFF_ENCODING set to utf8, but this only works for the main file
processed by groff, not to any subfiles that are sourced via .so .
Giving the -s option to groff to force a soelim doesn't work either.
Adding the -k option to force a preconv, whether before or after the -s option,
doesn'
Branden,
That's a pretty good guide. Thank you for your effort!
When you say points are '(about 1/72")', it probably doesn't hurt to go the
extra mile (!) in precision and say '(1/72.27")'. It's shorter (no need for
'about') and more correct. Also I would spell out inches here, as the
double-pr
I have some some Unicode characters with codes higher than 256 (e.g., smart
quotes) that 'refer' chokes on with the message "invalid input character code".
Is there a way to tell refer to just pass them through to stdout? The error
happens even if the offending characters don't occur inside th
Hi Carsten:
[Sorry. didn't send to group on first try.]
This is somewhat related. What is the canonical way to determine using generic
troff commands that the troff being used is Heirloom troff, without regard to
whether compatibility is off or on? (I used to test the number register .g to
rul
For those used to LaTeX, there is a pca-ix.tmac in my github.com/ds26gte/mpca
that can be used for index generation in -ms documents, using the same
'makeindex' program that LaTeX relies on, and which is available separately and
freely for all *nix-y systems.
Usage:
.IX text to be indexed
It has
er 26, 2015 12:16 PM, Keith Marshall
wrote:
On 26/10/15 13:12, Dorai Sitaram wrote:
> Incidentally, is there a way to tell from inside a document whether
> it is being processed by pdfroff or groff -Tps? In both cases, the
> string register .T is 'ps'.
Not really; pdf
Wouldn't it be useful to have the possibility of recursively searching the
subdirectories of a directory in GROFF_TMAC_PATH, typically with the addition
of a double-slash at the end of the concerned directory's name? (Cf. TeX's
TEXINPUTS.)
E.g.,
export GROFF_TMAC_PATH=$HOME/groffinputs//:
would
Thanks Ralph. I guess +x would have the same "accumulating" behavior as -x.
Curious there seems to be no way to represent a negative literal number the way
one can specify a nonnegative one, i.e., a negative number just for itself, not
as a decrement.
I was able to solve my particular problem w
I did a relative set of the PO (page-offset) register at the head of an ms
document
.nr PO -.25i
(I.e., I wanted it to be a quarter-inch less than its default value.)
Surprisingly to me, even though this statement was placed only once, at the
beginning of the document, its effect seems to be repe
Thankfully, it looks like I may have goofed and picked the wrong printout while
measuring lengths.
Everything seems to work fine now! Sorry about the false alarm!
--d
On Tuesday, March 17, 2015 11:11 PM, Doug McIlroy
wrote:
> If I set ?registers PO and LL and also set PS and VS,
If I set registers PO and LL and also set PS and VS, the values of PO and LL
seem to revert to the default values. It doesn't seem to matter which order I
set these registers in (all done in the preamble of the document of course).
What is a way to make all settings of these four registers sti
Found a solution! In the sourced file, instead of
.char ∖ \[u005C]
use
.char \[u2216] \[u005C]
--d
On Monday, March 2, 2015 2:56 PM, "carsten.ku...@arcor.de"
wrote:
Dorai Sitaram wrote:
> I had the following
> .char ? \[u005C]
> in a file (the first ? is U
I had the following
.char ∖ \[u005C]
in a file (the first ∖ is U+2216, or set-minus) and used set-minus within the
same file, and it works fine.
However, when I place the .char call in a different file, and source it via .so
or .mso, occurrences of set-minus in the sourcing file don't translate.
As is probably well known, the labels (btex ... etex) embedded in metapost
files don't show up well when the PostScript file is loaded into a groff
document using .PSPIC.
For example:
% mpost -troff lambda.mp
produces lambda.1
Inside a groff document eg.ms, use
.PSPIC lambda.1
The problems seem t
I have the environment variable GROFF_ENCODING globally set to utf8, and the
groff I'm using is
GNU groff version 1.22.2GNU grops (groff) version 1.22.2GNU troff (groff)
version 1.22.2
on Ubuntu 14.10 (64-bit)
I tried your example and I get, with both troff and nroff,
name expected (got a specia
Is this planned? Section 5.4 of the manual suggests that "almost any printable
character" can be used, with the exception of spaces and such, but I found that
even an ordinary-looking character like the pilcrow (U+00b6) creates error.
--d
I did all that (cvs up -dP, autoreconf) and still get what Heinz-Jürgen got.
Checked the date on groff.cpp and it says 2012. I also did a brand-new groff
checkout via cvs. No difference.
By the way, isn't groff --version supposed to exit after displaying the
version? It is waiting for input,
+1 on makeindex. See http://www.ccs.neu.edu/~dorai/troff2page (section 5) if
one wants to work off a working example.
--d
>
>From: "ted.hard...@wlandres.net"
>To: groff@gnu.org
>Sent: Sunday, September 9, 2012 4:01 PM
>Subject: Re: [Groff] Indexing these
I think esr is emphasizing (!) that in a structural-markup language the
tags can have no typographic meaning whatsoever.
While it may be possible to mimic the tags of structural markup in a
presentation-markup language, there is power in completely and firmly
separating the two aspects: you
Wouldn't it be useful to have parameters like \$[m-n] that pick out the
parameters \$m through \$n ?
Right now, a macro's body can use \$1 ... \$n, and \$*, and \$@, and then call
.shift howsoever many times to get the right "slice". However, a similar
ability isn't available for string defini
While on this subject, I'm trying to have (in -ms) the page number centered on
the footer rather than the header. So I do the requisite
.ds CH "
.ds CF \\n[PN]
But I notice the page number is set way too low on the page, and too far away
from the end of text. Fiddling with the values of the
In the man page for groff_www, in the description of the command .HTML, the
following example is given:
.de BGIMG
. HTML
..
Should not the second line read instead:
. HTML
I.e., with two backslashes?
thanks,
dorai
1. When I run groff with -Dutf8, it complains that gpreconv is not available.
This can be worked around by creating a soft link to preconv.
2. The more serious problem is this: -Dutf8 is not pervasive through .so or
.nx. It only applies to the file the main file that groff is called on.
> On Wed, Jun 03, 2009 at 08:55:23AM +0100, John¹ wrote:
> > Subject: [Groff] Typesetting Software
> >
> > Many years ago, when type used to be set by hand, I was one of those who
> > did the typesetting. I am now looking at the methodology of using either
> > Groff or LaTex to produce print
Excellent! I've experimented with it for a while, and it works as documented
except for one bit of strange behavior:
If the first thing that occurs in the text following leading spaces is a
font-switch, the font-switch doesn't take effect. If the font-switch is not
the first thing, it does
It should be enough to just check that the line (otherwise not empty) begins
with at least one space. Reading ahead to count the number of spaces is not
needed, and may indeed be bad, because the spaces need to print as usual.
As a example, consider the following text:
"This is a paragraph. T
Yes, that would work. Thus, the user defines a particular macro name to change
the default effect of space-at-line-start (implicit .br), just like the user
defines BLM to change the default effect of empty-line (implicit .sp).
--d
From: Werner LEMBERG
To: ds
groff can tell if an input line starts with horizontal space, and inserts a
line break. Is it possible to give the capability that checks this to the user
also? It will make it possible to write interesting macros...
--d
text. Without this local
switch, while it can still be done with a bit of tedious macrology, it is
rather unlike the -ms way.
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: Dorai Sitaram <[EMAIL PROTECTED]>
Cc: groff@gnu.org
Sent: T
I notice that groff's .PP, .LP and the like don't restore the glyph- and
fill-color to the default (black and white). Shouldn't they, in analogy to how
they treat font- and size-switches?
--d
> Can you provide a patch for www.tmac?
>
>
> Werner
I have placed my suggested changes in
http://www.ccs.neu.edu/~dorai/groffpatch/index.html
You can see or download the various files, including the explanation from
there, either singly or as a tarball.
Please feel free to modify to sui
Yes, having .TAG define a TAG- would be useful.
I would suggest defining TAG- as a string rather than as a macro, so
people can easily refer to it "in-line".
Also, in the first pass, \*[TAG-] will successfully refer to TAG's
second argument (or page number, if second arg missing) for ba
Something is not quite right -- I may not have stated the bug precisely. I am
using the development snapshot (the one that the site says is produced twice a
day) with a stated version of 1.19.3 (which doesn't pinpoint the day of the
snapshot).
I can confirm that the bug is still present in t
.PIMG -C img.png
and
.PIMG img.png
both cause the following error:
can't open `-C': No such file or directory
The error doesn't happen when I specify an alignment argument of -L or -R.
--d
Looking
The .URL and .TAG macros defined in www.tmac have the following behavior when
processed by a device other than -Thtml.
.TAG label
.URL #label foo
produces
foo <#label>
The text <#label> isn't informative because the printed document has no #label
that the reader can determine. Would it not
Would it be possible to add a file-existence-checker to groff that works in
safe mode?
Right now, I use a macro
.de fileexists
.sy test -f \\$1
..
Example use:
.fileexists foo.tmp
.ie !\n[systat] .code_that_uses_foo.tmp
.el .unsafe_code
unsafe_code could set up the conditions for creating foo
This is for Alejandro Lopez-Valencia, if he's still fielding reports on his
very useful and tasteful nroff.vim syntax file.
This synax file currently highlights a .ig environment as a comment, but
assumes that the .ig will always be closed by a double-dot (..), even if the
.ig has an argument
Thanks!
Now, unless I'm misreading the intent, the documented \n[.U] is ascribed
behavior opposite to what actually happens. According to the manual, "If
gtroff is called with the -U command line option, the number register .U is set
to 1, otherwise to zero."
On groff 1.19.3 (on Solaris), I u
After checking the docs, it doesn't seem like groff offers a register or any
other way for checking if it is being run in unsafe mode. Would this not be a
good idea? I have some macros that use unsafe requests to create and update an
index. I'd like for these macros to be silent or issue may
Given a .JOBNAME request in the input document, groff -Thtml creates multiple
output HTML files, splitting the input at every .NH 1 and .SH.
Groff's ms's .SH takes an optional numeric argument n whereby .SH n typesets in
a style (font size) similar to .NH n. (By default, n = 1.)
I think that
Meg McRoberts wrote
>
> I prefer HTML as an output format from the same source that can also
> generate PS, PDF, formatted ASCII... It's great to get a technical
> document into HTML to display on the web but if I want a printed
> copy, the HTML doc isn't compact enough to be satisfying...
I wo
Is it considered a security risk to allow ~ or shell environment variables
in the argument to .so? For example,
.so ~/.groffrc
.so $HOME/.groffrc
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
I was wondering why Gaius had to generate an image for .DC for the HTML output.
Using the following CSS declaration
.dropcap {
line-height: 90%;
font-size: 400%;
float: left;
}
and enclosing the letter to be dropped inside
...
produces a decent dropcap. (The color argument can be
Y 0
> .\}
>
> at the top of my file. If you don't want nroff to paginate, add
> a .pl 1000 right after the .nr HY 0, and a .pl \n[nl]u at the end
> of the file.
>
> jcs
>
> On Wed, Mar 16, 2005 at 03:08:59PM -0500, Dorai Sitaram wrote:
> > I'd li
Thanks, Werner!
--d
>
>
> I've uploaded groff.html (from the current CVS) as
>
> http://groff.ffii.org/groff/devel/groff.html.bz2
>
>
> Werner
>
>
> ___
> Groff mailing list
> Groff@gnu.org
> http://lists.gnu.org/mailman/listinfo/groff
>
I'd like to avoid adjustment (justification) and hyphenation on a document
but only if it's being processed by nroff.if n). In essence,
.if n .na
.if n .nh
should hold for every paragraph. What's a robust way to do this? Trying
to adding this as a hook (via .am) to various things, like the he
I don't mind (too much) that the groff doc is currently in texinfo, but
does groff.texinfo convert into Info or HTML for anybody? It must, I know,
so what is the magic?
It consistently fails to for me, and I have texinfo and makeinfo 4.7 (and
the groff dist asks for at least 4.6, so I know I'm no
75 matches
Mail list logo
