Werner LEMBERG:
> Indeed. However, it's just a matter of taste to
> handle funny preconv and soelim cases with either
>
>soelim | groff -K ...
>
> (current groff) or with
>
>preconv -e... | groff -s ...
>
> (patched groff)
It didn't occur to me. There's no need to patch it
then...
-
>> >> $ groff -V -s -Kcp1251 -t -Tutf8
>> >> soelim | preconv -ecp1251 | tbl | troff -Tutf8 | grotty
>> >
>> > Not that you should ever do this, but if you were using, say,
>> > UTF-16, soelim would not be very effective unless preconv ran
>> > first.
>
> Could soelim be rewritten to use fgetw
On Fri, Dec 07, 2012 at 07:36:09AM +0100, Werner LEMBERG wrote:
>
> >> $ groff -V -s -Kcp1251 -t -Tutf8
> >> soelim | preconv -ecp1251 | tbl | troff -Tutf8 | grotty
> >
> > Not that you should ever do this, but if you were using, say,
> > UTF-16, soelim would not be very effective unless preco
>> $ groff -V -s -Kcp1251 -t -Tutf8
>> soelim | preconv -ecp1251 | tbl | troff -Tutf8 | grotty
>
> Not that you should ever do this, but if you were using, say,
> UTF-16, soelim would not be very effective unless preconv ran first.
Indeed. However, it's just a matter of taste to handle funny
On Thu, Dec 06, 2012 at 02:20:13PM +0100, Werner LEMBERG wrote:
> This has been discussed a few months ago on the list, IIRC, and then I
> stated that I no longer remembered why soelim comes after preconv.
> Unfortunately, this comment is still true: I can't remember the
> exact cause.
>
> $ gro
>> Does groff's -V option help? It shows the constructed pipeline.
>>
>> $ groff -V -Kcp1251 -t -Tutf8
>> preconv -ecp1251 | tbl | troff -Tutf8 | grotty
>> $ groff -V -s -Kcp1251 -t -Tutf8
>> preconv -ecp1251 | soelim | tbl | troff -Tutf8 | grotty
>>
>> The preconv has happened be
Ralph Corderoy:
> > mmst1: tr -d 15 < [infile]| groff -s -Kcp1251 -t
> > -Tutf8>[outfile].txt
> > mmst2: soelim [infile] | tr -d 15 | groff-Kcp1251 -t
> > -Tutf8>[outfile].txt
> >
> > With the included test file (test.mm) the first
> > call seems to
Hi Anton,
> mmst1: tr -d \015 < [infile]| groff -s -Kcp1251 -t
> -Tutf8>[outfile].txt
> mmst2: soelim [infile] | tr -d \015 | groff-Kcp1251 -t
> -Tutf8>[outfile].txt
Does groff's -V option help? It shows the constructed pipeline.
$ groff -V -Kcp1251 -t
Tadziu Hoffmann:
> Interesting that you mention this, because that's
> exactly what I usually do (inspired by man, of
> course). That is, I have a shell script "myroff"
> [*] which reads the first line of the input file,
> interprets it as options, and calls groff accord-
> ingly (and als
> Nevertheless, I think it would be better then to store both
> a tmac.-raw file and a preprocessed tmac..
>From what I've read, the old Bell Labs [nt]roff had an option
to read macro files in a sort of "compiled" version (to reduce
startup time), so if one used this feature it would have been
us
Werner LEMBERG:
> Compare this to the doc package: Before installa-
> tion to the tmac directory, (almost) all names
> have the prefix `doc-' which gets stripped, to-
> gether with all leading whitespace. Using a Make-
> file for doing `make install', it is really triv-
> ial to preproce
> On the other hand, I already have a macro package which I use to
> maintain more than one document. Naturally, I want to keep it in
> the tmac directory and call via the -m option, which I can't because
> it has to be preprocessed with gpreconv on account of its containing
> bits of Russian tex
> Files included via .mso, .so, or -m, are never run through
> preprocessors.
That's why soelim was invented
http://lists.gnu.org/archive/html/groff/2003-01/msg00069.html
(at least for .so, don't know about .mso or -m).
Hello all,
I have a problem designing well-strucutred documents
consisting of several files. Files included via
.mso, .so, or -m, are never run through preproces-
sors. For example, it is very incovenient to use a
macro package containing Russian text together with
-K, and it is impossi
14 matches
Mail list logo
