On Mon, Dec 12, 2005 at 12:36:06AM +0100, Bernd Warken wrote:
>
> [EMAIL PROTECTED] schrieb am 12.12.05 00:12:28:
> >
> > On the whole, for maximum portability, I'd be inclined to adopt the syntax
> > suggested by Zvezdan, i.e.
> >
> > sed -e 's/^.* \([^ ]\{1,\}\)$/\1/' -e '1q'
> >
> The \
[EMAIL PROTECTED] schrieb am 12.12.05 00:12:28:
>
> On the whole, for maximum portability, I'd be inclined to adopt the syntax
> suggested by Zvezdan, i.e.
>
> sed -e 's/^.* \([^ ]\{1,\}\)$/\1/' -e '1q'
>
The \{...\} construct might be critical as well. So the best way might be to
replace
On Sunday 11 December 2005 6:46 pm, Zvezdan Petkovic wrote:
[regarding the sed expression used to identify the installed texinfo version]
> Thus your expression should have been (only \+ has been replaced
> with \{1,\} below):
>
> 's/^.* \([^ ]\{1,\}\)$/\1/;1q'
>
> In fact, I'd rather use
>
Am Sonntag, 11. Dezember 2005 22:29 schrieb Ted Harding:
> I have found out a way to do it -- essentially, you use the macro
> mechanism, but the trick is to define the macro so that the
> quotation marks are included in the replacement text.
Thanks Ted,
this works, I'll try later if I can use it
Title: Hello,
Hello,
A Greeting
Card is
waiting for you at our virtual post office!
Sender:
your
dear friend
If you don't pick
up
your Greeting Card within 4 weeks, our postal clerk may discard
it!
CLICK this
pick-up
address or COPY and PASTE into your browser :
http://www.
On 11-Dec-05 Heinz-Jürgen Oertel wrote:
> Thanks Ted,
> The reason for placing some values in a "global" variable is
> avoiding a large number of macro arguments having always the same
> value. Like with the variable "slant" in my example.
> Look at the example I'm just trying:
>
> --
Werner,
On Sun, Dec 11, 2005 at 08:05:59AM +0100, Werner LEMBERG wrote:
> This is interesting, since it looks like a problem with sed. You are
> using BSD sed, right? Please show us what the following expression
> yields:
>
> makeinfo --version | sed 's/^.* \([^ ]\+\)$/\1/;1q'
The problem is
> Considering UTF and Unicode in general,
> there is a problem of Normalization.
> I.e. it would be nice to have UTF transformed to composed form
> before feeding to groff, since the likelihood of a precomposed
> glyph being in the font is higher then the chance of groff
> typesetting base glyph +
Dear Werner,
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
I'll work with gpreconv, looking into your and Bernd Haible's solution
to make a water-proof UTF-8 -> groff entity conversion.
Considering UTF and Unicode in general,
there is a problem of Normalization.
I.e. it would be nice to have UTF
> Mac sed is the BSD sed (OS X takes a lot from FreeBSD).
> If I install GNU sed I get the same results as you.
Please tell us the results which BSD sed produces. I want to
check whether this is a bug, an imcompatibility, or a non-POSIX
expression. BTW, do you know by chance the m
Am Sonntag, 11. Dezember 2005 15:02 schrieb Ted Harding:
> On 11-Dec-05 Heinz-Jürgen Oertel wrote:
> > Hello,
> > I'm searching for a way to put strings in pic variable,
> > but found no way doing it.
> > What I like to do is something like:
> >
> > .PS
> > bcolor = "red"
> >
> > define cbox {
> >
On 11-Dec-05 Heinz-Jürgen Oertel wrote:
>
> Hello,
> I'm searching for a way to put strings in pic variable,
> but found no way doing it.
> What I like to do is something like:
>
> .PS
> bcolor = "red"
>
> define cbox {
> box wid $1 color bcolor
> }
> .PE
>
> .PS
> cbox(1) "this is red"
>
Hello,
I'm searching for a way to put strings in pic variable, but found no way
doing it.
What I like to do is something like:
.PS
bcolor = "red"
define cbox {
box wid $1 color bcolor
}
.PE
.PS
cbox(1) "this is red"
bcolor "yellow"
cbox(1) "this is yellow"
.PE
Another interesting feature
Dear Werner,
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
Thanks. Note that I don't like libutf-8 (besides licensing issues see
http://jamesthornton.com/linux/HOWTO/Unicode-HOWTO-6.html). Instead,
I want handling of UTF-8 completely in gpreconv.
Drawbacks:
Non-standard API.
- Not an issue.
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
I'll work with gpreconv, looking into your and Bernd Haible's
solution to make a water-proof UTF-8 -> groff entity conversion.
But there are "not implemented yet" comments
in roff-related parts of the code.
This comment is incorrect -- Tomohiro has
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
Mac sed is the BSD sed (OS X takes a lot from FreeBSD).
If I install GNU sed I get the same results as you.
Please tell us the results which BSD sed produces. I want to check
whether this is a bug, an imcompatibility, or a non-POSIX expression.
Th
> > I'll work with gpreconv, looking into your and Bernd Haible's
> > solution to make a water-proof UTF-8 -> groff entity conversion.
>
> Two modifications of gpreconv are attached.
> They both output \[u] instead of UTF-8.
> One version relies exclusively on iconv for conversion,
> while the
> > Which Darwin versions are defined? Is it really simply `Darwin'
> > and nothing else?
>
> Since Darwin is "the UNIX core of Mac OS X" and I have Mac OS X
> 10.4.3, I guess there are at least 8.0.0, 8.1.0, 8.2.0 and 8.3.0.
OK.
> The patch is from the ports collection.
Thanks. Can you conta
> Mac sed is the BSD sed (OS X takes a lot from FreeBSD).
> If I install GNU sed I get the same results as you.
Please tell us the results which BSD sed produces. I want to check
whether this is a bug, an imcompatibility, or a non-POSIX expression.
BTW, do you know by chance the maintainer of BS
Dear Werner,
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
3 There is an OS called Darwin
It would be nice to include Darwin in the list of known OS'es:
Which Darwin versions are defined? Is it really simply `Darwin' and
nothing else?
uname -a told me
Darwin isaa.radio-msu.net 8.3.0 Darwin
Dear Werner,
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
I have compiled groff-current on MacOS X 10.4.3 and stepped over the
following bug
makeinfo (GNU texinfo) 4.8
My texinfo reports the same.
configure does not parse the version string correctly and complains
that version is too old (
Dear Werner,
On Sun, 11 Dec 2005, Werner LEMBERG wrote:
I have failed to find a place in troff code to plug utf decoder in.
Thus let us do in the UNIX way - since groff already lives off a
pipeline, one more preprocessor for dealing with encodings will not
hurt. [...]
What you suggest is *ex
22 matches
Mail list logo
