Dear All,
in a follow-up to myself:
If I understood where the whole .1C definition ends, I could copy that
block into an own macro definition and from there eliminate just those
commands which flush the old page and begin a new page. I could even
ignore the tests for floats and footnotes because
Another follow-up:
I just checked the one-column mode across the macro packages ms, me and
mm, and lo and behold, the mm man page tells me:
1C [1] Begin one-column processing. A 1 as an argument disables
the page break. Use wide footnotes, small foot‐
notes may be overprinted
olumns, so I have to insert a break
manually.
This should now be an obstacle of minor concern.
Best regards,
Oliver.
On 20/11/2023 21:04, Oliver Corff via wrote:
Another follow-up:
I just checked the one-column mode across the macro packages ms, me and
mm, and lo and behold, the mm man pag
lumn mode
.1C 1
.TS
.\" Your wide table here
.TE
.\" And back to two-column mode.
.2C
Rest of the text
On 20/11/2023 21:04, Oliver Corff via wrote:
Another follow-up:
I just checked the one-column mode across the macro packages ms, me and
mm, and lo and behold, the mm man page tells me:
Dear All,
while experimenting with the mm macro package for the first time I
noticed that from the very start it did not behave exactly as expected
--- which was entirely due to my lacking of understanding of some basics.
Starting a text without any macro yields just a page flooded with text
---
21T13:37:13+0100, Oliver Corff via wrote:
while experimenting with the mm macro package for the first time I
noticed that from the very start it did not behave exactly as expected
--- which was entirely due to my lacking of understanding of some
basics.
Before digging into the details of your me
Dear Branden,
thank you very much for the answer!
The journal title can be repeated in the page header. The original
document happens do to it, too, and thus this is a perfect solution for
my particular case.
I get it: the .AF points to the company or institution publishing the
document, unlike
Hi Branden,
I get *your* point, but I was lured to believe that I could write my own
Memorandum Type by copying an existing one in the ../tmac/mm/ directory
and assigning an appropriate number. I thought "types 0 to 5 are
supported" can be interpreted as "a file for these types is provided",
whic
Hi Branden,
thank you for your quick response!
I had just hit the send button, and the bell rang --- I saw T. Kurt
Bond's incoming mail. What a coincidence.
On 18/12/2023 22:07, G. Branden Robinson wrote:
Hi Oliver,
At 2023-12-18T21:57:07+0100, Oliver Corff wrote:
Enter groff 1.23.0. I compi
Hi Alexis,
I admit that the source files of the whole groff system have a structure
that in theory allows for apparently easy modifications, but this is not
what they are meant to be. The transparent source code is not an
invitation to edit.
Your modifications, in themselves, are plausible, but
Hi Tom,
བཀྲ་ཤིས་བདེ་ལེགས
have you tried the font TibMachUni-1.901b.ttf? It is available via
package manager e.g. in Fedora 39.
Can post a source file for your examples, please? I may try in tomorrow.
Best regards,
Oliver.
On 21/01/2024 00:09, Tom wrote:
Hi,
I did typeset few books in Heir
Hi Tom,
བཀྲ་ཤིས་བདེ་ལེགས།
(sorry, I forgot the shad)
have you tried the font TibMachUni-1.901b.ttf? It is available via
package manager e.g. in Fedora 39.
Can post a source file for your examples, please? I may try in tomorrow.
Best regards,
Oliver.
On 21/01/2024 00:09, Tom wrote:
Hi,
I
hen I
can dig deeper into the ligature problem.
Best regards,
Oliver.
On 21/01/2024 18:48, Deri wrote:
On Sunday, 21 January 2024 00:28:42 GMT Oliver Corff via wrote:
Hi Tom,
བཀྲ་ཤིས་བདེ་ལེགས།
(sorry, I forgot the shad)
have you tried the font TibMachUni-1.901b.ttf? It is available via
pac
t the source code of your trial file? Then
I can dig deeper into the ligature problem.
Best regards,
Oliver.
On 21/01/2024 18:48, Deri wrote:
On Sunday, 21 January 2024 00:28:42 GMT Oliver Corff via wrote:
Hi Tom,
བཀྲ་ཤིས་བདེ་ལེགས།
(sorry, I forgot the shad)
have you tried the font Tib
Hi,
Deri already followed up the conversation that was prompted by Tom's
questions regarding Tibetan.
I'll attempt to steer the conversation away from Tibetan towards a more
generic technical issue: processing ligatures (that's what Tom's
problems boil down to).
If we take the Tibetan syllable
/interpolations are very
powerful in groff, certainly powerful enough to solve the Tibetan
ligature problem.
I'll inspect the font description files, thank you for the hint.
Best regards,
Oliver.
On 22/01/2024 02:47, Dave Kemper wrote:
On 1/21/24, Oliver Corff via wrote:
Now the question whi
Hi Tom,
last time, I already mentioned that e.g. the terminal has no problems
creating mandatory ligatures with a regular Tibetan font.
I did not forget the issue, I am just under pressure to deliver work
bound by a deadline, which will be another fortnight from now.
Best regards,
Oliver.
On
Hi Deri,
just as Peter said: this news just unmade my day.
My contributions to groff are tiny, I am just an avid user who follows
groff development with great interest but little of own competence for
substantial contributions. All the more I appreciate the work you have
been making with groff a
Dear All,
recently I compiled, and re-compiled, and again recompiled a set of
various documents with different tables, equations etc.. For each of the
documents, the precise requirements of preprocessors were different, and
more often than not, I forgot to set the appropriate groff option when
ru
orff wrote:
Hi Lennart,
I constantly ignore this trap due to my less-than-frequent postings.
Thank you for pointing out this one.
Best,
Oliver.
On 22/03/2024 22:26, Lennart Jablonka wrote:
Quoth Oliver Corff via:
Reply-to: Oliver Corff
This might not be the greatest of ideas. An MUA
Hi Branden,
thank you very much for this effort. One question: the appearance of
your reconstruction is slightly different from the original. Your lines
contain approx. 10% more characters, in result a 10-line paragraph in
the original text is about 9 lines long in the reconstruction. May I
assum
Hi Branden,
On 12/06/2024 18:22, G. Branden Robinson wrote:
Hi Oliver & Larry,
At 2024-06-12T17:02:22+0200, Oliver Corff via wrote:
thank you very much for this effort.
My pleasure--if I can call it a pleasure to discover defects in groff's
mm package scrambling out like roaches
Hi Tomek,
the Tibetan font isssue is a difficult nut to crack, for two main reasons:
- the groff font tables do not contain information provided by the
ligature mechanism of Truetype or Opentype fonts
- groff itself is only set up ("hard wired") for a small number of
conventional ligatures used
Hi,
in my humble opinion, a solution to your problem (if I understood it
correctly) already exists. Perhaps a good starting point for writing
useful macros which output the desired text according to language is the
macro repository of groff.
Check, e.g. the macro files trans.tmac, de.tmac, sv.tm
Hi Dave,
thank you very much for pointing out the usefulness of units!
Adding the "u" did the trick.
The simple macro
.de hline
\l'\n[LL]u'
..
.hline
now does the trick, the line length is exactly the same es the text line
length, no problems with truncated divisions anymore.
Best,
Oliver.
Dear All,
Recently I started using groff for writing business letters. In my
particular case, I experimented with the macro package me following the
example letter I found in the documentationm, but my question is not
linked to the choice of any particular macro package.
In me, adding a footer w
Dear All,
I was in search of the macros for writing indented and bulleted lists.
While groff_mm contains the macro BL which is explained as "Begin
bulleted list" and groff_me has "(l begin list" and ")l end list", I was
a bit baffled how groff_ms successfully hides its list feature from the
user:
lics) in string
definitions without any difficulty.
Best regards,
Oliver.
On 09/11/2024 20:34, Bento Borges Schirmer wrote:
Hey Oliver,
Em sex., 8 de nov. de 2024 às 19:05, Oliver Corff via GNU roff
typesetting system discussion escreveu:
Check, e.g. the macro files trans.tmac, de.tmac, sv.tmac, c
Dear Norwid,
I am overwhelmed by your response to my Saturday afternoon roff
exercise! Thank you for your copious feedback, also with regard mhchem,
etc. I installed IQmol on my computer to explore the field a bit
further. Besides that, there is quite a zoo of chemical notations! Of
which I was b
Hi Robert,
Thank you for your points. I get your idea.
Of course it is a salient approach to have perl, bash etc. loop through
some prompt and readline statements in order to produce the static roff
file that can then be compiled into an elegant invoice.
Consider my idea not to be a pursuit of
Hi Ingo,
thank you very much for your response!
I didn't have a *thorough* look at mom yet, it seems to have a dedicated
presentation mode, I'll study that and I'll certainly inspect the
multi-column feature.
In addition, I'll also have a look at gpresent. There is more than one
way to Rome;-)
Hi onf,
thank you for your example! I'll try it during the next days.
Yes, I am aware of looming complexity issues but I regard this as an
exercise only. I do not want to bulldoze my way forward if it is really
not practical, etc. Let's reword my approach: I only want to see if the
idea is *poss
32 matches
Mail list logo
