G. Branden Robinson, just quick commentincle on this:
> So if "adjustment" is, as I claim, "the widening of
> the spaces between words until glyphs abut both the
> left and right margins", well, that's clearly not hap-
> pening here.
No, it is not. What you describe is "both" adjustment,
G. Branden Robinson:
> People frequently run into trouble because they usually
> don't want the text of function prototypes filled, but the
> prototypes can also get lengthy, and they don't know how
> to make the text adapt to the available terminal width in
> the absence of filling. (Short answe
G. Branden Robinson to Anton Shepelev:
> > This means that one must /set/ rather than unset
> > GROFF_SGR to restore the normal nroff behavior.
>
> This advice, while still applicable to groff 1.22.4, is
> becoming stale. Distributors that introduced the
> GROFF_SGR Debia
Hello, all
What is the covenstional way of documenting a set of C
functions with -man? Have you any recommendations or
examples about typesetting function declaraions, their
return types and aruguments in a classic man-page? The .SY
macro does not seem to work well for C, because its function
de
Anton Shepelev wrote to G. Branden Robinson:
> > Check your environment for variables named "GROFF_SGR"
> > (a Debianism) and "GROFF_NO_SGR". Unset them both and
> > try "groff -man -Tutf8" again.
>
> `export | grep -i sgr' finds nothin
Jim Hall:
> Several weeks ago, I interviewed Dr. Marshall Kirk
> McKusick about how he writes his books using groff:
> https://technicallywewrite.com/2023/10/13/groffbooks
McKusick writes about orphan elimination, end-of-
line tweaking, and balancing of text on facing
pages. Does that
G. Branden Robinson to Anton Shepelev:
> > I wonder what Debian user or developer dis-
> > liked those SGR sequences emitted by groff...
>
> Well, here's one of them.
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312935
>
> ...with my leng
G. Branden Robinson to Anton Shepelev:
> > `export | grep -i sgr' finds nothing, unfortu-
> > nately. Where else can I look for the reason of
> > -man treating my virtual terminal as a printer?
> > Once I find it, I will bring it up with the ad-
> > minis
. Branden Robinson to Anton Shepelev:
> > instead of using ANSI control codes, and this has no
> > intended effect. How can I cause `-man -Tutf8' to use
> > ANSI codes?
>
> Check your environment for variables named "GROFF_SGR" (a
> Debianism) and "GROFF_
Hello, all
`groff -man -Tutf8' does not seem to handle font
styles on my terminal. I have made sure that plain
`groff' works as expected:
This is
.ft B
strange
.ft R
indeed.
Damian McGuckin to Anton Shepelev:
> As you noticed, that 1.22.4 version of '-mm' solved the
> fill-mode problem with '.DS'.
>
> However, when you use
>
>.DS 1
>.EQ (X)
>... equation
>.EN
>.DE
>
> it places put the
Damian McGuckin:
> The bug is that while
>
> .DS 1
>
> uses the standard indent,
>
> .DS 1 1
>
> does NOT use the standard indent.
Let us maybe share some examples of a) the current
and b) the expected behavior. This e-mail is for-
matted using mm, w
Damian McGuckin:
> I went back to a very old document using troff and
> MM. It is a tutorial on using troff at the macro
> package level without needing to know much about
> the low level troff. I was contemplating updating
> it and putting it out there.
>
> I am trying to use a display wi
Damian McGuckin:
> I went back to a very old document using troff and
> MM. It is a tutorial on using troff at the macro
> package level without needing to know much about
> the low level troff. I was contemplating updating
> it and putting it out there.
>
> I am trying to use a display wi
I wrote seven years ago:
> OK, I have modified the patch (attached).
>
> But I am not sure how mm is supposed to handle
> long signatures if they spread across the page
> boundary: should it treat the .FC + .SG combina-
> tion as an indivisible keep or not, e.t.c.; so I
> did it the si
hj.oertel:
> by default groff generates PS, using the flag
> -Tps. In Linux you can convert it to PDF using
> the ps2pdf tool.
Ditto on Windows, just install Ghostscript for this
OS: http://ghostscript.com/download/gsdnld.html .
--
() ascii ribbon campaign - against html e-mail
/\ h
Peter Schaffter:
> Werner, you have fulfilled the role perfectly, and
> I know I speak for everyone on the list when I say
> you have earned not only our respect, but our ad-
> miration. Being a lead developer entails qauli-
> ties that go far beyond coding skills, not the
> least of which
Hello all,
I should like to typeset em dashes surrounded by
thin, say 1/4th en, spaces. To prevent a dash from
starting a new line, the first space must be un-
breakable. The second one must be discardable.
Both spaces must be unstretchable. How to do it?
The '\h' describption re
Tadziu Hoffmann:
> Thanks! Out of curiosity, I just ordered a used
> copy.
You should not have hurried:
http://www.gpo.gov/fdsys/pkg/GPO-STYLEMANUAL-2008/pdf/GPO-STYLEMANUAL-2008.pdf
> The book costs 12 Euros, and shipping from Aus-
> tralia costs 18 Euros. :-|
I had to order Clarke E
Jerome Frgacic:
> Here is the context : I'm student in Law and next
> year I will have to write a memorandum. Neverthe-
> less, this memorandum must be in MS Word format
> which displease me greatly. This format is im-
> posed to verify if we respect the instructions,
> and especially
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...
-
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
trebol:
> I've seen that hyphenation in mail is a bad idea.
Then justified text is the same in that it makes re-
formatting difficult.
> No other way to prevent multiple pages to .pl
> 1000?
Another way would be to set up transparent page
breaking, i.e. zero vertical margins, no keep
trebol:
>Thanks Aton.I think it's good that the
> hyphenation character is independent of the rest
> of the glyph's assigna- tions. For now I'll let
> you rest of my newbie's questions, and I will con-
> tinue studying how groff works. But I think in
> a short time I'm go
trebol:
> [...] so I'm going to follow the Anton's advise.
I see you are still having \(hy as the hyphenation
character. You can specify a different character,
the ASCII '-' for example, in unicode.tmac or else-
where using the .shc request:
.shc -
--
() ascii ribbon campaign - agains
trebol:
> > > I can use -Tascii, but as you may have no-
> > > ticed, I'm not a English speaker, so I need
> > > send utf8 mail, and formating with groff makes
> > > the work easy. Any advice?
> >
> > Comment the mappings in share\groff\1.20.1\tmac\
> > unicode.tmac. This file is automati
trebol:
> I can use -Tascii, but as you may have noticed,
> I'm not a English speaker, so I need send utf8
> mail, and formating with groff makes the work
> easy. Any advice?
Comment the mappings in share\groff\1.20.1\tmac\
unicode.tmac. This file is automatically loaded by
the
I wrote:
> My other suggestion...
Correction: It is actually Anton Shterenlikht's,
while I only proposed a way to implement it.
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Keith Marshall:
> > Thanks, I missed the piece about hd*sect-pg.
> > My version is definitely better then.
>
> Except for one fairly important issue: you are ad-
> vocating exposure of what *should* be a private in-
> terface, (according to naming convention), and is
> thus *entirely* spe
Ralph Corderoy:
> > Yes, and this is exactly what hd@set-page does.
> > The documentation doesn't say that P is not
> > read-only. I consider hd@set-page as a setter
> > of the field P and therefore preferable to set-
> > ting P directly. If it was not so trivial my
> > mehtod would
Keith Marshall:
> > I agree, but I didn't find a public mechanism to
> > do that.
>
> Does the attached achieve the desired effect?
> Agreed, it isn't intuitive: it's very picky about
> the placement of the reassignment of register 'P',
> and you have to set it to less than zero for it,
>
Anton Shterenlikht:
> Now that I sorted out my empty lines, I get the
> cover page with no number.
>
> I tried groff -n option, but it seems to change
> the number of only the cover page, which is not
> shown anyway. The numbers of other pages are unaf-
> fected. Is this the expected beh
Keith Marshall:
> > That is solved by (thanks to Anton Shepelev > ton@gmail.com>)
> >
> > .hd@set-page -1
> >
> But that isn't really a good solution! It re-
> quires getting your hands dirty with the internal
> (private) details of the
Anton Shterenlikht:
> However, I'm very reluctant to mess with mm/ms
> macro definitions locally. I'll live with the page
> number on the front page. The most annoying thing
> was the page number on the cover page, which is
> solved by .hd@set-page -1.
As a temporary solution, you can c
Anton Shterenlikht:
> I want the cover page to show no page number, the
> front page to show no number, and the first normal
> page to show page number 2. All pages after that
> I want to be numbered consequtively.
This is complicated and couldn't do it without fix-
ing mm. Maybe it's not wo
Anton Shterenlikht:
> This doesn't seem to have an effect on the cover or
> the front pages. Adding .PGNH removes page number
> from all consequtive pages, but not from these two.
I don't think the cover macros have anything to do
with the header, so this is strage. .PGHN works fine
for me
I wrote:
> Anton Shterenlikht:
>
> > > Also, you can use the second argument to
> > > .GETST to save the reference into a string and
> > > use that in the caption.
> >
> > Thanks, this works:
> >
> > .PSPIC rep-cold-mises-mesh.ps 6.0
> > .ds caption "Mises stress in the 0.3 mm notch
Anton Shterenlikht:
> > Also, you can use the second argument to .GETST
> > to save the reference into a string and use that
> > in the caption.
>
> Thanks, this works:
>
> .PSPIC rep-cold-mises-mesh.ps 6.0
> .ds caption "Mises stress in the 0.3 mm notch model
> .as caption " at \*[co
Anton Shterenlikht:
> I'd like to make a cover page with mm .COV-
> ER/.COVEND. How can I not number it, i.e. start
> numbering pages only from the following (front)
> page?
>
> Also, ideally I don't want to show the number on
> the front page. How to do this?
I don't have time t
Anton Shterenlikht:
> I want to reference some figure in the caption of
> another figure.
Also, you can use the second argument to .GETST to
save the reference into a string and use that in the
caption.
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against p
Anton Shterenlikht:
> I want to reference some figure in the caption of
> another figure.
Instead of .SETR, you should use the fourth parame-
ter of .FG. Same applies to .TB. You may check the
corresponding entries in the groff_mm man page.
--
() ascii ribbon campaign - against html e-mail
Anton Shterenlikht:
> How can I make the ToC appear in the beginning of
> the document, and not at the end, with mm .TC
> macro?
Using the psutils package, you can move the last
page containing the TOC to the beginning of the doc-
ument:
psselect -p_1,1-_2 in.ps out.ps
> Also, ho
Tadziu Hoffmann:
> > I don't have time now to look why this happens
> > [...]
>
> It has to do with "AS" saving the text in a macro.
> This results in part of the eqn code being already
> evaluated while saving the abstract, not when it's
> being processed for printing.
Thanks, now I see. Wh
Anton Shterenlikht:
> How about maths in the abstract?
> I don't know where to place
>
> .EQ
> delim $$
> .EN
I don't have time now to look why this happens, but
Werner's method works with .AS as well:
.ds eq $a sup b$
.AS
\\*[eq] is a formula in the abstract!
...
just make sur
Keith Marshall:
> Actually, preconv opens its input stream in "bina-
> ry" mode, rather than in Window's special "text"
> mode. Thus, it does see the \r\n EOL sequence,
> which it then explicitly interprets as the line
> terminator, so explicitly emulating the behaviour
> which would hav
I wrote:
> Is it reasonable to modify gpreconv or its Windows
> port so that on Windows it will expect '\r\n'?
preconv(1) says:
Trailing '-dos', '-unix', and '-mac' suffixes of
coding tags (which give the end-of-line conven-
tion used in the file) are stripped off before
the c
Werner Lemberg:
> > May I suggest a patch that will fix the format
> > of the header number in references?
>
> Please do!
OK, it is attached.
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
--- m-orig.tmac 2012-08-02 20:06:16.773
And here's another problem: floating displays in mm
are output from within a very strange environment
called \%ds*fev, which is nowhere defined, which
means it has the default parameters, including the
line length of 16 cm. This results, for example, in
incorrect horizontal alignment of
Hello all,
I have started using references in mm and found that
GETHN returns a heading number with two trailing
spaces, because this is the value of the hd*mark
string. This format is very inconvenient, because
what I expect to be '(2.1)' is in fact '(2.1. )'.
May I suggest a patc
Clarke Echols:
> The approach I usually use for superscripts is \u
> and \d, and to reduce the size of the superscript
> a \s-1 and \s+1 or +/- 2 if it looks better.
When I need to make my superscripts size-indepen-
dent, I multiply the current font size by a factor
instead of using a fixe
Tadziu Hoffmann:
> If you know for sure that your label requires only
> one line-height, then it would be easier to start
> a partially collected line (e.g., including your
> list marker and the right-hand label) and then al-
> ready set the new line length. This way you
> wouldn't have
Hello, again
I want to typeset a list like this:
1. Text text text text text text text [label A]
text text text text text text text text
text text text text text text text text
text text..
2. Text text text text text text text [label B]
Hello, all
I have problems with gpreconv on Windows (GNUWin32
Groff). Whenever I want to use it, I have to con-
vert the end-of-line symbols:
tr -d \015 < [infile]|groff -U -Kcp1251 ...
which makes the use of soelim much less convenient,
because I have to preconvert my files to the
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
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
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
Tadziu Hoffmann:
> > Adding \c and replacing .bp with 'bp fixed it.
>
> In a message further on in the thread Werner says
> he has implemented an "em1" request which is the
> same as "em" but doesn't have the last-page re-
> striction.
Yes, I had seen it. But my version of groff is too
ol
Hello all,
.bp doesn't seem to work in an end-of-input trap.
Here's an example for -Tascii:
.de END
this page
.tm before bp
.bp
.tm after bp
next page
..
.em END
End of input occurs here!
Why could this be? The same code works as expected,
i.e. prints "ne
Steve Izma
> James Lowden sent me, off list, this link to an
> article he wrote about the relevance of groff to
> fundamental concepts of programming and computer
> use. I assume he's too modest to broadcast it,
> but I think it's excellent:
> [...]
My thanks to James and to you, Steve
I accidently came upon what seems to me an unfair
judgement about groff and TeX:
As an example: In a presentation-markup lan-
guage, if you want to emphasize a word, you
might instruct the formatter to set it in
boldface. In troff(1) this would look like
so:
A
Bruno Haible:
> Anton Shepelev:
>
> > Is it possible to tell groff to use the standard
> > hyphen-minus sign of the ASCII table instead of
> > \[u2012] for hyphenation?
>
> People who ask this usually have a groff input
> that uses '-' both to d
I wrote:
> Another question is about the hyphen sym-
> bol -- \[hy]. Is it possible to tell groff to use
> the standard hyphen-minus sign of the ASCII table
> instead of \[u2012] for hyphenation? I couln't
> achieve it by commeting out the corresponding line
> in unicode.tmac, and i
Tadziu Hoffmann:
>> Could you please tell me the purpose of this
>> mapping in unicode.tmac:
>>
>> .char ' \[cq]
>>
>> This causes all apostrophes to be typeset as
>> closing single quotes. Is it correct?
>
> Yes.Apostrophes and (english) single right
> quotes are identica
Hello, all
Could you please tell me the purpose of this mapping
in unicode.tmac:
.char ' \[cq]
This causes all apostrophes to be typeset as closing
single quotes. Is it correct?
Anton
Ken Mandelberg:
> I've attached the ascii and postscript output. It
> gets the multiple authors and author titles right,
> but makes a mess of the document title. I suspect
> the latter is too Bell Labs specific.
The mess in the title is some roff language con-
structs that, assuming the
Ralph Corderoy:
> Is
> http://books.google.co.uk/books?id=Wz1C5JhTzlYC&lpg=PR12&ots=e8Ftu5WzMi&dq=documenters%20workbench%20mm%20macros&pg=PA38#v=onepage&q=documenters%20workbench%20mm%20macros&f=false
> of any use? Section 7 might be going through the macros you're
> discussing. Obviously, not
Werner LEMBERG:
> Please tell me if you have found a patch which I
> can apply to the repository.
This is bound to be difficult because I don't have
an exact specification of how mm _should_ typeset
the signature, and have to try to imitate it based
on tests -- the black box method...
O
Ken Mandelberg:
> I've attached the ascii and postscript output. It
> gets the multiple authors and author titles right
Looks like your version of mm completerly ignored
the last three arguments to AU: location, deparment
and initials. I am not sure it is correct either.
Anton
Ken Mandelberg:
> I tested the patch. It does indeed fix the single
> author with title case.
>
> However, there still is one difference between
> groff and troff. In troff the signature comes out
> bold and in groff it doesn't. Any thoughts on
> that?
OK, I have modified the patch (at
Ken Mandelberg:
> It seems like AU/AT with the MM macros is not
> working properly.
>
> Here is a simple test
>
>.AU "John Smith"
>.AT "CEO"
>.MT 5
>.P
>testing
>.FC
>.SG
>.br
>
> [...]
>
> So the AT title string never comes out, and there
> is an extraneous "
Hello, John
I don't have access to any other implementation of
troff than groff, but I have consulted "The Docu-
menter's Workbench", and it seems that groff's mm
signature macros have incompatibilities more serious
than the omission of the title, and some errors too.
For example, it print
Please, add the following two lines to the beginning
of the file:
.warn
.if !d secf .ds secf \" If not specified on commandline, init secf here.
I somehow missed them when copying.
I have attached the full working file for convenience.
Anton
secfilter.man
Description: Unix manual page
Dear Siteshwar, excuse me for addressing you as Van-
nevar Bush.
Anton
Vannevar Bush:
> It parses and shows me the whole page. What if I
> want to parse only OPTIONS section ? I am looking
> for something like :-
>
>groff -X -P -resolution -P100 -man -parse-section "OPTIONS" passwd
Here is my quick, dirty and incomplete solution:
.nr skip 0u \" Flag to in
Ken Mandelberg:
> Still no CEO.
Sorry, I missed this part. I looked into m.tmac and
found that the Memorandum-style signature does not
include the title (.AT). The only place where the
title is used is in the ms.cov -- ms-style cover
page activated by .COVER ms.
The curent implemenat
Ken Mandelberg:
> It seems like AU/AT with the MM macros is not
> working properly.
The problem is with the Memorandum-style signature
macro.
Without .warn in the beginning of your file you were
missing several warnings from Groff. I added it and
saw where the errors were. It turns o
Clarke Echols:
> I know the 'bp is the cause, but don't know how to
> handle page numbering at the bottom of the page
> while suppressing the 'bp request after EOF is
> reached.
Do I understand you correctly that you are calling a
'bp explicitly in the end of your file? If so,
maybe
Volker Wolfram:
> I'm using groff from the packages depot. But I re-
> ported to this list problems with textblock and
> viewing Postscriptfiles with ghostview and gv for
> a while.
But in the thread "Right margin problems" you said
the problem was with GhostScript, not with Groff.
Try v
Date: Thu, 22 Dec 2011 18:24:28 +0100
From: vol...@volker-wolfram.de (Volker Wolfram)
To: anton@gmail.com
Subject: Re: [Groff] Right margin problems
Anton Shepelev wrote:
> Volker,
>
> I have tried your example on my machine, and the re-
> sult is right-justified, as expect
Volker,
I have tried your example on my machine, and the re-
sult is right-justified, as expected.
Deri James suggested that your PostScript viewer
might not be working correctly. Try opening your
.ps file in a different viewer and also check if
with -Tlatin1 the resulting text file
Werner LEMBERG:
> Unfortunately, I don't have enough time currently
> to find a solution for your original problem.
Thank you very much for your time! Now I have more
options to choose from.
Anton
The previous post was encoded in CP-1251.
Please, accept my apology.
I can re-post it if necessary.
Anton
Thanks for your reply, Werner:
> What about doing it the naive way?
>
> File `lcuc' in UTF-8 encoding:
> [...]
> Provided you have proper PS fonts, this works with
> -Tps also.
>
> Am I missing something?
Your example works perfectly with -Tutf8 if the
source file is in UTF-8 and the -K pr
Werner LEMBERG:
> Can you prepare a small example which really
> demonstrates what you want to do?
Sorry for the innacurate example. I used a latin
letter instead of a Russian one and a random unicode
entity just to show the kind of translation I was
using.
Here is what I want to
Clarke Echols:
> [...]
> I went through the entire system and changed it so
> the name of a command, system call, etc. was al-
> ways lowercase unless the actual command or name
> was uppercase or mixed-case.
>
> That eliminated the confusion and improved usabil-
> ity. I am still opposed to
Hello all,
I want to typeset headers in man pages (an-old.tmac)
differently for text-based and PostScript devices.
For the former I want them to be uppercase, while
for the latter -- in the normal case, as they were
typed.
I thought I would prepend the TH and SH macros with
code that woul
Larry Kollar:
> I'm in sudden need of a hyphenation file for Por-
> tuguese (Brazilian if it matters).
Try the LaTeX patterns:
http://www.ctan.org/tex-archive/language/portuguese
Groff is designed to accept them. As I see, the
Portuguese file has some \lcode requests which may
be inco
Werner LEMBERG:
> > If it is OK, I will also provide a corresponding
> > path for the groff_mm man page.
>
> Please do so. And please provide a ChangeLog en-
> try also.
The patch to the man page is attached, and the
changelog entry could be as follows:
Add support for hyphenation modes
Werner LEMBERG:
> Please do so. And please provide a ChangeLog en-
> try also.
OK.
> PS: I can apply your patches as soon as the copy-
> right assignment has arrived.
Oh, I thought the limit was on the size of one patch
and not on their total size so I still could submit
small ones...
Hello all,
MM has only two hyphenation modes: no hyphenation
and mode 14. I disfavour mode 14 and propose a
patch that will allow MM to use other hyphenation
modes while keeping it backwards compatible with the
current behaviour.
The semantics of MM's Hy register are remaining the
sa
Hello, Werner.
Here is what I came up with. Feel free to edit to
your own taste or reject :)
Anton
--- groff.texinfo 2011-08-21 23:08:07.18750 +0400
+++ groff.texinfo.new 2011-08-27 01:04:15.546875000 +0400
@@ -6882,7 +6882,11 @@
@cindex manipulating hyphenation
@cindex hyphenati
Sorry, the later request should be:
.hcode \[u] x
Anton
Just as I thought I have finished the patch, I found
out I was wrong about the following piece:
Werner LEMBERG:
> > Therefore, I suppose that groff applies the ex-
> > isting character translations inversely to get
> > back to some simple characters. Then, hyphen-
> > ation codes can be com
Werner LEMBERG:
> > Frankly, yes :) -- add a warning to the descrip-
> > tion of the .tr request. Especially so, because
> > there are examples in the manual in which the
> > mapping is changed and then "restored" back. The
> > user should know the side effect of this opera-
> > tion.
>
> Tha
Werner LEMBERG:
> This is not possible. How shall come a glyph-only
> object into existence? I don't count ligatures
> and similar things here since they also need input
> characters to exist.
> [...]
> Well, \N'...' is kind of a glyph-only object, but
> by its very definition you can't hyph
Werner LEMBERG:
> Yes, this is a mess, introduced long before I was
> involved in groff. However, this affects the ter-
> minology but not the documentation itself. AFAIK,
> I've fixed all places in the doc files to make a
> clear distinction between input characters and
> output glyphs.
Thank you for the kind and patient explanation,
Werner.
> However, please avoid the term 'AGL compatible'.
> We are not talking about glyphs but about charac-
> ters!
Maybe this confusion is not only my fault also the
manual's:
The distinction between input, characters,
and o
Sorry for the mangled text in the previous message.
Werner LEMBERG:
> I've posted a solution a few years ago to the
> groff list which is still valid.
Ah, thank you. So you are mapping the Russian alpha-
bet to internal characters correspoinding to KOI-8-R
and then using a hyphenation patt
Werner LEMBERG:
> I've posted a solution a few years ago to the
> groff list which is still valid.
Ah, thank you. So you are mapping the Russian alpha-
bet to internal characters correspoinding to KOI-8-R
and then using hyphenation patterns in the same
encoding.
This way, not only UTF
Werner LEMBERG:
> Please don't hesitate to ask! Ideally, you could
> then improve the documentation based on your ques-
> tions :-)
Thanks, I appreciate it. I thouhgt I'd jot a draft
document descirbing various aspects of setting up
groff for a specific language, that would include
deal
1 - 100 of 220 matches
Mail list logo
