On Tue, 2 Jan 2024 11:04:25 -0600
Dave Kemper wrote:
> > ECMA-48 says for 0x84:
>
> Also irrelevant to groff, as it doesn't use ECMA-48. Groff tools
> (including gpic) take input in Latin-1, period.
I don't think so. ECMA-48 may be interpreted by terminals.
In the case of terminal output,
If gpic gets Ä (0xc3 0x84) it complains about 0x84.
If gpic gets ä (0xc3 0xa4) it does not complain about 0xa4.
gpic says: "invalid input character".
So because both being above ASCII (8 bit area), what makes 0x84 wrong?
It seems that 0x84 is located in a control area whereas 0xa4 in an
graphic
IMHO,
the website pool should not be divided. Instead access to information
should be accomplished by different means.
I dump all my code snippets or running prof of concepts, what I
otherwise would forget, into one directory and find these old samples
later either by file naming or via grep. The
A showcase as like at a trade show?
I think it would be better to have easy to understand single topic
prove-of-concepts samples, a bin to throw in and a
whatever-grep-function for searching.
Those kinda website have to be invented in the first place, right?
On Thu, 07 Dec 2023 17:35:25 +
For the protocol, write a macro:
.de SYS-include\" .SYS-include filename extension
.ds SYS-filename \\$1
.sy preconv -e utf8 \\*[SYS-filename] \
| grap | pic | tbl | eqn -T\\*(.T > \\*[SYS-filename].intermediate
.so \\*[SYS-filename].intermediate
.sy rm \\*[SYS-filename].intermediate
..
Werner LEMBERG wrote (Thu, 17 Nov 2016 09:02:52 +0100
(CET)):
> > might someone be resident in Berlin/ Germany? willing to chit-chat
> > at a Cafe about that C-code base, 'cause it's really leaved behind,
> > a bit patchy and dangerous to play around with and I don't wanna sit
> > for myself.
>
well so, ehm,
_m^..^m_
might someone be resident in Berlin/ Germany? willing to chit-chat at
a Cafe about that C-code base, 'cause it's really leaved behind, a bit
patchy and dangerous to play around with and I don't wanna sit for
myself.
(In my spare time, I'm not interes
Joh-Tob Schäg wrote (Wed, 11 Nov 2015 17:32:47
+0100):
> Dear groff-mailing list,
>
> i seached for an alternative to latex and found groff. Sadly i found
> no IRC or something where i could ask directly.
> But before i invest time in groff or some macro system, i wanted to
> know if it fits m
exchanged:
> ttf2afm -o "$afmfont" "$ttffont"
> ttf2ufm $ttffont - | t1asm -a > $pfafont
with:
fontforge -script ffscript.pe $ttffont
(a hint from http://www.schaffter.ca/mom/momdoc/appendices.html)
=> success
[fontforge should write a documentation for their scripting.]
wrote (Wed, 1 Jul 201
Hi, I did:
groffpath="/usr/share/groff/current/font/devps"
DESCfile="$groffpath/DESC"
TEXTMAPfile="$groffpath/generate/textmap"
TEXTENCfile="$groffpath/text.enc"
#DOWNLOADfile="$groffpath/download"
DOWNLOADfile="./download"
ttffont='ttf/DroidSans.ttf'
groffname='DSaR'
afmfont="$(basename $ttffon
Hi, since I sparked an issue, I might explain my:
I coded a macro, that does a defined vertical space
(.sp //n[distance]u). The value can be set if the
switch '--define' is used. The macro should make a
temporary vertical move, when a number was provided.
Therefore I met a condition that if no p
Carsten Kunze wrote (Fri, 21 Nov 2014 18:12:10
+0100 (CET)):
> The new users might not start with creating macro packages like MM.
> They would use an existing macro package to create a document. The
> best way to attract them is to create a comfortable macro package.
Samples! Running samples,
Carsten Kunze wrote (Tue, 18 Nov 2014 11:00:55
+0100 (CET)):
> hoh...@arcor.de wrote:
>
> > > .ifx ... \{\
> > > ...
> > > .\}
> > > .el .if ...
> >
> > A customer would know inherently that for
> >
> > .if x ... \{\
> > ...
> > .\}
> > .el .if ...
>
> The use should know if compatibility m
Carsten Kunze wrote (Mon, 17 Nov 2014 14:32:09
+0100 (CET)):
> .ifx ... \{\
> ...
> .\}
> .el .if ...
A customer would know inherently that for
.if x ... \{\
...
.\}
.el .if ...
it is an "if", it is a special comparison and he has to look for it at
the chapter for comparisons (3 facts out o
I cannot see a benefit in anything other/new than the prefix indicator
that already exists. The concept is scalable and should be used. In
input.cpp the ifelse construct used for prefix chars, that should be
converted to a switch (I already did it), is equally to the switch used
for requests. To i
Ralph Corderoy wrote (Sat, 15 Nov 2014 12:17:25
+):
I favor switch before elif (and the like), at least in the sources
(do_if_request() in input.cpp) as well. ;)
Holger
wrote (Wed, 12 Nov 2014 20:33:07 +0100):
At least, this concept
> .if 'str'pattern1'pattern2'..'patternN' anything
fails in groff cannot determine the end of the conditional:
.if 'str'pattern1'pattern2' .tm ' cause of that
Spaces can also be part of the pattern. It seems, that braces are
nee
Ralph Corderoy wrote (Fri, 07 Nov 2014 16:16:38
+):
> Hi Holger,
>
> > Due to the 'Troff User's Manual' page 24 and the man 7 groff
> > (missing a negation)
>
> What's missing?
"I" -- I was missing .. ;)
> > the statement:
> >
> > .if 'str1'str2' anything
> >
> > cannot handle regular
Ralph Corderoy wrote (Thu, 06 Nov 2014 16:35:23
+):
> Hi Holger,
>
> > .\" I found this for strings
> >
> > .ds c "
> > .ds d "
> > .if '\*c'foo' .ds d "bar
> > .ie '\*d'bar' .tm *9: true
> > .el .tm *9: false
>
> If you want to preserve d's value for later use then you're back t
Hi, I wonder if this sample, that demonstrates OR of two string
comparisons, are an recommend way to code such conditions, avoiding an
extra macro or code doubling.
Regards Holger
.\" I found this for strings
.ds c "
.ds d "
.if '\*c'foo' .ds d "bar
.ie '\*d'bar' .tm *9: true
.el .tm
I was wrong. Dieresis is used in PinYin.
The "Chinese for Beginners" (ISBN 7-5619-1117-3) I refer, also uses
twice the size periods below the vowel to tag the accentuated syllable
of a word.
sorry Holger
wrote (Thu, 7 Aug 2014 15:35:28 +0200):
>
>
> [forward due to wrongly replied privatly
[forward due to wrongly replied privatly -hh-]
> Found a lot of lǜlǚ on the net but cannot check my papers this
> month. Sorry. Syllables lu/lü and nu/nü may be ambiguous. It's the
> only use of ü.
Yep.
> Wikipedia talks about a ü-free PinYin and Chinese use us-keyboards.
Maybe for *ente
"Bernd Warken" wrote (Mon, 4 Aug 2014
18:06:03 +0200):
> For `gpinyin', the European-like Chinese, I need to create character
> overstrikes for the 1st (a macron) and the 3rd tone (a caron).
> To append an accent over the ü and Ü characters (u/U umlaut) for all
> 4 tones seems to be even more com
Ralph Corderoy wrote (Sat, 12 Jul 2014 14:15:41
+0100):
> Hi Holger,
>
> > Doug McIlroy:
> > > (1) Does white space get decorated?
> >
> > Yes. So it can be distinguished from multiple underlinings.
>
> Don't quite understand what you mean here? I guess Doug was thinking
> of the difference
Doug McIlroy wrote (Tue, 08 Jul 2014 09:10:05
-0400):
> (1) Does white space get decorated?
Yes. So it can be distinguished from multiple underlinings.
> (2) How about punctuation?
When part of the string or text. So one can text it on the spot.
> (3) Do multiple decorates terminate together
Werner LEMBERG wrote (Fri, 28 Mar 2014 06:44:19 +0100
(CET)):
> Well, *if* someone is going to implement a better line breaking
> algorithm, it should be the best available, and not a compromise.
> Changes are necessary in any case...
A clear word for mission statement. BTW.
> > Like Doug, I sm
Peter Schaffter wrote (Thu, 27 Mar 2014 19:29:13
-0400):
> On Thu, Mar 27, 2014, Tadziu Hoffmann wrote:
> >
> > > So there are two readily-available methods: varying
> > > letter-spacing, or varying inter-word spacing.
> >
>
> Not "or" -- "and". Most times, I opt for word-spacing adjustments.
Peter Schaffter wrote (Mon, 3 Mar 2014 16:43:27
-0500):
>
> archaic, of limited use, poor typesetting compared to TeX,
> legendarily difficult to master. None of it is true--except, of
> course, the last bit.
>
> ...
>
> where are these front-ends to come from if we don't attract new
> users w
Tadziu Hoffmann wrote (Wed, 26 Feb 2014
23:06:17 +0100):
>
> > Three browsers, three layouts (surf uses webkit).
>
> Hmmm, well, I suspect if you used groff with -Tlatin1, -Tlj4,
> -Tdvi, and -Tps you might also get four different layouts...
> Simply consider different browsers like different d
No, despite the Typos. Three browsers, three layouts (surf uses
webkit). Firefox's is perfect!
Holger
"Eric S. Raymond" wrote (Wed, 26 Feb 2014 10:42:52
-0500):
> hoh...@arcor.de :
> > > Some years ago I enhanced geqn so it can emit MathML.
> >
> > What did I wrong?
>
> To emit MathXML get
"Eric S. Raymond" wrote (Wed, 26 Feb 2014 08:29:00
-0500):
> hoh...@arcor.de :
> > I don't got to what extend the support of web/ html features shall
> > be supported -- catchword: use case. For instance, will eqn code be
> > traversed to MathJax?
>
> Some years ago I enhanced geqn so it can e
Volker Wolfram wrote (Wed, 26 Feb 2014
07:59:35 +0100):
> And as a newbie I don't know about the code and design of groff. But
> I've changed from LaTeX to groff because it is simple and easy to
> understand.
+1
Using Groff features a learning curve with raising success.
> And that is very cool
I don't got to what extend the support of web/ html features shall be
supported -- catchword: use case. For instance, will eqn code be
traversed to MathJax?
Holger
Tadziu Hoffmann wrote (Fri, 7 Feb 2014
00:29:11 +0100):
> >> If the user set up the page margins incorrectly, you can hardly
> >> blame the software for that...
> >
> > cannot see any border setups at http://asciidoc.org/article.txt
>
> You set it in the style sheet? Or on the command line?
>
cannot see any border setups at http://asciidoc.org/article.txt
Tadziu Hoffmann wrote (Thu, 6 Feb 2014
16:20:47 +0100):
>
> > Found http://asciidoc.org/article.pdf that shows the Table of
> > Contents shifted to the right and I'm glad that in using groff
> > I can get ride of such artifacts (ye
Peter Schaffter wrote (Tue, 4 Feb 2014 11:32:00
-0500):
> On Tue, Feb 04, 2014, Dave Kemper wrote:
> > I understand the need for backwards compatibility, but I more and
> > more find myself wishing groff had a global option to choose
> > between "follow historical usage" and "be sane." For som
Peter Schaffter wrote (Sun, 2 Feb 2014 00:03:58
-0500):
> On Sat, Feb 01, 2014, hoh...@arcor.de wrote:
> >
> > Werner LEMBERG wrote (Wed, 29 Jan 2014 06:37:05 +0100
> > (CET)):
> > > Given today's memory abundance and the high velocity of CPUs, the
> > > ideal route would be to implement a do
"Eric S. Raymond" wrote (Tue, 4 Feb 2014 23:08:02
-0500):
> James K. Lowden :
> > Hmm, seems to me every document is presentation-centric, depending
> > on what that means. Are you suggesting Postscript and PDF are not
> > long for this world? Are we doomed to the eyesores produced by
> > lousy
Werner LEMBERG wrote (Wed, 29 Jan 2014 06:37:05 +0100
(CET)):
> Given today's memory abundance and the high velocity of CPUs, the
> ideal route would be to implement a document-wide algorithm for
> typesetting a document (in contrast to TeX's page-wide approach).
I think, that an author can prev
Hi, a simple drawing might be:
\\h'|-\\n(.ou+0.3c'\\v'|09.2c'\\D'l 0.6c 0'\
\\h'|\\n(.lu+\\n(.ou-1c'\\D'l 0.6c 0'
This is drawing two lines:
\D'l '
at the end, and temporary moves, where to start drawing:
\v'|'\h''
Units are necessary due to default interpretations by groff, "|" makes
position
Once I stumbled over the .sp feature, to increase the output line
number counter (.nm) at every call to .sp, and ask myself, if here is
another "harmless" vertical movement intended to be used instead. For
instance to have a paragraph spacing.
--hh
41 matches
Mail list logo
