libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] w32 and Libtool.


From: Ralf Wildenhues
Subject: Re: [RFC] w32 and Libtool.
Date: Sun, 31 Oct 2010 10:13:21 +0100
User-agent: Mutt/1.5.20 (2010-08-04)

Hi Peter,

* Peter Rosin wrote on Sat, Oct 30, 2010 at 11:06:12PM CEST:
> Den 2010-10-30 09:15 skrev Ralf Wildenhues:
> > * Peter Rosin wrote on Fri, Oct 29, 2010 at 10:00:34PM CEST:
> >> +With contemporary GNU tools, auto-import often saves the day, but see
> >> +the GNU ld documentation and its @code{--enable-auto-import} option for
> >> +some corner cases when it does not.
> > 
> > This should have a cross reference to just that documentation.
> 
> ...if I write:
> 
> With contemporary GNU tools, auto-import often saves the day, but see
> the GNU ld documentation and its @code{--enable-auto-import} option
> for some corner cases when it does not
> (@pxref{Options, , --enable-auto-import, ld, The GNU linker})
> 
> that renders as:
> 
>    With contemporary GNU tools, auto-import often saves the day, but see
> the GNU ld documentation and its `--enable-auto-import' option for some
> corner cases when it does not (*note -enable-auto-import: (ld)Options.)
> 
> with my info reader.  Why is one dash eaten?  Can I stop that from
> happening?  Should I care? (i.e. the link works, at least for me)  And...

Have you tried using @option{--enable-auto-import} here?  Please check
for all render forms (info, PDF, DVI, HTML) for whether they cope with
this correctly.  The point is that '--' means a longer dash; see info
texinfo Conventions.

> > Please write as:
> >    Examples are
> >    @uref{http://alain.frisch.fr/@/flexdll.html, FlexDLL} and
> >    @uref{http://edll.sourceforge.net/, edll}.
> > 
> > makeinfo should get the line breaking right by itself IMVHO.
> 
> ...what's up with the extra "@/" in your version?  (just curious)

It allows an optional line break at this point:
  info texinfo --index /

> Regarding line breaking, both versions render similar to:
> 
>    It should be noted that there are various projects that attempt to
> relax these requirements by various low level tricks, but they are not
> discussed here.  Examples are FlexDLL
> (http://alain.frisch.fr/flexdll.html) and edll
> (http://edll.sourceforge.net/).
> 
> in my 80 column info reader.  Which is not optimal IMVHO.  :-/  Oh well.

One way around that is to simply reword the sentence.  Surprisingly
often that works quite well without making things sound too stupid.
E.g.:
  The interested reader may refer to the @uref{...} and ... projects
  for more details.

Feel free to go ahead as you prefer.

Thanks,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]