Hi,
Am 14.10.2009 um 23:57 schrieb (Ted Harding):
The result of the above is that the number register \n[wnumber]
is set to 107659 which is the truncated value of the number of
"u" in 105.5*0.36mm namely 107659.8425197 (as shown by the value
of \*[wstring]), so you have lost precision to the ex
> Hello, in real world this is sooo easy:
>
> h = 105,5 mm
> w = h *0.36
>
> In groff world 105.5 and 0.36 needs to come in centimeters,
> then some correction needs to be applied.
Well, in the simple case above, 0.36 does *not* need to come in
centimeters. It is a simple numerical factor. The
> I am pretty stunned. It's not clear to me why current software has
> such crude limitations with one must circumvent with even more crude
> wordarounds.
TeX is even worse...
> What about enhancing groff and trowing out these limitations? At
> least in non-compatible mode there should be no pr
Hello Werner,
Am 15.10.2009 um 11:48 schrieb Werner LEMBERG:
I am pretty stunned. It's not clear to me why current software has
such crude limitations with one must circumvent with even more crude
wordarounds.
TeX is even worse...
Maybe, but the goal is to make it better and not to excuse
> Perhaps someone else will?
See? That's exactly the issue. Of course it's easy to say
"why do we have to put up with such crude limitations in
current software", but unless someone is pissed enough
to decide to fix it (or someone decides it's fun to do
something new), things stay as they are.
Am 15.10.2009 um 12:51 schrieb Tadziu Hoffmann:
See? That's exactly the issue. Of course it's easy to say
"why do we have to put up with such crude limitations in
current software", but unless someone is pissed enough
to decide to fix it (or someone decides it's fun to do
something new), thin
> First: I didn't want to offend anyone.
>
> I'm glad, groff is there and I like it very much. Contributing
> is good, and I would if, I'd be actually able to. To state this
> isn't a hollow phrase, I reworked the troff and groff-articles
> in the german wikipedia a time ago. This is not much but
Hello,
in the current form groff doesn't deal well with URL references for
bibliographic entries. There is no documented markup to specify a URL as
part of .Rs/.Re entries. .Lk doesn't behave properly as can be seen with
the timecounter(9) man page on NetBSD.
I propose to add a new macro .%U to al
Further to my previous post, first here is a revision of
the .PS and .PE macros in the 'ms' macro set which allow
the use of ".PS T" so as to (effectively) suppress any
effect on the printed page. It is assumed that no drawing
is done during a call to ".PS T <> .PE".
--8<-- cut here --
On 15/10/2009, at 11:50 PM, Tadziu Hoffmann wrote:
:
:
And I
believe the work everyone contributes to this list is well
appreciated.
This situation and attitudes towards groff is a lot more complex than
this.
In my professional life needed a lot of high level Math and graphics
ga
> Nevertheless I spent a few weeks on this integration thing and
> produced a longish report on what can be done and how, and gave an
> example. Graphics, far more complex than what you can hope from
> pic, embedded in groff. I haven't got a single answer, apart from
> the usual thing: this file
11 matches
Mail list logo
