> > Well, the default bundle of groff doesn't come with koi8 support.
>
> Do you want it?
No, since it can't be handled completely.
> Or everything will be dealt with by preconv?
Yes.
> >> What about hcode?
>
> Is it possible to use UTF or u names in its arguments?
Only real characters, *
Dear All,
when I make a PDF from PS with ZapfDingbats-Reverse with
ghostscript \(lh (left pointing hand) shows OK
(bounding box is too small, but that is another issue).
But if I use PSNormalizer built into my Mac OS X 10.4.5
(stripped version of some Adobe product) left hand is moved to the left
Dear Werner,
On Tue, 14 Mar 2006, Werner LEMBERG wrote:
And how can it be done? There are files for koi8 and cp1251 input
(ones with lot of trins),
Well, the default bundle of groff doesn't come with koi8 support.
Do you want it? Or everything will be dealt with by preconv?
Hmm, I've just
Larry Kollar wrote:
I did "make clean," updated, did a configure & make, and everything
seems to be working properly now. Sorry for the false alarm.
But then a trivial change to pdfroff.ms broke it again.
I guess I should bite the bullet, install it, and see if that takes
care of it.
--
Ted suggests adding the font to /font/devps/DESC (see below).
What is the purpose of this?
I haven't done it and things seem to work, but perhaps I'm missing
something.
Agreed -- if you add your fonts to /usr/share/groff/site-font/devps,
then you don't have to worry about them getting stom
> > Currently, there are no changes w.r.t. hyphenation. Just take,
> > say, ruhyphal.tex and use a bunch of .hpfcode lines to map its
> > koi-8 encoding to iso-8859-5. Then set up iso-8859-5 as the input
> > encoding as usual.
>
> Why "a bunch" of .hpfcode lines?
The hyphenation patterns in the
Am Montag, den 13.03.2006, 07:48 +0100 schrieb Werner LEMBERG:
> > I would like to know, if there is a standard column width, when I use
> > the .TS macro?
>
> Yes. If there are N columns, and a text block spans C columns, the
> default width of this text block is
>
> \n[.l]*C/(N+1)
>
> I've
> .\" line length increase to cope w/ tbl weirdness
> .ll +(\n(LLu * 62u / 100u)
> .TS
> lll.
> ... data ...
> .TE
> .\" line length decrease back to previous value
> .ll -(\n(LLu * 62u / 100u)
>
> Are there any objections against this solution?
Looks OK. On the other hand, it is not clear to me
> PS printers and software RIPs (namely, ghostscript as it is the best
> know and more widespread) have a limited repertoire of known fonts,
> the (in)famous "LaserWriter 35), be it in ROM or disk. Everything else
> must be downloaded; be it to the printer disk, RIP library directories
> and confi
Dear Werner,
On Sat, 4 Mar 2006, Werner LEMBERG wrote:
PS. I did not quite follow the developments in hyphenation support.
What has to be done to, say, russian hyphentaion file to adapt
it to the next groff version?
Currently, there are no changes w.r.t. hyphenation. Just take, say,
On 13-Mar-06 Robert Marks wrote:
> Ted suggests adding the font to /font/devps/DESC (see below).
> What is the purpose of this?
> I haven't done it and things seem to work, but perhaps I'm missing
> something.
>
>>From: (Ted Harding) <[EMAIL PROTECTED]>
>>Subject: RE: [Groff] Adding fonts to groff
On 3/13/06, Robert Marks wrote:
> Ted suggests adding the font to /font/devps/DESC (see below).
> What is the purpose of this?
> I haven't done it and things seem to work, but perhaps I'm missing something.
>
PS printers and software RIPs (namely, ghostscript as it is the best
know and more widesp
> .ev 1 \" 1a) why is this necessary?
> .di x \" 1b)
> . trf psline.ps \" 1c) dumps psline.ps with \\$1 replaced onto macro x?
> .di \" 1d)
> .ev \" 1e)
> Why are 1a) and 1e) necessary?
Switching to another environment prot
> If you add to the prologue you do it because you want to use the
> same routine over an over, so one can not `compile-in
> runtime-parameters'. I think that your example could be modified to
> do the right thing, but I would be loath to explain such a
> complicated thing to any user, let alone t
> A simple version (read you know there is a large line) can be found
> at /proc/cpuinfo most lines fit nicely on one line. but the flags
> entry (e.g. mine) can be quit large.
>
> /* larges line: */
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clf
> Ted suggests adding the font to /font/devps/DESC (see below).
> What is the purpose of this?
Registering a font in the DESC file makes groff load it at startup.
Today, this makes only sense if the font is `special' -- but even in
this case it is often more convenient to use the `.special' reques
> Having installed a new font, I now want to print all characters.
> I thought of having a loop:
>
> for i=1 to 350 do X
> "i" "\N'i'"
> X
>
> But this won't work, of course.
Actually, it works -- see below. I'll update the documentation
(namely that the `c' conditional operator works with \N'.
> Having installed a new font, I now want to print all characters.
> I thought of having a loop:
>
> for i=1 to 350 do X
> "i" "\N'i'"
> X
>
> But this won't work, of course.
> How can I do such a thing?
.nr index 0 1
.while (\n+[index] <= 350) \{\
. nop \n[index]: \N[\n[index]]
. br
. \}
HTH,
On 13-Mar-06 Robert Marks wrote:
> Having installed a new font, I now want to print all characters.
> I thought of having a loop:
>
> for i=1 to 350 do X
> "i" "\N'i'"
> X
>
> But this won't work, of course.
> How can I do such a thing?
.nr NN 0 1
.while \n+[NN]<255 \n[NN]\0\N'\n[NN]'\0\0
is on
Having installed a new font, I now want to print all characters.
I thought of having a loop:
for i=1 to 350 do X
"i" "\N'i'"
X
But this won't work, of course.
How can I do such a thing?
Thanks,
Bob
--
Robert MARKS, Australian Graduate School of Management,
UNSW SYDNEY, NSW 2052,
Ted suggests adding the font to /font/devps/DESC (see below).
What is the purpose of this?
I haven't done it and things seem to work, but perhaps I'm missing something.
>From: (Ted Harding) <[EMAIL PROTECTED]>
>Subject: RE: [Groff] Adding fonts to groff -- instructions?
>
>10. Edit /usr/share/grof
asume we create a datasheet from a database entry.
normaly you have line of "right" lenght (meaning they do not spoil the
layout). So your document is nice untill someonly realy uses the max
size in the database.
A simple version (read you know there is a large line) can be found at
/proc/cpu
On 13/03/2006, at 7:20 PM, Werner LEMBERG wrote:
There is an underline character in every name which does not look good
in print.
I had this problem even in troff where I tried to lift the underline
character by translating it to \(ru.
\[ru] is defined as follows in ps.tmac:
.char \[ru]
> i have noticed the problem also (mostly fixing the problem by adding
> T{ to every line. a max width sepcifierer would be helpfull.
> (forcing a wrap ?)
I don't really understand. Please give an example.
Werner
___
Groff mailing list
Groff@gn
Hi Werner,
i have noticed the problem also (mostly fixing the problem by adding T{
to every line. a max width sepcifierer would be helpfull.
(forcing a wrap ?)
re,
walter
Werner LEMBERG wrote:
I would like to know, if there is a standard column width, when I use
the .TS macro?
Yes. If t
> There is an underline character in every name which does not look good
> in print.
> I had this problem even in troff where I tried to lift the underline
> character by translating it to \(ru.
\[ru] is defined as follows in ps.tmac:
.char \[ru] \D'l .5m 0'
If you want to lift up the underli
Hello font folks,
This is not a matter of life & death, just an annoyance.
I'm writing the documentation of a subroutine library where, du to the
number of routines,
all names are prefixed for easy grouping/finding.
There is an underline character in every name which does not look good
in pr
27 matches
Mail list logo
