"W. L. Estes" wrote:
>
> > Attached is a simple test case that demonstrates that @value{} does not
> > appear to be working inside @uref for texi2pdf. It does work for makeinfo
> > and (I think) texi2dvi. This construct worked with the texinfo shipped
> > with RedHat 6.0 and only broke when I upgraded to 4.0 to fix the @image
> > problem you folks have helped me through.
>
> The texinfo manual states:
>
> You can use the `@set' command to specify a value for a flag, which
> is expanded by the `@value' command. A flag is an identifier; for best
> results, use only letters and numerals in a flag name, not `-' or
> `_'--they will work in some contexts, but not all, due to limitations
> in TeX. The value is just a string of characters, the remainder of the
> input line.
I deleted the _ in the example and it still failed. I used OARURL as
the variable name. I also tried replacing the @uref that is causing the
problem with @b to see if is was a general expansion issue. The
following
sequence worked:
@set OAR-URL http://www.OARcorp.com
@b{@value{OAR-URL},@value{OAR-URL}}
and this one did also:
@set OARURL http://www.OARcorp.com
@b{@value{OARURL},@value{OARURL}}
So I think this is more an issue that @uref has a problem with expanding
variables than the anything else.
The "_" discussion reminds me of a problem I saw a few years ago. Can
you
@include{} a file name with an _ in it? I remember some tool that did
not
like that. The newlib documentation is extracted from the source code
and
some C library name had an _ in it so the file.tex had one in it. Weird.
--
Joel Sherrill, Ph.D. Director of Research & Development
[EMAIL PROTECTED] On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
