[Groff] pspic: Text around picture?
Hello,
did anyone make an effort to enhance the pspic-macro, to
text flows around the picture, like that:
x
x
x +-+ xxx
x | | xxx
x | | xxx
x | | xxx
x | | xxx
x | | xxx
x +-+ xxx
x
x
x
x
Should be "fairly easy", if I'm right: pspic already
extracts and calculates things. In the simple case of left
or right-aligned pictures, we need to change indent (or page
offset?) and (only, for right-aligned) pictures the line
length and add a small margin (configurable? register?) for
a little space around the picture.
Ne also need to to suppress local vertical motion according
to the picture height, so text should run around the picture
just fine.
Next task would be more complicated: When do we need to
reset the po/indent/ll? Is there something like a "new line
trap" which gets called every new line? So pspic can hook
into that and if the vertical motion difference beween the
call of pspic and the actual position (add the margin men-
tioned before) is greater than the picture height, we can
reset the values to saved ones from before the pspic-call.
More tough things to do:
· Handle text around centered or indented pictures,
· Provide some mechanism to center a picture description
text under the picture (-L|-R|-I also) which also gets
added to the margin calculation ("makes picture taller"),
· Provide similar mechanisms for PICtures
Any help or advice would be appreciated. Thanks!
:wq! PoC
Re: [Groff] pspic: Text around picture?
Hello, Am 27.03.2009 um 21:44 schrieb Heinz-Jürgen Oertel: www.tmac provides this functionality partly. See man groff_www the .MPIMG description. Thanks for your kind answer. An internet browser does this wrapping itself, as soon as you add an align-Tag to the img src. This has nothing to do with groff. If you look into www.tmac, you can also see that this is using the pspic-macro, which doesn't provide the needed functionality. I'll have some tries with Werner's advices this weekend. :wq! PoC
Re: [Groff] pspic: Text around picture?
Hello Werner,
Am 27.03.2009 um 16:13 schrieb Werner LEMBERG:
AFAIK, no.
So, I'm again on the front ;-)
It's much simpler: Just set (vertical) traps at the end of the image
to reset the margins.
I didn't have the time to search the docs for that, but I had in mind
that there's some kind of trigger I could use. Thanks for the pointer!
A quick solution for an image which should appear exactly at the
position where it is inserted in the source is straightforward.
If the image fits onto the page, I see no problem with that.
It's far more complicated to do the same for floating images: Just
imagine
that an image no longer fits on the current page and has to be shifted
around...
You're right. Hm. Pspic simply leaves space. Consequently this is not
what I intend. This means, there has to be another "if" - the image
won't fit, pull it onto the next page.
· Handle text around centered or indented pictures,
Even TeX can't do this...
So that would be a huge plus for groff, won't it? ;-)
· Provide some mechanism to center a picture description text under
the picture (-L|-R|-I also) which also gets added to the margin
calculation ("makes picture taller"),
I don't really understand this. Please give an example.
x
x
x +-+ xxx
x | | xxx
x | | xxx
x | | xxx
x | | xxx
x | | xxx
x +-+ xxx
x pic1: foo xxx
x
x
x
· Provide similar mechanisms for PICtures
It's basically the same: Put the pic drawing into a diversion so that
its dimensions get calculated, which can then in turn be used to make
the text float around the image. However, there's the same problem as
with other images, namely, what to do if the pic drawing is larger
than the remaining space on the current page.
Could not be *that* hard, but I'm not really used to the groff
registers and many escapes around if's and calculations, which makes
me feel a bit handicapped ;-) AND I don't have a clue how to
accomplish that nicely (say: fairly readable in a normal document).
But that's and exercise for later. First, I'll stick with eps's.
Below is a first simple try which you could use to start with.
Thank you *very* much! It works basically, great! The picture gets
placed a bit too far to the right (exact the amount of space between
text and image on the left side of the image), I'll have a look into
that later.
May I ask how long you took to write that down?
:wq! PoC
Re: [Groff] pspic: Text around picture?
Hello, Am 28.03.2009 um 00:06 schrieb Werner LEMBERG: May I ask how long you took to write that down? Approximately 90 minutes, including the answer to your email. Thanks! I appreciate your help very much but unfortunately still didn't find time and free CPU-cycles inside my head to dig deeper into the issue. :-( It's on my ToDo-list. :wq! PoC
Re: [Groff] Integer arithmetic
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 extent of 1 in 107659 (which you can probably live with)! 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. What about enhancing groff and trowing out these limitations? At least in non-compatible mode there should be no problem, in compatible-mode the limitations could stay for people who rely on this limitations. Any comments? :wq! PoC
Re: [Groff] Integer arithmetic
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 limitations by pointing to other crap, stating "they're making it no better", right? ;-) What about enhancing groff and trowing out these limitations? At least in non-compatible mode there should be no problem, in compatible-mode the limitations could stay for people who rely on this limitations. Do you volunteer? I'd love to, but I'm not really good im programming, no clue of object oriented stuff. I still struggle with your code snippet for having text flowing around PSPIC-Imports. And, of course, time is a really limiting factor here. You might have a look at heirloom troff's implementation which already has such an extension; it makes absolutely no sense to program something differently. http://heirloom.sourceforge.net Perhaps someone else will? :wq! PoC
Re: [Groff] Integer arithmetic
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), things stay as they are. Remember, you get what you paid for. 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 I hope it proves that I also don't agree with the "anything for nothing" attitude, your last sentence might possibly impute to me. :wq! PoC
Re: [Groff] I am tired
Am 03.12.2009 um 10:19 schrieb Walter Alejandro Iglesias: 2) Is it too difficult to write my own macros for footnotes? Don't know but I won't bother reinventing the wheel. There are plenty of ready-made macro sets with footnote-ability. 3) In case I decide to use the ms, me, mom, etc. Which of them is the better solution to my needs (novel a4 paper)? If you're already experienced with LaTeX, perhaps mom fould fit you best. There's plenty of docs here: http://web.ncf.ca/fs222/mom/ mom-01.html I prefer "me" but mostly for historical reasons (I begun with me years ago and am too lazy to learn something new). Another good thing to look at would be ms. :wq! PoC
Re: [Groff] groff on Intel platform
Hello Miklos, Am 14.01.2010 um 07:57 schrieb Miklos Somogyi: My questions are: 1) Is there an intel version of groff at all? Groff has been with OS X at least since I use it (10.2) and it's still with 10.6, 1.19.2. 2) Anyone who went through of getting unix stuff and X under Snow any advice please? What exactly do you need/miss? There's groff, there's GNU textutils and there's vim. What else do you need? :-) :wq! PoC
Re: [Groff] gs and grops problems
Hello, Am 20.01.2010 um 13:13 schrieb Miklos Somogyi: - it seems that grops that came with 10.6.2 has a problem with any input: grops::4:fatal error: cannot create temporary file: No such file or directory I think it's a problem related to your latest post, where also some tempfiles could not get created. Please make sure, /tmp exists somehow and is writeable by you. With OS X, this is a symlink to /private/tmp, which in turn is a directory flagged 1777. :wq! PoC
Re: [Groff] pspic: Text around picture?
Hi Dan, Am 23.02.2010 um 21:47 schrieb Werner LEMBERG: Thank you for the nearly-one-year-old posting at http://www.mail-archive.com/groff@gnu.org/msg04603.html For many reasons I still didn't find the time to dig into the excellent example from Werner, so I can't give you advice yet. :wq! PoC
Re: [Groff] filled polygons in pic
Am 12.04.2010 um 04:31 schrieb Doug McIlroy: It it seems like a good idea, I might volunteer to try to do it right. From my point of view, it absolutely makes sense. I also missed polys from time to time. :wq! PoC
Re: [Groff] How to include a letterhead
Hi Chris, Am 08.10.2010 um 08:12 schrieb Chris Velevitch: I'm trying to create a pdf with full page letterhead. When I do:- cat
Re: [Groff] Inline Images
Am 16.10.2010 um 18:45 schrieb Paul O'Leary McCann: Is there any standard way of putting images inline? Sparklines aren't what I had in mind, but they're an example of the sort of thing I'd like to be able to do. Did you take a look at the PIC-Documentation? It's rather versatile! :wq! PoC
Re: [Groff] labelling and referring
Am 29.11.2010 um 15:23 schrieb Tim23: Is it possible to label equations or tables to refer to them from anywhere in a text? Yes, for equations this is possible. See the documentation for the .EQ- request to use equation numbering. For tables you have to build something yourself. Example: .\" Define Register TN with an autoincrement-Value of 1. .nr TN 0 1 And for numbering tables: .(b .TS .TE .sz -2 .ce 1 Table \n+(TN: Foo Bar .sz .)b (I'm using me macros, so adjust to your needs) :wq! PoC
Re: [Groff] labelling and referring
Am 29.11.2010 um 21:14 schrieb (Ted Harding): As well as using the auto-increment mechanism to create successive table/equation numbers automatically, it is also useful to be able to cross-reference them later in the text. Thanks ted, this is a nice extension to the standard-numbering- mechanisms! Very helpful! :wq! PoC
[Groff] Refer and mysterious comma
Hello, I want to use refer for what it's been written. :-) But I'm stumbling over some things which I can't explain nor solve. I'm using me-macros with Groff 1.19.2 which I tried to package for debian lenny a while ago (I was missing the Euro-Glyph) in the standard-version. Given it's input: .R1 database references.txt accumulate join-authors " und " ", " " und " move-punctuation .R2 Blabla, some paragraph with a citation. .[ Barkhausen Grundlagen .] More text to follow, more footnotes, usw. Lorem Ipsum and stuff. .[ $LIST$ .] The database "references.txt" is indexed via indxbib and contains the referenced entry like that: %A Dr. Heinrich Barkhausen %B Allgemeine Grundlagen %I Verlag S. Hirzel %C Leipzig %D 1937 %S Lehrbuch der Elektronen-Röhren und ihrer technischen Anwendungen %V Erster Band %Y 4. Auflage The output of groff -ww -me -ma4 -mgerman -Retp for the input file is attached as screenshot. As you can see, between the author (%A) and title (%B), there is some strange quote-comma-quote. I have no idea where it comes from. I removed join-authors from the refer-flags (which I used to get german strings) but that doesn't make any difference. Additionally after the Author is also a comma which is (at least in german) not right. How can I get rid of these two things? Any ideas? Thanks for help! :wq! PoC <>
Re: [Groff] Refer and mysterious comma
Hi Tadziu, Am 04.12.2010 um 21:07 schrieb Tadziu Hoffmann: [...] But I'm stumbling over some things which I can't explain nor solve. As you can see, between the author (%A) and title (%B), there is some strange quote-comma-quote. It appears to be a bug in -me. With -ms it works perfectly. Thanks for the checking! That seems to be the reason for many errors while groff runs, just like these: infile.me:958: warning: macro `(f' not defined infile.me:958: warning: macro `[T' not defined infile.me:958: warning: macro `[P' not defined infile.me:958: warning: macro `[O' not defined infile.me:958: warning: macro `)f' not defined infile.me:971: warning: macro `[T' not defined infile.me:971: warning: macro `[P' not defined infile.me:971: warning: macro `[O' not defined infile.me:983: warning: macro `[T' not defined infile.me:983: warning: macro `[E' not defined How can I assist in solving this? :wq! PoC
Re: [Groff] pspic: Text around picture?
Am 03.04.2009 um 18:10 schrieb Denis M. Wilson: Centre hole in text macro fixed. See http://www.oxytropis.plus.com/groff/markup-1.0.1.tar.gz Seems to have increased to 1.0.6. :-) :wq! PoC
Re: [Groff] pspic: Text around picture? (Resent without attachment)
Hello Werner, Am 27.12.2010 um 09:12 schrieb Werner LEMBERG: Does anyone want to help me in fixing remaining issues (and perhaps enable this one to go into some future version of groff itself)? I'll try, however, I can't promise that I have enough time. Thank you very much for your efforts. That's why I didn't ask especially you, since you already stated you're short on spare time. First: grofftest.me:68: warning: missing `)' (got newline) grofftest.me:68: warning: missing `)' (got newline) That's, when rfloat is called: .rfloat PM84.eps 1i Please provide grofftest.me (or rather, a minimal example which exhibits your problems). Archive of all neccessary files be accessed via http://www.pocnet.net/~poc/grofftest.tar.gz (about 1M). Message was rejected from the mailing list software for being too big :-) :wq! PoC
Re: [Groff] Refer and mysterious comma
Hi Tadziu,
Am 30.12.2010 um 21:36 schrieb Tadziu Hoffmann:
- space between %D and a following comma from %P.
- space before the full stop when %P is not used.
try following the date with a "\c", too:
\\*([D\c
Thanks very much for that! With your explanation regarding \c, it's
now clear how this works out!
For aesthetics you might also want something like
.if !"\\*([P"" \{.tr -\(en
, S. \\*([P\c
.tr -- \}
if you have page ranges specified as "78-85".
Thanks also. I incorporated this but since I'm only providing start
pages, it's of no use for me.
Werner, any Ideas if and how to integrate this "fix" into e.tmac? I
can provide diffs so at least the english version will work out right.
Any ideas how to provide proper german refer support (if that is
wanted within groff)?
:wq! PoC
Re: [Groff] pspic: Text around picture?
Hi Werner, Am 02.01.2011 um 09:16 schrieb Werner LEMBERG: In rfloat.tmac need to take environment attributes into account. For example line length (this works for raw troff without a macro package): Thank you VERY much!! Unfortunately, the space between text and output is gone, now. May I ask again for aid? This is a bug (or feature?) in -me: It internally redefines .ll to be a macro, accepting only a single argument. Below an updated version. Thank you VERY much, Werner! Works like a charm and the errors are gone, also. :wq! PoC
[Groff] eqn: sqrt looks ugly
Hello,
am I doing something wrong or did I find a bug?
Input:
.EQ
y = sqrt x
.EN
.EQ
y = sqrt { x a b c }
.EN
Processed with:
groff -me -ma4 -mgerman -e eqn.me |ps2pdf - ~/eqn.pdf
Using groff 1.19.2.
Output see screenshot and attached PDF. The line above the sqrt-sign
seems to start about one em left to the place it should start.
Any hints on that?
:wq! PoC
<>
eqn.pdf
Description: Adobe PDF document
Re: [Groff] Refer and mysterious comma
Hello,
Am 05.12.2010 um 01:04 schrieb Tadziu Hoffmann:
These are not critical. They occur because -me "clears" all
relevant strings before formatting a new reference, and groff
warns you if you try to remove a string or macro that doesn't
exist.
Perhaps this now broken with the new macro? I can see that the
reference string for %S is now output everytime after the first
reference has been placed in the text which is using %S.
Placing empty %S statements into the reference file doesn't change
anything. Seems that %S won't be cleared between individual reference
outputs. I can only observe this with %S but can't find any obvious
reason.
I'm using this definition:
.\" Redefine "article-in-book" references macro
.de [3
.(f
.ip "\\*([F.\0"
\\*([A\c
.if !"\\*([T"" , \\f2\\*([T\\f1\c
in \\f2\\*([B\\f1\c
.if !"\\*([S"" , \\*([S\c
.if !"\\*([V"" , Band \\*([V\c
.if !"\\*([E"" , bearb. \\*([E\c
.if !"\\*([I"" , \\*([I\c
.if !"\\*([C"" , \\*([C\c
\\*([D\c
.if !"\\*([P"" \{.tr -\(en
, S. \\*([P\c
.tr -- \}
.if !"\\*([O"" \\*([O
.)f
..
Any hints on that? Thank you!
:wq! PoC
Re: [Groff] eqn: sqrt looks ugly
Hi, thanks to everyone who responded. Am 15.01.2011 um 15:52 schrieb Werner LEMBERG: Something is probably broken with your installation. I suspict something with my fonts. Sigh. Btw, transferring the resulting PostScript file to my OS X box and converting that with the OS' tools reveals the following output from the described input. Again, thanks! :wq! PoC <>
Re: [Groff] Refer and mysterious comma
Am 15.01.2011 um 20:52 schrieb Tadziu Hoffmann: Perhaps this now broken with the new macro? I can see that the reference string for %S is now output everytime after the first reference has been placed in the text which is using %S. I guess you need to add "[S" to the stuff to be removed in "]-". May I again ask for further explanation, please? I can't find a closing bracket in the macro. :wq! PoC
Re: [Groff] Refer and mysterious comma
Hi Tadziu, Am 16.01.2011 um 00:29 schrieb Tadziu Hoffmann: It's the "]-" macro which prepares for a new reference by removing all the reference-related strings (which may have been set by the previous reference), but in e.tmac "[S" is missing from the list of string names in the definition of the macro "]-" (this is obviously a bug). Again, thank you very much! I circumvented this my having .am ]- .rm [S .. in my document and it works. Werner, need a patch for that? :wq! PoC
Re: [Groff] tbl and large font
Am 19.01.2011 um 17:00 schrieb walter harms: this works much better. Is there any reason why changing the font should not change the baseline also ? In fact, it does. But perhaps only within a certain range of sizes and -main reason- in normal text mode which is perhaps not sufficient for tbl. :wq! PoC
[Groff] Readymade Deb-Packages for groff 1.21
Hello, anyone made debian-packages for lenny of groff 1.21? I'm struggling with makefile-hardcoded pathes for xditview and other glitches. :wq! PoC
Re: [Groff] Refer and mysterious comma
Am 16.01.2011 um 11:11 schrieb Werner LEMBERG: Werner, need a patch for that? For -me? Yes, please. Here, please. This is for groff 1.19.2! Hope it applies cleanly to 1.21. :wq! PoC e.tmac.patch Description: Binary data
Re: [Groff] Refer and mysterious comma
Hello Werner, Am 23.01.2011 um 15:51 schrieb Werner LEMBERG: Here, please. This is for groff 1.19.2! Hope it applies cleanly to 1.21. Thanks! Unfortunately, I believe that there are some errors in your patch: Hm, this is interesting, since for me it works. I proposed a localized german version but since you wanted a patch, I redid Tadzius proposals and fixed the last glitches. to typeset the title with italics. Why? To be honest: Because I could. :-) It's a basic design decision of the -me macros to use quotes, and I don't want to change this default. OK. I didn't want to offend with this. Sorry for being so careless. For your other thoughts: I understand to some extend but not completely. I'm sorry. See below. Now that I've looked into the details more closely, I could fix all of this by myself. Thanks. However, I think it's a good idea to make *you* learn to fix it correctly :-) To be honest, I really tried, also with your rfloat proposal but it seems I'm just not programmer enough to decode the many backlashes, asterisks, braces and often single characters into something meaningful to me without investing ten times more time someone seasoned would need. Not to mention to fix eventual errors, translate back (and introduce new errors). Sorry. I'll never be more than an ordinary user, I think. Finally, I ask you to provide a proper ChangeLog entry. I don't think that I should get credits for something proposed by Tadziu and fixed by yourself eventually. :wq! PoC
Re: [Groff] Refer and mysterious comma
Am 23.01.2011 um 18:22 schrieb Werner LEMBERG: But what you provided is not a localized German version... Yes. Look into my first mail from Jan. 15. To be honest, I really tried, also with your rfloat proposal but it seems I'm just not programmer enough to decode the many backlashes, [...] OK, then I'll continue, preparing a patch which I ask you to test. Can do. Anyway, thanks for your efforts! Thanks for your patience! :wq! PoC
Re: [Groff] Problem with -me package
Hello Werner, Am 14.02.2011 um 09:27 schrieb Werner LEMBERG: Corrected version attached. Thanks! In the CVS, I've heavily modified your patch. Please check. Sorry for the delay. I checked. The refer-stuff is still in english language, even when using -mde. Using e, refer-me and refer from CVS for groff 1.20.1 (which is bundled with Debian Squeeze), groff emits a: warning: tab character in unquoted macro argument Everytime I'm switching from .2c back to .1c. Besides that, I can't see any problems yet. :wq! PoC
Re: [Groff] Problem with -me package
Hello Werner, Am 23.02.2011 um 10:56 schrieb Werner LEMBERG: Sorry for the delay. I checked. The refer-stuff is still in english language, even when using -mde. Yes, of course, since only English has been implemented. Ah, that wasn't obvious. I'm awaiting your patches which should now be much simpler. :-) Hope I do get it right this time. Please be patient. Using e, refer-me and refer from CVS for groff 1.20.1 (which is bundled with Debian Squeeze), groff emits a: warning: tab character in unquoted macro argument Everytime I'm switching from .2c back to .1c. Sample code, please. Looks like a harmless message, I believe, but fixing it would be better. See attachment. Command line: groff -ww -me -ma4 lipsum.me > lipsum.ps Thank you! :wq! PoC lipsum.me Description: Binary data
[Groff] Initials: Help appreciated
Hello, has anyone done a macro for initials yet? I tried to do it inline to learn but I fail: The jumpback doesn't work for me. Even .sp -1v won't work. I get many warnings about "cannot adjust line" and I only see the initial (word) and two empty pages. Last thing I don't know to handle is: How to determine when to reset the indent. .\" Height of the initial in lines .nr IH 2 .\" Set pointsize to a multiple of pointsize and spacing .\" and add extra spacing .sz \n(psu+\n(ssu*\n(IHu-\n(ssu Lorem .\" Set indent to the width of the inital, .\" add 2n extra space afterwards .in +\w'Lorem'+2n .\" Jump back one line of the current (big) pointsize \v'-\n(psu' .\" reset pointsize so text can continue .sz ipsum dolor sit amet, consectetur adipiscing elit. Ut dapibus velit non neque consectetur adipiscing. Sed accumsan, augue in eleifend consequat, tellus neque pulvinar libero, accumsan vehicula mauris ante sit amet tellus. Aenean tincidunt ultrices diam. Mauris ut tellus in lorem auctor dignissim. Morbi lobortis rhoncus cursus. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Call with groff -me -ma4. Any help is greatly appreciated! :wq! PoC
Re: [Groff] Problem with -me package
Hello Werner, Am 23.02.2011 um 18:06 schrieb Werner LEMBERG: I get no warning with current CVS. It seems that this has been fixed meanwhile. OK, thanks for checking! :wq! PoC
Re: [Groff] Initials: Help appreciated
Hello Ralph, Am 23.02.2011 um 14:43 schrieb Ralph Corderoy: Hi Patrick, without c, please. :-) Thanks. Have a look at the subject "YaDCM (Yet another Drop Capital Macro)" in the archive around 2005-03 and 2005-04. That may help. http://lists.gnu.org/archive/html/groff/2005-03/threads.html Thanks for the char *URL; I used the "final" Version by Werner, posted in http://lists.gnu.org/archive/html/groff/2005-03/msg00133.html Input: .dropcap Lorem darkblue 3 T 0 ipsum dolor sit amet, consectetur adipiscing elit. Ut dapibus velit non neque consectetur adipiscing. Sed accumsan, augue in eleifend consequat, tellus Call: groff -me -ma4 -mdropcap I get the following errors: dropcap.me:1: warning: numeric expression expected (got `d') dropcap.me:1: warning: can't find font `0R' dropcap.me:1: warning: can't find font `T' I'll see if I can find out what's going wrong here. :wq! PoC initaltest.pdf Description: Adobe PDF document
Re: [Groff] Initials: Help appreciated
Hello Deri, Am 23.02.2011 um 20:10 schrieb Deri James: This worked for me:- .dropcap Lorem 3 blue TR T 0 (Note the order of parameters). Unfortunately the parameters aren't explained, so I made a mistake. Sorry and thank you!! :wq! PoC
Re: [Groff] Initials: Help appreciated
Hello Peter, Am 23.02.2011 um 18:58 schrieb Peter Schaffter: The mom macros have a fairly sophisticated dropcap mechanism based on the number of lines to drop the cap plus the cap-height of running text. You might want to study it for ideas. Thank you! May I ask for a hint, for which command to look? Can't find anything in the docs on the first look. :wq! PoC
Re: [Groff] table column spacing
Am 07.04.2011 um 13:43 schrieb Ruud Baart: > In a table the column with can be defined by: w,WMinimal column width > value. But there is also some space from left cell boundary to cell content > and from the right side of the cell content to cell boundary. Sometimes, if > the table is too full, this space between cell content and cell boundary is > set to zero. > > Can this spacing between cell content and cell boundary be controlled with > parameters? Yes. Space between columns — A number may follow the key-letter. This indicates the amount of separation between this column and the next column. The number normally specifies the separation in ens*. If the ‘‘expand’’ option is used, then these numbers are multiplied by a constant such that the table is as wide as the current line length. The default column separation number is 3. If the separation is changed the worst case (largest space requested) governs. (Taken from tbl.pdf) :wq! PoC
Re: [Groff] table column spacing
Am 07.04.2011 um 16:04 schrieb Ruud Baart: Thanks, that works. I can't imagine that I missed it in the documentation for so many years. It brings me to an other question. Can the value be set for a whole document? The default value of 3 is quite some space. Probably a register setting? I don't think so, but I can't prove. Pic carries variables between multiple calls of .PS in some register, but within tbl, you explicitly have to give this number as part of the table format instructions, column by column. I can't remember finding anything in the docs for that, so I think it's hardcoded. :wq! PoC
Re: [Groff] man/troff to LaTex?
Am 04.08.2011 um 17:24 schrieb steve.gnuli...@gmail.com: Is there a way to convert a man source to a LaTex typesetting? I don't know of anything readymade. LaTeX and Groff have a distinct goal but differ in many ways. Such a program would be very complex and time-consuming to write. Think of something which converts C source to Pascal. (Besides, AFAIR p2c exists.) To probably help you: What do you want to accomplish? If you want to convert just one document once, it could be time saving to create it from scratch in LaTeX. :wq! PoC
Re: [Groff] eqn: sqrt problems
Hello Denis, Am 02.09.2011 um 13:22 schrieb Denis M. Wilson: What do people think? At first THANK YOU! I also suffer from this problem an I suspicted some font-related problem, too. Interestingly, the problem only arises when generating PDF files from the resulting Groff-PostScript. Sending the PS-Output directly to a PostScript Printer yields the desired result for me. :wq! PoC
Re: [Groff] help with refer
Hello Heinz-Jürgen, Am 12.12.2011 um 14:58 schrieb Heinz-Jürgen Oertel: if someone has a small example document using the ms macros and refer, I'm sure it will help me understand the usage. Unfortunately I can only provide a me-Example (which should not differ from ms). .\" Reference-defines for the whole document placed atop .R1 database references.txt accumulate join-authors " und " ", " " und " move-punctuation .R2 .\" This is an entry which sets a reference entry based on .\" the given words according to the entries in the database. .\" It causes no break and will appear just like a footnote. .[ Jager Television Receiver Valves .] .\" This is the end of the document. Print out the referred database entries .[ $LIST$ .] When changing the references.txt, I run indxbib references.txt to get a proper index. In fact, I don't remember if this is mandatory or optional. Also you have to add -R to the groff commandline, so refer actually gets called as another preprocessor. Hope that helps! :wq! PoC
Re: [Groff] Fancier placement of PSPICs?
Am 07.03.2012 um 13:08 schrieb Cedric Sodhi: Are there way to generally place an image different from filling a whole page width? By generically I mean doing so by using PSPIC and without particular knowledge of the sourrounding text and the image's dimension. By differently I mean, for example, float the image in the text, put multiple images into the same line, etc. I'm trying to get multiple images into one line and also have text flow arround a floating image. Do I have to write my own version of PSPIC for something like that? Please search in the list archive 2010 for the subject "pspic: Text around picture". I had a similar question and it's quite hard to entirely do it yourself if you're not used to the sometimes cryptic outlook of pure troff code. However, Werner Lemberg came up with a solution to build upon (rfloat). Unfortunately, I didn't have the nerves to dig down into the code yet. The picture is placed a bit too much to the right, the same amount as spacing between text and picture. Hope this helps. Again, big thanks to Werner for a starting point for floating text around pictures (and perhaps more objects, like PIC to come)! :wq! PoC
Re: [Groff] Trouble with mm
Hello Cedric, Am 17.04.2012 um 12:30 schrieb Cedric Sodhi: me on the other hand appears to be rather complicated and I seem not to find a documentation describing me as a whole. Regarding documentation: This is clearly not true. Complicated: Depends what you expect and are used to. :-) Manpage groff_me (7) exists. Additionally, there are formatted files which I used for my own education: /usr/share/doc/groff/meintro.me.gz /usr/share/doc/groff/meintro.ps.gz /usr/share/doc/groff/meintro.txt.gz /usr/share/doc/groff/meref.me.gz /usr/share/doc/groff/meref.ps.gz /usr/share/doc/groff/meref.txt.gz Btw. in the same doc-Folder, there's also formatted documentation about tbl, pic, and eqn. Me was my choice especially *because* it has (at least to myself) excellent documentation. :wq! PoC
Re: [Groff] Wrapping Text Arond Figures and Captions
Hi Frank, Am 23.01.2013 um 22:53 schrieb Frank Jahnke: > I would like to revisit a topic that has come up from time to time over > the years but really has not been solved. That is wrapping text around > figures and their captions. Yes, I am still aware of this topic and it still has a place on my long term ToDo-List. Werner's Macro should be seen as a starter for own optimizing and extending. I'm very grateful for this start, even if my time doesn't permit tinkering with this topic for a long time now. (Werner: Thanks, again, repeatedly!) I'm also not able to do groff coding myself. But I'm pretty sure that there will be no-one who fixes Werner's starter except people who want to solve this problem for themselves and are willing to learn enough of groffs gores to get it done. Last question is: Who gets it done first? ;-) :wq! PoC
