Re: [help-texinfo] Cannot make texinfo-5.2
I want to install texinfo-5.2 in Scientific Linux 6. As Gavin said, it's presumably some kind of gnulib issue. Apparently gnulib thinks your implementation of strstr is so awful that it has to replace it. Sigh. If you can, please try the pretest for the next release at http://alpha.gnu.org/gnu/texinfo/texinfo-5.1.90.tar.xz. Perhaps the problem has already been fixed, whatever it is. karl
Re: [help-texinfo] Cannot make texinfo-5.2
I appreciate your help. When I run make, I got this error message. (And same error with texinfo-5.1.90.) In fact, I want to install newlib, but for newlib, texinfo has to be installed. So I've tried to install texinfo. I understand that this probrem is not because of texinfo, so there is no need to reply. I'm sorry to have troubled you. Shirakata. On 2015/04/06 0:42, Gavin Smith wrote: n 5 April 2015 at 09:43, Hikari Shirakata shirak...@astro1.sci.hokudai.ac.jp wrote: Hello, I want to install texinfo-5.2 in Scientific Linux 6. It seems to be configured successfully, but I have an error at the next stage. /home/hoge/texinfo-5.2/info/infodoc.c:1153: undefined reference to `rpl_strstr' . I have been googling on this error, but I couldn't get the solution. What should I do for this error? Gnulib uses the rpl_ prefix for replacement functions. From the config.log file you attached, it looks like it found that strstr needed to be replaced by the Gnulib version. Is that error message a link error? Please post the full output of the command that gave this error message as well as the exact command itself you ran.
Re: [help-texinfo] Cannot make texinfo-5.2
In fact, I want to install newlib, but for newlib, texinfo has to be installed. Oh. You can probably just touch a .info file for newlib and it shouldn't care further. (newlib should be distributed with the .info, or not require it -- seems like a bug in their source distribution.) Alternatively, SL6 should surely have a texinfo package, which should suffice. Hope this helps, Karl
Re: [help-texinfo] how does one encode a middle dot? and other questions
at some point, it is envisonned to have a
command like @U{} to allow to put any unicode point.
We have @U for the upcoming release. In fact I implemented it
specifically after the discussion of middle dot for Catalan in January
and February.
The dots are sometimes inside, sometimes outside the square brackets.
Ok, will look.
checking for a french Unicode locale... none
Why does it check for that? Is it just for running a test?
Or would it enable stuff?
It comes from gnulib/m4/locale-fr.m4. I don't know why or what
dependency pulled it in. We did not request it explicitly. The test
result has no particular effect on Texinfo's behavior, so far as I know.
Sixth, how do I run texi2any without installing it?
I use a one-line shell script:
exec /path/to/texinfo/checkout/tp/texi2any.pl $@
I suppose an alias would do as well, if preferred.
but what will happen on a machine that does not use a UTF-8
locale? Will the resulting info file still be readable when the
above command is used? How will the guillemet get rendered there?
In my experience, the usual answer is that it will appear as binary
garbage.
In my further experience, the best answer is, don't use
@documentencoding UTF-8 unless it is really needed (e.g., the manual is
not written in English).
Not that anyone cares, but personally I deplore the current trend of
randomly forcing all manuals to UTF-8. The plethora of resulting
Unicode quotes makes the manuals unreadable in non-UTF-8 environments.
I have taken to replacing the three Unicode bytes with SPC SPC ` and '
SPC SPC so I can use them.
I wish to check whether makeinfo still produces no blank line
between the items of a bulleted list (which 5.1 doesn't but
4.13 did).
With the test file below, there is no blank line between the items with
either svn texinfo or with makeinfo 4.13 either.
I seem to recall precisely that 4.13 was inconsistent in this regard,
sometimes but not always adding blank lines. And so when Patrice
discovered this, it seemed like the most user-controllable and
-understandable behavior was to preserve blank lines in the input
between items, but not have the program add blank lines sometimes but
not others. Pretty sure other manuals used the
no-blank-line-insertion behavior for short lists.
I don't imagine that answer will make you happy, but it's where we are.
And whether @bullet{} still produces only a * (U+002A)
instead of a real [binary garbage] (U+2022) in an info file.
With the test file below, I get some multibyte character for the bullet.
I can't tell what it is, but it's probably the one you want.
best,
karl
\input texinfo
@setfilename listutf.info
@documentencoding UTF-8
@itemize
@item i.
@item j.
@end itemize
@bye
Re: [help-texinfo] how does one encode a middle dot? and other questions
On 5 April 2015 at 10:18, Benno Schulenberg bensb...@justemail.net wrote:
First, is there a way to encode U+00B7 (middle dot) in a texi
file, in a way similar to @guillemetright{} and @bullet{}?
Either use the character itself directly in the encoding of the file,
or the upcoming release has a new command @U so you could do @U{00B7}
- for Info output this gives the centre dot for UTF-8 output only.
Second, in the manual it says that @documentencoding sets the
input encoding. But I find that an @guillemetright{} only gets
rendered as » (instead of ) when I set @documentencoding
to UTF-8. So it's more like that command sets the output encoding,
no?
From the latest revision of the manual: The '@documentencoding'
command declares the input document encoding, and can also affect the
encoding of the output.
Sixth, how do I run texi2any without installing it?
Running tp/texi2any fails with:
Can't locate Texinfo/Convert/Texinfo.pm in @INC (@INC contains:
/usr/local/share/texinfo/lib/Text-Unidecode/lib
/usr/local/share/texinfo/lib/Unicode-EastAsianWidth/lib
/usr/local/share/texinfo/lib/libintl-perl/lib /etc/perl
/usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10
/usr/local/lib/site_perl . /usr/local/share/texinfo) at tp/texi2any line 106.
BEGIN failed--compilation aborted at tp/texi2any line 106.
Doing cd tp first has always worked for me. I haven't researched how
to get it to run as tp/texi2any. A related problem that has caught
me out several times is trying to run an installed makeinfo (e.g.
/usr/local/bin/makeinfo) when the present working directory is tp
in the source directory - it will use the modules from the source
directory (which may have uninstalled modifications) instead of the
installed modules.
(By the way, the gluing together of failed--compilation is ugly.)
AFAIK this is a Perl error message.
Re: [help-texinfo] how does one encode a middle dot? and other questions
On Sun, Apr 05, 2015 at 11:18:34AM +0200, Benno Schulenberg wrote:
Hi,
Several things.
First, is there a way to encode U+00B7 (middle dot) in a texi
file, in a way similar to @guillemetright{} and @bullet{}?
Not that I know of, but at some point, it is envisonned to have a
command like @U{} to allow to put any unicode point.
Second, in the manual it says that @documentencoding sets the
input encoding. But I find that an @guillemetright{} only gets
rendered as » (instead of ) when I set @documentencoding
to UTF-8. So it's more like that command sets the output encoding,
no?
Indeed, the output encoding is set to the input encoding in the
default case.
But what will happen on a machine that does not use a UTF-8
locale? Will the resulting info file still be readable when the
above command is used? How will the guillemet get rendered there?
Eli answered this question already on the info reader side.
It is also possible to set the output encoding explicitly, by using
-c OUTPUT_ENCODING_NAME=ascii
for instance. Also setting --disable-encoding could have the effect you
are looking for.
--
Pat
