Nabble - Gnu - Texinfo

Re: Problematic indentation in HTML output of makeinfo

2009-11-19T23:10:12Z

Am 20.11.09 07:59, schrieb Thomas Keller:
> [..] So putting
>
> @ifhtml
> @exampleindent 0
> @end ifhtml
>
> in the header fixes my problem.

Apparently I was too fast - while first-level preformatted areas no
longer have the unwanted whitespace, deeper levels still have it, see
again the attached files.

I tried to also set @paragraphindent to 0, but this didn't work. Is
there anything else I could set here?

I guess its visually pleasing to indent HTML output, but at least for
indenting preformatted contents its harmful. A good rule of thumb here
should be "indent the elements, not the contents" wherever possible,
because somebody might simple want to render another element (not only
@example or @smallexample) with a fixed width and would run into the
same problems.

Thomas.

--
GPG-Key 0x160D1092 | tommyd3mdi@... | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

Test 1.0

Up: (dir)

Top

This is
    a small
example
    which
            works

     This is
         a small
     example
         which
                 does not work

\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename test.info
@settitle Test 1.0
@ifhtml
@paragraphindent 0
@exampleindent 0
@end ifhtml
@c %**end of header

@node Top
@top Top

@smallexample
This is
a small
example
which
works
@end smallexample

@itemize
@item
@smallexample
This is
a small
example
which
does not work
@end smallexample
@end itemize

@bye

signature.asc (266 bytes) Download Attachment

From forum: Gnu - Texinfo - Bugs

Re: Problematic indentation in HTML output of makeinfo

2009-11-19T22:59:41Z

Hi Karl!

Am 20.11.09 01:30, schrieb Karl Berry:

> The normal way to use @example is without leading whitespace, since it
> inserts indentation itself. And you can control how much that
> indentation is with @exampleindent, if you feel the need.
>
> If you put your own physical whitespace characters in, then I don't see
> how we have any alternative but to honor them.
>
> Since the general goal of Texinfo is to produce the "same" output in
> different formats, I don't think it would be a good default not to
> indent in HTML.
>
> But anyway, maybe texi2html has some other css or other viable options
> to do what you want to do. For example, it occurs to me that if you
> reliably use the same amount of physical whitespace, you could use css
> to shift the [small]example envs to the left by that amount.

Maybe you got me wrong. Consider the attached texi file, which makeinfo
converts to the attached HTML file.

If you apply the following CSS to the HTML file

<style type="text/css">
pre.smallexample {
border: 1px solid red;
padding: 0;
}
</style>

you see what I mean. Even though the container gets a padding of 0, the
text still does not start on the very left of the container. This is
because the preformatted text is rendered as

<pre class="smallexample"> This is
a small
example
</pre>

where

<pre class="smallexample">This is
a small
example
</pre>

would be correct, since I have no way of removing the additional
whitespace with CSS foo. The problem gets uglier, if @example and
@smallexample are used deeper down the document tree, because additional
"prefix" whitespaces are then added.

However, I've looked into the manual of @exampleindent and this does
what I want, obviously [0] states

"@exampleindent is ignored for HTML output."

which apparently is no longer true for at least version 4.13. So putting

@ifhtml
@exampleindent 0
@end ifhtml

in the header fixes my problem.

Thanks for your help!
Thomas.

[0] http://www.gnu.org/software/hello/manual/texinfo/exampleindent.html
--
GPG-Key 0x160D1092 | tommyd3mdi@... | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename test.info
@settitle Test 1.0
@ifhtml
@exampleindent 0
@end ifhtml
@c %**end of header

@node Top
@top Top

@smallexample
This is
a small
example
@end smallexample

@bye

Test 1.0

Up: (dir)

Top

This is
    a small
example

signature.asc (266 bytes) Download Attachment

From forum: Gnu - Texinfo - Bugs

Re: Problematic indentation in HTML output of makeinfo

2009-11-19T16:30:27Z

The normal way to use @example is without leading whitespace, since it
inserts indentation itself. And you can control how much that
indentation is with @exampleindent, if you feel the need.

If you put your own physical whitespace characters in, then I don't see
how we have any alternative but to honor them.

Since the general goal of Texinfo is to produce the "same" output in
different formats, I don't think it would be a good default not to
indent in HTML.

But anyway, maybe texi2html has some other css or other viable options
to do what you want to do. For example, it occurs to me that if you
reliably use the same amount of physical whitespace, you could use css
to shift the [small]example envs to the left by that amount.

Best,
Karl

From forum: Gnu - Texinfo - Bugs

Problematic indentation in HTML output of makeinfo

2009-11-18T17:30:45Z

Hi!

I'm experiencing an unwanted nuisance with the HTML generator of
makeinfo up to the latest version 4.13: Leading indentation is preserved
in the final HTML output.

Normally this wouldn't be a problem since consecutive whitespaces are
collapsed into a single whitespace and therefor ignored, however in
preformatted areas (<pre>) which are created by @example or
@smallexample they shift the text to the right.

The only knob which changes the interpretation of whitespaces in CSS is
the white-space property [0], however this only leaves me with the
options to ignore consecutive whitespaces everywhere or to print them
everywhere, I cannot tell the browser to "ignore leading" whitespaces -
which is also not an option, because it would remove wanted leading
indentation as well.

The indentation is good for plaintext and info output, but in my opinion
indendation should be switched of completely for HTML output (or at
least the HTML target should have an option to do so).

Note that using @exdent is not an option here for two reasons, firstly,
because the indendation is wanted in other output formats we have
(amongst them PDF) and secondly, adding @exdent in front of every single
line in an @(small)example section seems to be hilarious...

Thanks for taking care!

Thomas.

[0] http://www.w3schools.com/CSS/pr_text_white-space.asp
--
GPG-Key 0x160D1092 | tommyd3mdi@... | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc (266 bytes) Download Attachment

From forum: Gnu - Texinfo - Bugs

Need help for the japanese document errors

2009-11-17T07:05:23Z

Hello,

This is the remaining bug first reported by Reinhold a while ago I would
like to solve. The japanese .texi is in utf8, and the utf8 in the document
is handled rightly, but not the translated strings. The document is part of
the test suite (and more precisely, it is the only file whose result is
not in the repository, since it is wrong), in
test/encodings/japanese.texi

When the strings were in the translations.pl file, I couldn't manage
to fix the issue without breaking something else. Now, with the gettext
framework the strings are separate from the code, in the file:
po_document/ja.utf-8.po

So it should be possible to fix this issue now. I even thought that the
issue would solve itself magically once that a gettext-like framework was
used. Unfortunately this is not the case and the document output hasn't
changed a bit after switching to the new translation framework.

Maybe this is a known issue with an easy fix and is covered by the
libintl-perl FAQ:
http://search.cpan.org/dist/libintl-perl/lib/Locale/libintlFAQ.pod#Why_do_the_gettext_functions_always_unset_the_utf-8_flag_on_the_strings_it_returns?
http://search.cpan.org/dist/libintl-perl/lib/Locale/libintlFAQ.pod#Can_I_set_the_utf-8_flag_on_strings_returned_by_the_gettext_family_of_functions?

But I cannot make sense of this.

To test, the best is to do:
cd test/encodings/
../run_test.sh japanese

the result is in out/japanese/japanese.html.

Help please!

For the record here is the original mail from Reinhold:

Recently, a Japanese guy decided to start translating the LilyPond
documentation to Japanese. It basically works with texi2html (texi2pdf doesn't
even handle Japanese glyphs at all!), however, we are running into a problem
with the navigation bars:

The strings are translated, but unfortunately they are not written out in
UTF-8 to the html file, but in some other encoding (I couldn't find out which,
none of the three major Japanese non-utf-8 encodings seems to fit!). For
example, the [Top] link in the navbars is displayed as [å†’é ] (that's an a
with a ring diacritic above, a dagger, an apostrophe and an e with an acute
accent) instead of the correct two-glyph [冒頭].

An example (.texi file to be run as "texi2html japanese.texi" and the
resulting .html file) is attached.

--
Pat

From forum: Gnu - Texinfo - Bugs

Re: problem with @verbatiminclude

2009-11-15T15:43:33Z

Hi John,

Sorry for the delayed reply.

@set srcdir foo+
@verbatiminclude @value{srcdir}/foo

I'm not surprised it fails. I'll look into it as soon as I have a
chance. (Oleg, if you have any chance to do so, that'd be great.)

Thanks,
Karl

From forum: Gnu - Texinfo - Bugs

Re: texinfo 4.12 and 4.13 don't run on Solaris 10

2009-11-15T14:02:19Z

Hi Bob,

% /usr/local/bin/texi2dvi --version
/usr/local/bin/texi2dvi: local: not found

Attached is the version from CVS. It tries to solve this problem.

Best,
Karl

texi2dvi (76K) Download Attachment

From forum: Gnu - Texinfo - Bugs

texinfo 4.12 and 4.13 don't run on Solaris 10

2009-11-14T10:25:09Z

This is the behavior I see under Solaris 10 with recent texinfo and
the many recent Solaris 10 /bin/sh patches applied:

% /usr/local/bin/texi2dvi --version
/usr/local/bin/texi2dvi: local: not found
texi2dvi (GNU Texinfo 4.13) 1.135

Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

% /usr/bin/bash /usr/local/bin/texi2dvi --version
texi2dvi (GNU Texinfo 4.13) 1.135

Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

The installed shell scripts are unusable as is.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/

From forum: Gnu - Texinfo - Bugs

problem with @verbatiminclude

2009-11-11T10:05:32Z

Hi,

I'm using texinfo.tex version 2008-04-18.10 from the 4.13a.dfsg.1-5
texinfo package on a Debian system.

Given the following input file,

\input texinfo
@setfilename foo.info
@set srcdir foo+
@verbatiminclude @value{srcdir}/foo
@bye

and a subdirectory called foo+ that contains a file foo (could be
empty) so that I would expect the @verbatiminclude command to succeed,
I see the following error when I process the file with tex:

$ tex foo.texi
This is TeX, Version 3.141592 (Web2C 7.5.6)
(./foo.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2008-04-18.10]: pdf, fonts, page headings, tables,
conditionals, indexing, sectioning, toc, environments, defuns, macros,
cross references, insertions,
(/usr/share/texmf-texlive/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.3 <23 July 2005>
) localization, formatting, and turning on texinfo input format.) (./foo.aux)
! I can't find file `foo{'.
<to be read again>
@fam
@tt ->@fam
=@ttfam @setfontstyle {tt}
+->{@tt
@char 43}
@value ... not set.}@else @csname SET#1 at endcsname
@fi
<argument> @value {srcdir}
/foo
@doverbatiminclude ...ble @setupverbatim @input #1
@afterenvbreak }
l.7 @verbatiminclude @value{srcdir}/foo

Please type another input file name:

I also happened to notice that if I comment out the "@setfilename
foo.info" line it works, and of course it works if the directory name
does not include a "+" character.

The makeinfo program can process this either way. My version of
makeinfo is from the same Debian texinfo package.

jwe

From forum: Gnu - Texinfo - Bugs

Re: Re: Gentoo Linux some `Info' manuals missing index

2009-11-02T20:08:55Z

> Date: Mon, 2 Nov 2009 16:54:12 -0600
> From: karl@... (Karl Berry)
> Cc:
>
> Harry, if you can, please try emacs-23.1. Not emacs-23.1.50.
> That will eliminate the prime variable of the Emacs version.

Sorry, I didn't realize that a development snapshot of Emacs was
used. Yes, that's another possible factor. As I said, stock 23.1
works for me.

Nabble - Gnu - Texinfo

Re: Problematic indentation in HTML output of makeinfo

Top

Re: Problematic indentation in HTML output of makeinfo

Top

Re: Problematic indentation in HTML output of makeinfo

Problematic indentation in HTML output of makeinfo

Need help for the japanese document errors

Re: problem with @verbatiminclude

Re: texinfo 4.12 and 4.13 don't run on Solaris 10

texinfo 4.12 and 4.13 don't run on Solaris 10

problem with @verbatiminclude

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Adding info documents to /usr/share/info

Re: Gentoo Linux some `Info' manuals missing index

Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Gentoo Linux some `Info' manuals missing index

Re: Adding info documents to /usr/share/info

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Looking for TeX/LaTeX gurus help

Re: Looking for TeX/LaTeX gurus help

Re: Looking for TeX/LaTeX gurus help

Re: Looking for TeX/LaTeX gurus help

Re: Gentoo Linux some `Info' manuals missing index

Re: Looking for TeX/LaTeX gurus help

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Looking for TeX/LaTeX gurus help

Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Gentoo Linux some `Info' manuals missing index

Re: Re: Gentoo Linux some `Info' manuals missing index

Re: Gentoo Linux some `Info' manuals missing index

Re: & in definitions, title