#x27;.ss 12 0' is the better choice in all languages? The books here on my
desk (en_US and en_UK) don't seem to have any extra end-of-sentence spacing,
or at least not as much as groff adds by default.
But I don't feel strongly about this issue.
BR,
/Jörgen
--
// Jörgen Grahn
year]
-.\". \" set hyphenation flags
-.\". nr HY 12
-.\".\}
+.if r GS \{\
+. \" update the date
+. ds DY \n[dy] \*[MO] \n[year]
+. \" set hyphenation flags
+. nr HY 12
+.\}
.
.
.\" mm package -- additional Swedish localization is done
motivated.
Still, I appreciate not having to point into my tetex installation to get
reasonable hyphenation.
/Jorgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]>-- Jonas
___
oo much.
I like the <>-like glyphs surrounding the URL, though.
My two cents,
Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Grof
y on Latin-1.
BR,
Jörgen
(speaking for myself only, and aiming to be constructive)
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
NO_SGR shell environment variable.
That's also mentioned in grotty(1).
/Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
to man,
less and their setups to make this work. For what it's worth, Debian
Gnu/Linux (which I use) chose to disable the feature in groff instead:
Disable the new ANSI colour/bold/underline escapes in nroff mode, because
most pagers either fail to cope with it or need special options t
er either
knows the string length, or takes case to append a NUL before calling
contents().
(It wouldn't be too hard to modify class string to always maintain a NUL
guard immediately after the last character of the string, if one cared to.)
/Jörgen
--
//
mber the details. They are also in the mailing list
archives, I think.
What I /do/ remember is that the previous PO (mis)feature was more serious
and harder to work around than the current one, so I'm still happy.
/Jörgen
--
// Jörgen Grahn "Kok
1338,19 @@
or
.I "groff ms"
should use this number register.
+.
+.IP \(bu
+For
+.I "groff ms"
+to use the default page offset (left margin),
+the
+.B PO
+number register must be undefined when the first
+.B ms
+macro is encountered.
+This implies that the user may not evalua
on't mention PO before the -ms macros kick
in, unless you intend to set it"? Seems like a fairly acceptable and
predictable rule to me -- despite my earlier confusion.
BR,
Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta.
margin.
> /usr/local/opt/groff-20050620/bin/groff -ms -Tps a >a.ps
After the LP, the value of PO is 0.
> /usr/local/opt/groff-20050620/bin/groff -ms -Tps b > b.ps
Before the LP, the value of PO is 0.
After the LP, the value of PO is 0.
> /usr/local/opt/groff-20050620/bin/groff -ms -T
current_filename = whole_filename.contents();
current_lineno = 1;
set_location();
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
a sane, portable way of eliminating the parenthesis?)
/Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
mmented-out section isn't interpreted?
I also see the "number register PO' not defined" you mention when using
nroff, but I expect my document to be broken under nroff right now.
To summarize:
solaris troff : adding the .ig section doesn't change output
semantics like those of gcc and other compilers. That would make Makefiles
easier to read and more portable -- as long as the user's troff is groff, of
course.
/Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]>
f in $(PROCESSEDEXAMPLEFILES); do \
+ for f in $(notdir $(PROCESSEDEXAMPLEFILES)); do \
rm -f $(exampledir)/$$f; \
- $(INSTALL_DATA) $$f $(exampledir)/$$f; \
+ $(INSTALL_DATA) examples/$$f $(exampledir)/$$f; \
done
uninstall_sub:
--
// Jörgen Grahn
someone here has found the neatest possible way of addressing this.
BR,
Jörgen
--
// Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta."
\X/ <[EMAIL PROTECTED]> -- Jonas
___
Groff
'.ig' ... '..'.
If I remove the .ig section (and its contents), I get a margin which seems
to be the -ms default and all is well.
Or have I misunderstood the .ig request completely?
BR,
Jörgen
--
// Jörgen Grahn "Koka lopplummer, ba
9% of all shell
scripts will break on such a system, making it unusable.
There are many incompatibilities among the shells that *can* be /bin/sh
(ksh, pdksh, ash, bash, zsh ...) but at least they belong to the same
family of languages. Csh and tcsh are a completely different track.
/Jörgen
--
20 matches
Mail list logo
