Re: [bug #45759] Can't find Texinfo::ModulePath
On Mon, Aug 17, 2015 at 09:13:10PM +, Karl Berry wrote: > TEXINFO_XS=stand-alone > > Please, no hyphen. Just "standalone" looks nicer. > > Yours for trivialities, Ok. -- Pat
Re: DTD version confusion
On Sun, Mar 01, 2015 at 10:23:32PM +, Karl Berry wrote: > +check-dtd-changes: > + $(MKDIR_P) tp/maintain > + (cd tp/maintain && wget -N > http://www.gnu.org/software/texinfo/dtd/$(TEXINFO_DTD_VERSION)/texinfo.dtd) > > Sorry, in all this lengthy back and forth, I don't understand what > problem needs to be solved. Did we forget to update something in 5.2? Yes, TEXINFO_DTD_VERSION should have been set to 5.2. More precisely, texinfo.dtd should have been compared with the 5.0 texinfo dtd, to determine if there are differences that require TEXINFO_DTD_VERSION to be set to the current version, here 5.2. -- Pat
Re: real subscripts and superscripts?
On Sat, Nov 22, 2014 at 07:08:48PM +0100, Dumas Patrice wrote:
> On Wed, Nov 19, 2014 at 11:07:04PM +, Karl Berry wrote:
> > Maybe I would favor using x^{2}y in textual context too, since there is
> > no good solution, and it is simpler to implement and explain ...
> >
> > Ok by me. Doing the simple way (always add braces) first seems
> > reasonable; if it turns out that the feature gets used enough and people
> > really don't like it, the output can always be tweaked later.
> >
> > I can add these to texinfo.tex and texinfo.texi, etc., easily enough.
> > Do you have time to add it to makeinfo?
>
> Yes. For HTML cross manual I propose doing the same as for "style"
> commands and key and kbd, that is replace by the content.
Also in raw text, I propose using content as is without any formatting
(used for instance for file names, for index sorting).
--
Pat
Re: real subscripts and superscripts?
On Wed, Nov 19, 2014 at 11:07:04PM +, Karl Berry wrote:
> Maybe I would favor using x^{2}y in textual context too, since there is
> no good solution, and it is simpler to implement and explain ...
>
> Ok by me. Doing the simple way (always add braces) first seems
> reasonable; if it turns out that the feature gets used enough and people
> really don't like it, the output can always be tweaked later.
>
> I can add these to texinfo.tex and texinfo.texi, etc., easily enough.
> Do you have time to add it to makeinfo?
Yes. For HTML cross manual I propose doing the same as for "style"
commands and key and kbd, that is replace by the content.
--
Pat
Re: makeinfo bug
On Thu, Aug 21, 2014 at 10:30:44PM +, Karl Berry wrote: > Also, I am not sure we should add a test for it. If we do, then we > should also add a test for every command-line option and I am not > sure we want that. > > Why not? > > Anyway, I don't think we're necessarily obliged to test every single > cmdline option, and it wouldn't even be possible to test every > combination. But I see no particular reason not to add tests to make > sure bugs don't come back. Ok, but I think that there is no reason for a specific command line option related bug to come back, in contrast with bugs in parsing/converting. Bug related with command line options, in general, are not caused by interactions with other changes, and therefore should not be prone to regressions. -- Pat
Re: makeinfo bug
On Thu, Aug 21, 2014 at 10:30:45PM +, Karl Berry wrote:
> except that I would have placed it a bit later. I'll do it and commit.
>
> 1) It seems your patch did not remove my block, so now those four lines
> are in two places.
Are you sure it isn't a local non commited modification?
>
> 2) In fact, I originally tried putting it later in the fn, which looks
> more natural given the existing code. However, I found that it does not
> have any effect if it is any later than it is. Experimentally, I
> determined that it has to be before the line:
> $self->push_top_formatter('_Root_context');
Indeed you are right. I didn't test enough... I changed the location
of $self->push_top_formatter('_Root_context'); instead. Thanks! I
commited the change.
Since I used you in the log it will be as if you did the mistake though
;-)
--
Pat
Re: @part command and docbook
On Tue, May 13, 2014 at 11:37:07PM +, Karl Berry wrote: > > No warning for HTML, as well as docbook, sounds right to me. Done. -- Pat
Re: @part command and docbook
On Mon, May 05, 2014 at 11:43:20PM +, Karl Berry wrote: > > Does that work? That seems to me to best reflect the reality of the > situation, which is that "partintro" text is a Docbook feature, not > supported in Texinfo. > > - we revisit the "no text after @part" rule and decide something > for Info. I think that the best would be simply ignore text > > If the above works for Arnold ... how about giving a warning if there is > text after @part? (Then I don't have a preference as to whether it is > ignored or not ignored.) But then the solution you (or I, in the other mail) propose with @docbook ... @end docbook would trigger the warning. Is it what you have in mind? -- Pat
Re: @part command and docbook
On Tue, May 06, 2014 at 09:59:20AM +0300, Aharon Robbins wrote: > Hi Karl and Patrice. > > > How about: > > > > @part Part Title > > @docbook > > intro to part blah blah > > @end docbook > > > > Does that work? That seems to me to best reflect the reality of the > > situation, which is that "partintro" text is a Docbook feature, not > > supported in Texinfo. > > It probably works, but it means I have to write all the > text in docbook instead of in Texinfo. I tried various bits > with @inlinefmt but then the got wrapped inside > tags and that was totally wrong. Doesn't the following work: @part A nice part @ifdocbook @docbook @end docbook The part is very nice. @docbook @end docbook @end ifdocbook > Is it reasonable to require that text after @part and before @chapter be > wrapped in @ifdocbook and then makeinfo can supply the tags? I think that there should be no situation in which we document that @if* commands should be used to use a Texinfo feature. There is only one such occurrence for now, for the titlepage, and I think that it should not be that way. > 1. Require and document that @part and following text be wrapped > in @ifnotinfo. Same as above, I don't think that we should ever propose to the user in the Texinfo manual format conditionals for standard Texinfo language features. > 4. makeinfo --docbook supplies tags. That being said, I still think that it could make sense to supply tags to get valid DocBook, even if the Texinfo is invalid, but I leave that decision to Karl. -- Pat
Re: @part command and docbook
On Sat, Apr 26, 2014 at 11:15:45PM +0300, Aharon Robbins wrote: > Hi Patrice. > > Me: > > > Right now if I use @docbook, I'm getting: > > > > > > > > > introductory blah blah here > > > > > > < these are from what came before the part > > > > > > > > >... > > > > > Patrice: > > That looks like a bug, the DocBook produced does not even seem to be > > valid? I am missing something? > > So, I misspoke. I get the above if I manually insert the docbook. But, > if I use @part, makeinfo does produce mostly correct docbook. > > There is one issue, which is the lack of tags. I had to > manually insert them around all the text between the @part and the > first @chapter. If makeinfo would insert them for me, I would be set. > > So, we might be able to have a happy ending after all. :-) Indeed, it even seems mandatory to product valid DocBook to have the text before the chapter be in . It may not be that easy to avoid producing empty , but aside from that it could be doable as the @part indeed has the text associated in the internal texi2any tree. But I still have a reservation, as it seems to me that the Texinfo would be invalid. Indeed, in the Texinfo manual, there is Because parts are not associated with nodes, no general text can follow the '@part' line. To produce the intended output, it must be followed by a chapter-level command (including its node). makeinfo/texi2any has no trouble parsing and even processing the Texinfo output. HTML output is good, but Info output is rather ugly because the part text is associated to the previous node, so appears after the previous node menu. And it makes complete sense because it is before the @node. Texi2dvi adds a full page for the text after @part, it is acceptable, I think. It is possible to produce better Info by using a construct like @node node before part @path the part In the part text @chapter Some chapter but it is still invalid and even leads to a warning stating that part cannot be associated to nodes. Here is what I propose: * in any case, add in DocBook output * decide whether - we revisit the "no text after @part" rule and decide something for Info. I think that the best would be simply ignore text between @part and the next @node/@chapter instead of putting it as part of the previous node. This means that the trick I proposed above with the warning would not work as expected anymore. - we do not change anything for the other formats Karl and others, opinions? -- Pat
Re: texinfo to docbook conversion - @r{} is not
On Mon, Feb 03, 2014 at 10:05:15PM +, Karl Berry wrote:
> >
>
> I agree. It is something I blindly took from makeinfo 4, but I agree
> that it doesn't make much sense.
>
> It was done because of the original use for @r, inside @example.
>
> @example
> x = 1; @r{some comment}
> @end example
But there is no reason why @r{} would only be used like that, even in a
@example and similar environments. If we really want something like
that I think that we should add a command similar with lineannotation
(that could be called anything) that would be rendered like @r, except
in DocBook.
--
Pat
Re: "special" spaces in Texinfo parsing and output
On Sun, Mar 24, 2013 at 06:42:37PM +, Karl Berry wrote: > > Consider [\r\n\t ] to be space characters? That's what seems like the > simplest and most expected result to me. That's not what I would expect. I would expect any unicode space to be treated as a space with respect to word and paragraph breaking. For feed is very different, I would expect it to be kept and not to be considered as a space, but as a 'ghost' character that is kept in any case, but is not a space nor a non space character. Yet, considering [\r\n\t ] only to be space characters and everything else to be non-space, treated as letters would simplify my life. > Do something different for parsing or is it ok to have all the space > like characters be considered as spaces? > > No, it's not ok. That's what occasioned the report in the first place > -- we don't want to lose form feeds. But, should space character, including form feeds simply be considered as not space, or should they be considered differently? > And for the output? Break words only at [\r\n\t ]? > > Sounds right to me. As Eli said, it seems reasonable to have a conf > variable to allow people to make their own. Maybe. Ok. > Keep the first space character only if it is not [\r\n]? > > I'm not sure what you mean. Suppose we have a text with a '* SPACE' what should be done at the end of a line, could it be replaced by a new line? Or if there is a space following or preceding the '* SPACE'? Should the '* SPACE' simply be considered as a normal character? Should it be considered that it has a simple width but a line may be broken right after it as for fullwidth east asian characters? > However, we don't really want to implement the semantics of the Unicode > space characters, let alone the full Unicode line-breaking algorithm, I > feel sure. At least not right now. That's another whole major project. > Just for example, there are other characters which end a sentence in > Unicode too ... http://www.fileformat.info/info/unicode/char/3002/ > etc. It's endless. Not necessarily, there is already some special handling of fullwidth east asian characters, and of all the Texinfo control of spacing, thus it may turn out not to be overly complex. That being said, I won't do it unless told to... > Meanwhile, if someone declares us-ascii but then uses non-ascii > characters, that's not our problem. It would be nice to output them > as-is instead of losing them (that's what C makeinfo did, I believe), > but I wouldn't say even that is 100% mandatory. I'd say that we let perl have its way. What would have been nice would have been to be able to catch perl error message and replace it by something more consistent with the other error messages and a proper accounting of line number, but I don't know how to do that. -- Pat
Re: some more itching msgids
On Sun, Dec 30, 2012 at 01:59:56PM +0100, Andreas Schwab wrote: > k...@freefriends.org (Karl Berry) writes: > > > > msgid "tex4ht error opening %s: %s" > > > > Based on your description, how about: > > tex4ht.pm failed to open %s: %s > > GNU standard would be: > > tex4ht.pm:%s: cannot open: %s I am not sure about that. Indeed, it is said: Error messages from other noninteractive programs should look like this: program:sourcefile:lineno: message when there is an appropriate source file, or like this: program: message But, in that case, the file that cannot be opened is not a source file, rather it may be a generated intermediate file or an output file. So it seems to me that the condition "when there is an appropriate source file". Now, if "when there is an appropriate source file" is in fact to be interpreted as "when there is an appropriate file" more generally, then ok, but is it really the case? -- Pat
Re: Texinfo pre 4.13.92: make check error
On Mon, Dec 31, 2012 at 07:10:07PM +0100, Jean-Charles Malahieude wrote: > > The results are equivalent in both cases. > I first tried with a modified fr.us-ascii.po and because of check's > abortion, reserved my work somewhere else and nuked my build > directory. > > I then retried with the tarball I grabbed on the FTP yesterday, with > the same unfortunate result. Indeed, the diff does not sseem to come from translated strings in document but from an error message: -glossary.texi:47: Unmatched `@end table' (possibly involving @glossary) +glossary.texi:47: ?? @end table ?? non appari?? (possibly involving @glossary) I cannot reproduce it, though, I'll have to investigate. > BTW, I'm reviewing po/fr.po and will submit it to JP Guérard for > uploading to the FTP (that will be next year). Thanks. -- Pat
Re: some more itching msgids
On Sun, Dec 30, 2012 at 01:59:56PM +0100, Andreas Schwab wrote: > > GNU standard would be: > > tex4ht.pm:%s: cannot open: %s I tried to improve tex4ht.pm and chm.pm error messages along those lines. Thanks! -- Pat
Re: texinfo-4.13.90 pretest available
On Mon, Nov 19, 2012 at 09:13:34PM +0100, Werner LEMBERG wrote: > > > As far as I have understood TeX will always accept this kind of > > construct and cannot be made to error on it, but the idea was to > > forbid it in makeinfo/texi2any. > > Why? What's the benefit? That allows to find those kind of invalid constructs, user will be able to fix them. Among the advantages of not having additional spaces there is simpler parsing and less information to keep in the tree or in the texinfo XML output. -- Pat
Re: [bug #35451] texi2any does not place output in the right place under MSWindows
On Sun, Feb 05, 2012 at 06:06:55PM +0100, Vincent Belaïche wrote: > >> > > > >The easiest way to fix this is to convert the argument to forward > >slashes right from the start (on Windows). Then the rest of the > >script doesn't need to know about backslashes. > > > > > > > > Yes, this one simple way to do it. Another way is to use only library > functions to manipulate filenames. There exists such kind of functions > in Java or in Elisp, there must be the counterparts in Perl (I am not > familiar with Perl, but I cannot imagine that this does not exist). > Personally I would prefer to use library functions, that sounds more > portable/futureproof. There are such library functions, in File::Spec. -- Pat
Re: Include paths for makeinfo
On Wed, Dec 21, 2011 at 02:35:33PM -0800, Karl Berry wrote:
> It looks at
> ('eps', 'gif', 'jpg', 'jpeg', 'pdf', 'png', 'svg');
>
> HTML output, there's no real use in linking to an eps or a pdf as an
> image in html output, is there? Browsers will not render them as an
> image within the page (at least not that I've ever seen), which is what
> is desired.
No, this is the list for docbook, not html. For html, it is only
('.png', '.jpg')
> Or maybe svg should come before all the bitmap formats. I'm not
I could add svg for html, but it is still undecided.
> Now, Docbook might be a different story since people convert that to
> other formats. (Is Docbook XML viewable directly?)
Yes, yelp, for instance, does that.
> So maybe pdf+eps
> should come first in that case:
> pdf eps png jpg jpeg gif svg
In docbook all the file found are given.
> I think it is better to provide both if possible, for accessibility,
>
> For both HTML and Docbook ... does a .txt form of an image really mean
Nope, only for Docbook. For HTML the alt tag is used, but no .txt.
> anything for accessibility? I don't see it. ASCII art is not
> accessible. The verbal descriptions useful for accessibility should be
> in the alt tag.
There is no alt tag in docbook, as far as I can say, but the .txt plays
that role within the .
--
Pat
Re: [bug #11700] rfe: diagnose references which produce wrong title in pronted output
On Thu, Feb 17, 2011 at 12:49:58AM +, Karl Berry wrote: > @refautomaticsectiontitle > would be better since it applies to all the @*ref commands and @ref seems > more generic than @xref? > > I thought about that too. Maybe. I'm not sure. We seem to use "xref" > to generically mean "cross-reference" in other cases. For instance, the > whole cross-references chapter is basically written around @xref, and > then describing the others in terms of how they differ. And "xref" does > somehow distinguish Texinfo cross-references from other kinds of > references, namely url "references" via @uref/@url. > > I dunno, I can go either way. Wdyt? Me too, no preference. Let's go for @xrefautomaticsectiontitle -- Pat
Re: [bug #11700] rfe: diagnose references which produce wrong title in pronted output
On Mon, Feb 14, 2011 at 12:16:57AM +, Karl Berry wrote: > > Maybe there could be a command along > @setxrefautomaticsectiontitle > > I don't think we need the "set" in the name, just > @xrefautomaticsectiontitle Maybe @refautomaticsectiontitle would be better since it applies to all the @*ref commands and @ref seems more generic than @xref? -- Pat
Re: macro bug in CVS makeinfo
On Tue, Dec 28, 2010 at 10:07:34PM +0100, Werner LEMBERG wrote: > > Is the new parser available already? I'm going to make a new groff The Parser is certainly ready, but the Converters are not done. Info is almost done, though not debugged. -- Pat
Re: makeinfo and expansion of @html in section name
On Tue, Jun 17, 2003 at 06:36:58PM -0400, Karl Berry wrote: > @section macro expanded @html > html text > @end html > > This isn't allowed. @html is a multiline command and @section's > argument has to be on one line. So they're fundamentally incompatible. > (You couldn't put an @example or any other environment in a @section > title either.) > > So I'm not sure there's a bug here? I totally agree, this shouldn't be allowed. And when generating info makeinfo rightly disagree: makeinfo_macros_expand_section.texi:17: Expected ` @end html'. makeinfo_macros_expand_section.texi:17: Unmatched [EMAIL PROTECTED]'. But when generating html there is no error, I think that there should be the same error than for makeinfo producing info. In fact a more precise error message like "No multiline command allowed in @section" would even be better but that would be a must. Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
makeinfo and expansion of @html in section name
Hi, I use texinfo-4.5. This is a bug report similar to Akim's one. @html in section name isn't handled the same when in macro expansion or not. I call makeinfo with html generation: makeinfo --html makeinfo_macros_expand_section.texi I have the following macro: @macro bidule @html html text @end html @end macro I call it within a @section: @section macro expansion @bidule The resulting html is macro expansion html text When @html is put as is, like in @section macro expanded @html html text @end html the result is macro expanded html text although the result should have been the same. And when I call makeinfo without --html I get: [EMAIL PROTECTED] tmp]$ makeinfo makeinfo_macros_expand_section.texi makeinfo_macros_expand_section.texi:17: Expected ` @end html'. makeinfo_macros_expand_section.texi:17: Unmatched [EMAIL PROTECTED]'. makeinfo: Removing output file `makeinfo_macros_expand_section.info' due to errors; use --force to preserve. My personnal point of view is that the correct behaviour is this behaviour, that is, an error. A file with these constructs is attached. Pat makeinfo_macros_expand_section.texi Description: TeXInfo document ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
cross references in html, next
Hi,
Next proposal for cross references in html manuals.
Links are basically constructed using the pair (node name, manual).
A link consists in 4 components, an host name, a directories part, a
file name and a target part. The file is simply 'index.html'. The
target is constructed using the node name. The host and directories
are constructed using the manual name. Of course the host, directories,
file and target are to be used to construct an url
(like http://host/directories/index.html#target).
I first describe how to map the (node name, manual) to the 3 components
in the general case, and then fill the gaps in the case of the software
generating the cross reference (ie the software which tries to refer to
another manual) and the software generating the target.
expansion of @ commands
---
If the node name contains a @value or a user defined macro (defined with
@macro), they are expanded. Comments are also removed. @if* commands
are also supposed to be allready expanded.
@ commands in node names are not supported in makeinfo or texi2dvi, thus
it is adviced not to use them. However as they are not ruled out by design
of texinfo and as Karl said that maybe one day it will be supported, they
are included in this proposal for sake of completness.
The following @ commands are not allowed (ie the resulting file name is
unspecified):
@math, @menu, @afourlatex , @afourpaper, @afourwide, @alias, @anchor,
@node, sectionning commands (@headings, @section, @appendix..), @bye,
@center, @centerchap, @?index, @printindex, @*table, @columnfractions,
@contents, @shortcontents, @summarycontents, @cropmarks, @defindex,
@defcodeindexn, all the @deffn like commands, @example and the like,
@enumerate, @itemize, @definfoenclose, @dircategory, @direntry,
@document*, @titlepage, @exampleindent, @*footing, @*heading, @flush*,
@footnotestyle, @group, @include, @item, @itemx, @kbdinputstyle,
@raisesections, @lowersections, @macro, @*headings, @math, @need,
@pagesizes, @settitle, @setfilename, @author, @cartouche,
@set*contentsaftertitlepage, @*titlepage, @this*, @title, @titlefont,
@unmacro, @rmacro, @vskip, @verbatiminclude, @copying, @insertcopying,
@paragraphindent, @tex, @html, @verbatim, @today
and corresponding @end command.
Accented letters are transformed into their utf-8 equivalent character,
The following @ commands are transformed into text. I write the command, and
then what it should be transformed too. 'NOTHING' has a special meaning, it
means that the command is removed. If the command has braces and there is
something in the braces, the text in the braces is transformed, and then
the substituted command name is followed by a space and the transformed
text. For example '@bullet{a text}' leads to '* a text'. 'SPACE' means
a space.
@(space) SPACE
@(tab) SPACE
@(newline) SPACE
@* SPACE
@! !
@? ?
@. .
@: NOTHING
@tie SPACE
@equiv corresponding utf-8 character
@point -!-
@result =>
@expansion ==>
@print print -|
@error error-->
@exdent NOTHING
@noindent NOTHING
@page NOTHING
@refill NOTHING
@bullet *
@TeX TeX
@minus -
@copyright (C)
@dots ...
@enddots
@exclamdown utf-8 character
@questiondown utf-8 character
@pounds pounds utf-8 character
@@ @
@{ {
@} }
@- NOTHING
For the following @ commands, the @ command and braces are removed and
replaced with the text within argument which is recursively transformed:
@dotless, @acronym, @asis, @b, @command, @cite, @code, @dfn, @dmn, @emph,
@env, @file, @kbd, @key, @samp, @sc, @strong, @t, @var, @url, @w
For @sc letters are capitalized.
@email is replaced by the text, and if not present the mail adress.
@verb is processed as usual and replaced by the corresponding text.
The following @ commands shouldn't appear in node names, but, still for
completness, they are considered:
@uref is replaced by the third arg, or the second if not present or the first
@image is replaced by the first arg
@footnote and its argument are removed
@sp and the number following it are removed
@*ref is replaced by the first argument (the node name)
node name expansion
---
multiple spaces and tabs are transformed into just one space.
letters, numbers, and '-' ([A-Za-z0-9-]) are not modified.
ascii 7 bit characters are transformed into _xx where xx is the ascii
character in hexadecimal. '_' is itself mapped to _5f.
Other characters are transformed into _ where is the utf-8
code of the character in hexadecimal.
The letters in hexadecimal should be in lower case.
target generation
-
The target name is simply the expanded node name. The reason why only
[A-Za-z0-9-_] appear in expanded node names is that the targets are
in or in id= attributes, and only those characters are allowed
in xhtml. It is possible to have 2 different nodes expanding to
the same target name, if there are @ commands in node name (for example
@code{node} and @dfn{node} both leads to node).
construction of host and directories from m
Re: cross manual references in html manuals, second
> For our xref node name proposal, sure. But for Info output, right now > there is no utf-8 (or Latin 1, for that matter) output at all. Sorry, I think == is fine in info output too. Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: cross manual references in html manuals, second
> Maybe other people use it to express another kind of equivalence, but > it doesn't mean the same thing as ``='' or ``==''. > > It is certainly true that == and \equiv (the real symbol, three > horizontal lines) don't mean the same thing. However, we have to > transliterate \equiv into something for Info. I think the symbol `==' > is better than the word `equiv', although admittedly it's just my > opinion. Do you have another suggestion? Use the utf-8 character, similarly than @exclamdown or @pounds. Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: cross manual references in html manuals, second
> It is true that case is "preserved" (not significant) on Windows. > However, that is no reason why we should not generate file/target names > using uppercase letters. I think we should, just because it's closer to > the actual name of the code. For target, yes, but for filename it doesn't seems right to me. Indeed, imagine in a document there is 2 nodes differing only by case, say @node there and @node There If we are on windows, both will be in there.html. If we are on unix, one will be in There.html, the other in there.html. What to choose for the software doing the ref ? My idea was to use there.html as file name and distinguish with the target. Thus there -> there.html#there There -> there.html#There It doesn't matter, however (as far as cross manual references are concenrned) if we use only index.html as file name. In that case, as case is significant in targets, we don't have any problem. > > @today today > > Let's just disallow @today in node names. It doesn't make sense either way. You're right. Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: cross manual references in html manuals, second
> @verbatim, @tex, and @html are environments (with corresponding @end), > so they can't be included in node names. Right. > @verb, on the other hand, seems like it could be allowed. > It would just "expand" to its argument. Right too > Accented letters are transformed into their 8-bit equivalent character, > according to the iso latin 1 mapping. > > There are accented letters not in Latin 1. Perhaps we have use utf-8. Argh. This is quite annoying, as we then have to use an encoding of special chars like _ (if I'm not wrong about the number of hexadecimal characters used to describe an utf-8 character) for anything else than ascii 7bit. Not a real problem though, but it has to be fully acknowledged. > The following @ commands have no real reason to be used in node names, thus > it is recommended to use the plain text equivalent: > > I'm not sure what this means. I don't think it matters though. I was trying to say that people doing manuals should avoid using the @commands and use instead what will be expanded, for example people should avoid doing @node a @equiv b but rather write @node a == b > @equiv equiv OR == > ... > > I think the symbolic representation (==) would be better than the word > `equiv'. Right > @today today > > Should probably be the actual date. Hum. In node name expansion in documents, yes, but for cross reference to other manuals I think it is better not ot use the date of generation of manual as it has chances to be wrong. > @copyright (C) > ... > @exclamdown ! OR 8-bits equivalent > @questiondown ? OR 8-bits equivalent > @pounds pounds OR 8-bits equivalent > > The 8-bit character seems like the right thing for all of these. Or utf-8 if we go for utf-8 for accented characters. > I don't remember what the following does ;-) > @tie SPACE > > It produces an interword space at which a line break is not allowed. > Like ~ in plain TeX and LaTeX. Allright. > @email is replaced by the text, and if not present the mail adress. > > @email could appear in a node name as much as anything else. > > The letters in hexadecimal should be in small caps. > > Lowercase, not small caps. Of course, sorry for that mistake. In fact I mistaken caps for case everywhere in the proposal... (by the way don't hesitate to correct me, I am not a native english speaker, and that's pretty bad when I try to do formal proposals :). > (the local software may also skip the file name as browsers (or servers ?) > > Servers. Browsers just do `GET /' or whatever. It's up to the server > to decide whether to return index.html, or index.htm, or run index.cgi, > or whatever. (See the DirectoryIndex directive in Apache.) Right. > The manual name should only contain the following characters: > [A-Za-z0-9-_/], / having a special meaning. > > And `.', also with a special meaning. (For example, the Emacs manuals > say [EMAIL PROTECTED] ../info/emacs'; not that I think this is a good idea, > but it's the way it is.) Right. > and anchor names and generate a file per filename constructed as above. > > Really? I don't think we necessarily have to generate a file for every > node. (If that's the `filename constructed as above' that you mean.) > That would make --no-split impossible to implement, and users wouldn't > be happy about that. Argh. I specified that (a file per node) in order to avoid at best having to resort to javascript, and also for (a sort of) backward compatibility with what does makeinfo... But if you like better the other possibility it also has some advantages too. For example all the links are in a file, there are no unusefull files generated, we don't have to hassle with file names. > Instead, how about always generating the xref to the top level of the manual? > http://distant/manual/index.html#target > > In the no-split case, that will just work. If the distant manual is > split (in whatever way), then the distant software makes the above url > redirect (using your javascript method) to: > http://distant/manual/targetfile.html#target No problem. I will do another proposal, then. > Also makeinfo keeps the caps in file names. > Did I miss something? Don't we get to use both A-Z and a-z? Are you > proposing case-folding somewhere along the way? I didn't see that. If you look closely at my proposal, the files used only [a-z], as somebody said that on windows the case didn't matter. But it doesn't matter if the only filename really used is index.html. Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
cross manual references in html manuals, second
Hi,
New proposal for cross references in html manuals.
Links are basically constructed using the pair (node name, manual).
A link consists in 4 components, an host name, a directories part, a
file name and a target part. The file name and the target are constructed
using the node name. The host and directories are constructed using the
manual name. The host, directories, file and target are to be
used to construct an url (like http://host/directories/file#target).
I first describe how to map the (node name, manual) to these 4 components
in the general case, and then fill the gaps in the case of the software
generating the cross reference (ie the software which tries to refer to
another manual), thereafter called the local software, and the software
generating the cross reference target manual, called distant software.
expansion of @ commands in node names
-
If the node name contains a @value or a user defined macro (defined with
@macro), they are expanded. Comments are also removed. @if* commands
are also supposed to be allready expanded.
@ commands in node names are not supported in makeinfo or texi2html, thus
it is adviced not to use them. However as they are not ruled out by design
of texinfo and as Karl said that maybe one day it will be supported, they
are included in this proposal for sake of completness.
The following @ commands are not allowed (ie the resulting file name is
unspecified):
@math, @menu, @afourlatex , @afourpaper, @afourwide, @alias, @anchor,
@node, sectionning commands (@headings, @section, @appendix..), @bye,
@center, @centerchap, @?index, @printindex, @*table, @columnfractions,
@contents, @shortcontents, @summarycontents, @cropmarks, @defindex,
@defcodeindexn, all the @deffn like commands, @example and the like,
@enumerate, @itemize, @definfoenclose, @dircategory, @direntry,
@document*, @titlepage, @exampleindent, @*footing, @*heading, @flush*,
@footnotestyle, @group, @include, @item, @itemx, @kbdinputstyle, @raisesections
@lowersections, @macro, @*headings, @math, @need, @pagesizes,
@settitle, @setfilename, @author, @cartouche, @set*contentsaftertitlepage,
@*titlepage, @this*, @title, @titlefont, @unmacro, @rmacro, @vskip,
@verbatiminclude, @copying, @insertcopying, @paragraphindent
and corresponding @end command.
It also seems to me that @verbatim, @verb, @tex and @html should not be
allowed too, but I am not certain about these, however (especially @verb
and @html).
Accented letters are transformed into their 8-bit equivalent character,
according to the iso latin 1 mapping.
The following @ commands are transformed into text. I write the command, and
then what it should be transformed too. 'NOTHING' has a special meaning, it
means that the comand is removed. An 'OR' means that I am not certain which one
is the good one. If the command has braces and there is something in the
braces, the text in the braces is transformed, and then the substituted command
name is followed by a space and the transformed text. For example
'@bullet{a text}' leads to '* a text'. 'SPACE' means a space.
The following @ commands have no real reason to be used in node names, thus
it is recommended to use the plain text equivalent:
@(space) SPACE
@(tab) SPACE
@(newline) SPACE
@* SPACE
@! !
@? ?
@. .
@: NOTHING
@equiv equiv OR ==
@point point OR -!-
@result result OR =>
@expansion expansion OR ==>
@print print OR -|
@error error OR error-->
@exdent NOTHING
@noindent NOTHING
@page NOTHING
@refill NOTHING
@bullet *
@TeX TeX
@today today
@minus -
@copyright (C)
@dots ...
@enddots
@exclamdown ! OR 8-bits equivalent
@questiondown ? OR 8-bits equivalent
@pounds pounds OR 8-bits equivalent
The following cannot be avoided easily:
@@ @
@{ {
@} }
@- NOTHING
I don't remember what the following does ;-)
@tie SPACE
For the following @ commands, the @ command and braces are removed and
replaced with the text within argument which is recursively transformed:
@dotless, @acronym, @asis, @b, @command, @cite, @code, @dfn, @dmn, @emph,
@env, @file, @kbd, @key, @samp, @sc, @strong, @t, @var, @url, @w
For @sc letters are capitalized.
The following @ commands shouldn't appear in node names, but, still for
completness, they are considered:
@email is replaced by the text, and if not present the mail adress.
@uref is replaced by the third arg, or the second if not present or the first
@image is replaced by the first arg
@footnote and its argument are removed
@sp and the number following it are removed
@*ref is replaced by the first argument (the node name)
node name expansion
---
@ commands are expanded as above.
multiple spaces and tabs are transformed into just one space.
letters, numbers, and '-', are not modified.
All the characters other than [A-Za-z0-9-] are transformed into _xx where
xx is the ascii code of the character in hexadecimal. _ itself is also
mapped (to _5f). The letters in hexadecimal should be in small caps.
file name and targe
makeinfo segfaults with @itemize line with @item on the same line
Hi,
I triggered makeinfo from texinfo-4.5 to segfault with the following
construct:
@itemize @bullet @item on the same line that itemize
@item more text
@end itemize
Here is the output (... means repeated, up to a large number):
$ LANG=C;makeinfo bug_makeinfo.texi
bug_makeinfo.texi:24: @bullet expected `{...}'.
...
Too many errors! Gave up.
...
Segmentation fault
I tried to do a bt, but it is too long. There must be some recursion error.
I give the beginning of the bt, though:
(gdb) run
Program received signal SIGSEGV, Segmentation fault.
0x4007764c in vfprintf () from /lib/libc.so.6
(gdb) bt
#0 0x4007764c in vfprintf () from /lib/libc.so.6
#1 0x4007c4b2 in buffered_vfprintf () from /lib/libc.so.6
#2 0x400776d7 in vfprintf () from /lib/libc.so.6
#3 0x40081059 in fprintf () from /lib/libc.so.6
#4 0x080527e0 in remember_error () at makeinfo.c:342
#5 0x080526a3 in file_line_error (infile=0x806bab0 "bug_makeinfo.texi",
lno=23, format=0x80615dc "%c%s missing close brace") at makeinfo.c:261
#6 0x080551ae in discard_braces () at makeinfo.c:2193
#7 0x0804a9b3 in cm_bye () at cmds.c:1386
#8 0x080527ea in remember_error () at makeinfo.c:344
#9 0x080526a3 in file_line_error (infile=0x806bab0 "bug_makeinfo.texi",
lno=23, format=0x80615dc "%c%s missing close brace") at makeinfo.c:261
#10 0x080551ae in discard_braces () at makeinfo.c:2193
#11 0x0804a9b3 in cm_bye () at cmds.c:1386
#12 0x080527ea in remember_error () at makeinfo.c:344
#13 0x080526a3 in file_line_error (infile=0x806bab0 "bug_makeinfo.texi",
lno=23, format=0x80615dc "%c%s missing close brace") at makeinfo.c:261
#14 0x080551ae in discard_braces () at makeinfo.c:2193
#15 0x0804a9b3 in cm_bye () at cmds.c:1386
#16 0x080527ea in remember_error () at makeinfo.c:344
#17 0x080526a3 in file_line_error (infile=0x806bab0 "bug_makeinfo.texi",
lno=23, format=0x80615dc "%c%s missing close brace") at makeinfo.c:261
#18 0x080551ae in discard_braces () at makeinfo.c:2193
---Type to continue, or q to quit---
I attach the .texi file.
Pat
bug_makeinfo.texi
Description: TeXInfo document
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
$Id$ rcs/cvs tags in texinfo manual
Hi,
Maybe it is a feature, maybe not: in the texinfo manual, there are some
$Id$ strings in an example (and in index). They are modified each time the
manual is checked out. Maybe it could be desirable not to have those
strings modified. In that case there is a trick, add @asis{} before Id:
$@asis{}Id . $
Pat
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: does @setref command exists in texinfo ?
On Thu, Jan 23, 2003 at 10:06:19AM -0500, Karl Berry wrote: > Subject: does @setref command exists in texinfo ? > > Isn't this the functionality provided by @anchor? > http://www.gnu.org/manual/texinfo/html_node/anchor.html You are absolutely right, it is exactly that. Thanks Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
does @setref command exists in texinfo ?
Hi,
It is not a bug report but rather a question.
I have seen old things about a @setref command in texinfo, being only
implemented in tex. I had a look at texinfo.tex, and such a macro exists,
but it doesn't seems to be used from texinfo files (and makeinfo breaks
on it, and it is not mentionned in the texinfo manual), rather from
other macros. If I put something like @setref{ref}{Ynothing} I get
a reference in the dvi, but I think it is bad practice. Am I true ?
Thanks for your help.
Pat
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: bug? with texi2dvi and udotaccent in section
> Hope it'll be OK this time. It works well this time. No warning, no error and a perfectly right output (as far as I can see). Thanks ! Pat ___ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: bug? with texi2dvi and udotaccent in section
Hi,
I disclaim that I am quite ignorant about all that but it never hurts to
give an opinion...
> I fear that this is all leading nowhere, however. Even if we somehow
> special cased the accent commands so that they were really supported,
> the next problem would be that hyphenation didn't work. And I feel sure
> there are other problems as well.
Maybe, but all that is solved in TeX, ie with stuff like \'e you can
create absolutely correct documents, thus chances are it can be
solved here too.
> The only real way to support languages other than English is to allow
> real 8-bit input, I think, so preaccented letters can be used. The
> existing accent commands are just Knuth's kludge to allow accents in
> occasional foreign words in English.
I don't agree totally, as 8 bits characters are really hard to deal with
because they can be encoded in a lot of fashions. If you produce a
document in a given 8 bit locale, it will be unreadable with another
locale. You could specify the encoding within the document and let the
formating tools retrieve the informations, but I have no idea whether
it is harder to implement or easier than the kludges which allows to
use only well normalized 7 bit ascii. It seems that latex can handle
both cases (with \'e for 7 bits and \usepackage[latin1]{inputenc} for
use of 8 bits, here encoded with latin1)..
In my opinion using UTF8 would be an even superior approach because
it avoids the pitfalls of 7 bits (not enough characters) and 8 bits
(multiple encodings).
Anyway the required work may be different for the different approaches,
and I have no idea about what is easier/harder.
Pat
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: bug? with texi2dvi and udotaccent in section
Hi,
> OK, done. I'd be grateful if you test it.
It seems to work great. However there is a quote (") appearing
in every refs (not only the ones with accented characters).
For example:
(see Chapter"1 [ref to umlaut], page 2).
You can try to reproduce it with the texinfo file I attached.
> And, again, thank you very much for the bug report!
Reporting is relatively easy...
Thanks for the patches !
Pat
refsaccent.texi
Description: TeXInfo document
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: bug? with texi2dvi and udotaccent in section
Hi,
I have tested the new texinfo.tex, and it is fine for accented letters
in node names. Thanks for the fix !
However xrefs don't work, at least with acute accents, umlaut (") and
circonflex accents (^). makeinfo works well in these cases
(without any option).
(even with xrefs like @pxref{@^{@dotless{i}}, ,@^{@dotless{i}}} or
@pxref{@^{o}, , @^{o}} makeinfo produces the right output).
I atached a file showing those problems and the log too.
Pat
refsaccent.texi
Description: TeXInfo document
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=tex 2002.9.23) 14 JAN 2003 13:18
**/home/dumas/texinfo/refsaccent.texi
(/home/dumas/texinfo/refsaccent.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2003-01-12.11]: Basics,
\bindingoffset=\dimen16
\normaloffset=\dimen17
\pagewidth=\dimen18
\pageheight=\dimen19
\outerhsize=\dimen20
\outervsize=\dimen21
\cornerlong=\dimen22
\cornerthick=\dimen23
\topandbottommargin=\dimen24
\headlinebox=\box16
\footlinebox=\box17
\margin=\insert252
\EMsimple=\toks12
\groupinvalidhelp=\toks13
\mil=\dimen25
\exdentamount=\skip18
\inmarginspacing=\skip19
pdf,
\tempnum=\count26
\lnkcount=\count27
\filename=\toks14
\filenamelength=\count28
\pgn=\count29
\toksA=\toks15
\toksB=\toks16
\toksC=\toks17
\toksD=\toks18
\boxA=\box18
\countA=\count30
fonts,
\sffam=\fam8
\textleading=\dimen26
\mainmagstep=\count31
\fontdepth=\count32
page headings,
\titlepagetopglue=\skip20
\titlepagebottomglue=\skip21
\evenheadline=\toks19
\oddheadline=\toks20
\evenfootline=\toks21
\oddfootline=\toks22
tables,
\tableindent=\dimen27
\itemindent=\dimen28
\itemmargin=\dimen29
\itemmax=\dimen30
\itemno=\count33
\multitableparskip=\skip22
\multitableparindent=\skip23
\multitablecolspace=\dimen31
\multitablelinespace=\skip24
\colcount=\count34
conditionals, indexing,
\secondaryindent=\skip25
\partialpage=\box19
\doublecolumnhsize=\dimen32
sectioning,
\chapno=\count35
\secno=\count36
\subsecno=\count37
\subsubsecno=\count38
\appendixno=\count39
\absseclevel=\count40
\secbase=\count41
\chapheadingskip=\skip26
\secheadingskip=\skip27
\subsecheadingskip=\skip28
toc,
\tocfile=\write0
\contentsrightmargin=\skip29
\savepageno=\count42
\lastnegativepageno=\count43
\shortappendixwidth=\dimen33
\tocindent=\dimen34
environments,
\errorbox=\box20
\lispnarrowing=\skip30
\envskipamount=\skip31
\circthick=\dimen35
\cartouter=\dimen36
\cartinner=\dimen37
\normbskip=\skip32
\normpskip=\skip33
\normlskip=\skip34
\lskip=\skip35
\rskip=\skip36
\tabw=\dimen38
defuns,
\defbodyindent=\skip37
\defargsindent=\skip38
\deflastargmargin=\skip39
\parencount=\count44
macros,
\macscribble=\write1
\paramno=\count45
\macname=\toks23
cross references,
\auxfile=\write2
\savesfregister=\count46
\footnoteno=\count47
(/usr/share/texmf/tex/plain/dvips/epsf.tex
\epsffilein=\read0
\epsfframemargin=\dimen39
\epsfframethickness=\dimen40
\epsfrsize=\dimen41
\epsftmp=\dimen42
\epsftsize=\dimen43
\epsfxsize=\dimen44
\epsfysize=\dimen45
\pspoints=\dimen46
\epsfnoopenhelp=\toks24
)
\noepsfhelp=\toks25
localization,
\nolanghelp=\toks26
\defaultparindent=\dimen47
and turning on texinfo input format.) (refsaccent.aux)
@cpindfile=@write3
@fnindfile=@write4
@vrindfile=@write5
@tpindfile=@write6
@kyindfile=@write7
@pgindfile=@write8
()
\openout0 = `refsaccent.toc'.
Chapter 1 [1
\openout2 = `refsaccent.aux'.
\openout3 = `refsaccent.cp'.
\openout4 = `refsaccent.fn'.
\openout5 = `refsaccent.vr'.
\openout6 = `refsaccent.tp'.
\openout7 = `refsaccent.ky'.
\openout8 = `refsaccent.pg'.
]
! Missing @endcsname inserted.
@accent
@^#1->{@accent
94 #1}
@^{@dotless {i}}
-snt
@refx #1#2->@expandafter @ifx @csname X#1
@endcsname @relax @angleleft [EMAIL PROTECTED]
@xrefX ... = @hbox {@ignorespaces @refx {#1-snt}{}
}@ifdim @wd 2 > 0pt @refx ...
l.25 (@pxref{@^{@dotless{i}}, ,@^{@dotless{i}}}
).
?
! Missing @endcsname inserted.
@accent
@^#1->{@accent
94 #1}
@^{@dotless {i}}
-snt
@refx ... TeX again.}@fi @fi @fi @else @csname X#1
@endcsname @fi #2
@xrefX ... = @hbox {@ignorespaces @refx {#1-snt}{}
}@ifdim @wd 2 > 0pt @refx ...
l.25 (@pxref{@^{@dotless{i}}, ,@^{@dotless{i}}}
).
?
! Extra @endcsname.
@refx ...}@fi @fi @fi @else @csname X#1@endcsname
@fi #2
@xrefX ... = @hbox {@ignorespaces @refx {#1-snt}{}
}@ifdim @wd 2 > 0pt @refx ...
l.25 (@pxref{@^{@dotless{i}}, ,@^{@dotless{i}}}
).
?
! Extra }, or forgotten @endgroup.
@xrefX ...m @wd 2 > 0pt @refx {#1-snt}@space @fi }
Re: bug? with texi2dvi and udotaccent in section
Hi,
Now the only accent which still seems problematic is the accute accent.
Attached a simple texinfo file showing the bug, and the log. It would
be nice if it could be solved too.
Notice that the dvi outputed seems right.
Pat
nodeacute.texi
Description: TeXInfo document
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=tex 2002.9.23) 10 JAN 2003 15:36
**/home/dumas/texinfo/nodeacute.texi
(/home/dumas/texinfo/nodeacute.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2002-11-25.11]: Basics,
\bindingoffset=\dimen16
\normaloffset=\dimen17
\pagewidth=\dimen18
\pageheight=\dimen19
\outerhsize=\dimen20
\outervsize=\dimen21
\cornerlong=\dimen22
\cornerthick=\dimen23
\topandbottommargin=\dimen24
\headlinebox=\box16
\footlinebox=\box17
\margin=\insert252
\EMsimple=\toks12
\groupinvalidhelp=\toks13
\mil=\dimen25
\exdentamount=\skip18
\inmarginspacing=\skip19
pdf,
\tempnum=\count26
\lnkcount=\count27
\filename=\toks14
\filenamelength=\count28
\pgn=\count29
\toksA=\toks15
\toksB=\toks16
\toksC=\toks17
\toksD=\toks18
\boxA=\box18
\countA=\count30
fonts,
\sffam=\fam8
\textleading=\dimen26
\mainmagstep=\count31
\fontdepth=\count32
page headings,
\titlepagetopglue=\skip20
\titlepagebottomglue=\skip21
\evenheadline=\toks19
\oddheadline=\toks20
\evenfootline=\toks21
\oddfootline=\toks22
tables,
\tableindent=\dimen27
\itemindent=\dimen28
\itemmargin=\dimen29
\itemmax=\dimen30
\itemno=\count33
\multitableparskip=\skip22
\multitableparindent=\skip23
\multitablecolspace=\dimen31
\multitablelinespace=\skip24
\colcount=\count34
conditionals, indexing,
\secondaryindent=\skip25
\partialpage=\box19
\doublecolumnhsize=\dimen32
sectioning,
\chapno=\count35
\secno=\count36
\subsecno=\count37
\subsubsecno=\count38
\appendixno=\count39
\absseclevel=\count40
\secbase=\count41
\chapheadingskip=\skip26
\secheadingskip=\skip27
\subsecheadingskip=\skip28
toc,
\tocfile=\write0
\contentsrightmargin=\skip29
\savepageno=\count42
\lastnegativepageno=\count43
\shortappendixwidth=\dimen33
\tocindent=\dimen34
environments,
\errorbox=\box20
\lispnarrowing=\skip30
\envskipamount=\skip31
\circthick=\dimen35
\cartouter=\dimen36
\cartinner=\dimen37
\normbskip=\skip32
\normpskip=\skip33
\normlskip=\skip34
\lskip=\skip35
\rskip=\skip36
\tabw=\dimen38
defuns,
\defbodyindent=\skip37
\defargsindent=\skip38
\deflastargmargin=\skip39
\parencount=\count44
macros,
\macscribble=\write1
\paramno=\count45
\macname=\toks23
cross references,
\auxfile=\write2
\savesfregister=\count46
\footnoteno=\count47
(/usr/share/texmf/tex/plain/dvips/epsf.tex
\epsffilein=\read0
\epsfframemargin=\dimen39
\epsfframethickness=\dimen40
\epsfrsize=\dimen41
\epsftmp=\dimen42
\epsftsize=\dimen43
\epsfxsize=\dimen44
\epsfysize=\dimen45
\pspoints=\dimen46
\epsfnoopenhelp=\toks24
)
\noepsfhelp=\toks25
localization,
\nolanghelp=\toks26
\defaultparindent=\dimen47
and turning on texinfo input format.) (nodeacute.aux
! Undefined control sequence.
\@a
-title
@xrdef ...@endgroup @expandafter @gdef @csname X#1
@endcsname
l.7 'xrdef {\'a-title}
{\'a}
?
! Undefined control sequence.
\@a
-pg
@xrdef ...@endgroup @expandafter @gdef @csname X#1
@endcsname
l.8 'xrdef {\'a-pg}
{2}
?
! Undefined control sequence.
\@a
-snt
@xrdef ...@endgroup @expandafter @gdef @csname X#1
@endcsname
l.9 'xrdef {\'a-snt}
{Section'tie1.1}
?
)
@cpindfile=@write3
@fnindfile=@write4
@vrindfile=@write5
@tpindfile=@write6
@kyindfile=@write7
@pgindfile=@write8
()
\openout0 = `nodeacute.toc'.
Chapter 1 [1
\openout2 = `nodeacute.aux'.
\openout3 = `nodeacute.cp'.
\openout4 = `nodeacute.fn'.
\openout5 = `nodeacute.vr'.
\openout6 = `nodeacute.tp'.
\openout7 = `nodeacute.ky'.
\openout8 = `nodeacute.pg'.
] [2] (nodeacute.toc) [-1] )
Here is how much of TeX's memory you used:
1305 strings out of 23013
14084 string characters out of 222065
29250 words of memory out of 350001
2189 multiletter control sequences out of 1+15000
31953 words of font info for 111 fonts, out of 40 for 1000
19 hyphenation exceptions out of 1
12i,4n,10p,256b,213s stack positions out of 3000i,100n,1500p,5b,4000s
Output written on nodeacute.dvi (3 pages, 1784 bytes).
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
Re: bug? with texi2dvi and udotaccent in section
> texi2dvi seems to break on @udotaccent{a} in a @section.
>
> It's not the @udotaccent in the @section that's the problem, it's the
> one in the @node. You can't use @ commands in node names, they have to
> be simple text.
I see, but it is a bit inconvenient for languages with accented
characters... I don't know any language with udotaccent, but it must
exist, otherwise it won't be in texinfo ;-) (the texinfo I processed
was used for tests only).
> (Well, makeinfo has an option --commands-in-node-names to allow this,
> but it is fragile due to its nature, and it won't help with TeX
> processing, anyway.)
makeinfo even without any option process this right to create the info
file. And TeX accepts other kinds of accented characters, but I remember
that there were problems with accented characters in crossrefs. What
pushed me to do that report was that with other accented characters things
went more smoothly.
Pat
___
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
bug? with texi2dvi and udotaccent in section
Hi,
texi2dvi seems to break on @udotaccent{a} in a @section. I attached a file
demonstrating the problem, and the log produced by texi2dvi.
I use texinfo-4.3a, on a redhat 8.0, with the default tex distribution.
Pat
nodetest.texi
Description: TeXInfo document
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=tex 2002.9.23) 9 JAN 2003 10:57
**/home/dumas/texinfo/nodetest.texi
(/home/dumas/texinfo/nodetest.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2002-11-25.11]: Basics,
\bindingoffset=\dimen16
\normaloffset=\dimen17
\pagewidth=\dimen18
\pageheight=\dimen19
\outerhsize=\dimen20
\outervsize=\dimen21
\cornerlong=\dimen22
\cornerthick=\dimen23
\topandbottommargin=\dimen24
\headlinebox=\box16
\footlinebox=\box17
\margin=\insert252
\EMsimple=\toks12
\groupinvalidhelp=\toks13
\mil=\dimen25
\exdentamount=\skip18
\inmarginspacing=\skip19
pdf,
\tempnum=\count26
\lnkcount=\count27
\filename=\toks14
\filenamelength=\count28
\pgn=\count29
\toksA=\toks15
\toksB=\toks16
\toksC=\toks17
\toksD=\toks18
\boxA=\box18
\countA=\count30
fonts,
\sffam=\fam8
\textleading=\dimen26
\mainmagstep=\count31
\fontdepth=\count32
page headings,
\titlepagetopglue=\skip20
\titlepagebottomglue=\skip21
\evenheadline=\toks19
\oddheadline=\toks20
\evenfootline=\toks21
\oddfootline=\toks22
tables,
\tableindent=\dimen27
\itemindent=\dimen28
\itemmargin=\dimen29
\itemmax=\dimen30
\itemno=\count33
\multitableparskip=\skip22
\multitableparindent=\skip23
\multitablecolspace=\dimen31
\multitablelinespace=\skip24
\colcount=\count34
conditionals, indexing,
\secondaryindent=\skip25
\partialpage=\box19
\doublecolumnhsize=\dimen32
sectioning,
\chapno=\count35
\secno=\count36
\subsecno=\count37
\subsubsecno=\count38
\appendixno=\count39
\absseclevel=\count40
\secbase=\count41
\chapheadingskip=\skip26
\secheadingskip=\skip27
\subsecheadingskip=\skip28
toc,
\tocfile=\write0
\contentsrightmargin=\skip29
\savepageno=\count42
\lastnegativepageno=\count43
\shortappendixwidth=\dimen33
\tocindent=\dimen34
environments,
\errorbox=\box20
\lispnarrowing=\skip30
\envskipamount=\skip31
\circthick=\dimen35
\cartouter=\dimen36
\cartinner=\dimen37
\normbskip=\skip32
\normpskip=\skip33
\normlskip=\skip34
\lskip=\skip35
\rskip=\skip36
\tabw=\dimen38
defuns,
\defbodyindent=\skip37
\defargsindent=\skip38
\deflastargmargin=\skip39
\parencount=\count44
macros,
\macscribble=\write1
\paramno=\count45
\macname=\toks23
cross references,
\auxfile=\write2
\savesfregister=\count46
\footnoteno=\count47
(/usr/share/texmf/tex/plain/dvips/epsf.tex
\epsffilein=\read0
\epsfframemargin=\dimen39
\epsfframethickness=\dimen40
\epsfrsize=\dimen41
\epsftmp=\dimen42
\epsftsize=\dimen43
\epsfxsize=\dimen44
\epsfysize=\dimen45
\pspoints=\dimen46
\epsfnoopenhelp=\toks24
)
\noepsfhelp=\toks25
localization,
\nolanghelp=\toks26
\defaultparindent=\dimen47
and turning on texinfo input format.)
@cpindfile=@write3
@fnindfile=@write4
@vrindfile=@write5
@tpindfile=@write6
@kyindfile=@write7
@pgindfile=@write8
()
\openout0 = `nodetest.toc'.
Chapter 1 [1
\openout2 = `nodetest.aux'.
\openout3 = `nodetest.cp'.
\openout4 = `nodetest.fn'.
\openout5 = `nodetest.vr'.
\openout6 = `nodetest.tp'.
\openout7 = `nodetest.ky'.
\openout8 = `nodetest.pg'.
]
! Illegal parameter number in definition of @next.
@crcr
@oalign ...z@skip @lineskip .25ex@ialign {##@crcr
#1@crcr }}
@udotaccent ...idewidth @sh@ft {-1ex}.@hidewidth }
}
@lastnode
-title
@internalsetq #1#2->'xrdef {#1
}{@csname #2@endcsname }
@dosetq ...@write @auxfile {@internalsetq {#1}{#2}
}}@iflinks @next @fi }
...
l.17 @section @udotaccent{a}
?
! Illegal parameter number in definition of @next.
@crcr
@oalign ...z@skip @lineskip .25ex@ialign {##@crcr
#1@crcr }}
@udotaccent ...idewidth @sh@ft {-1ex}.@hidewidth }
}
@internalsetq ...'xrdef {#1}{@csname #2@endcsname
}
@dosetq ...@write @auxfile {@internalsetq {#1}{#2}
}}@iflinks @next @fi }
@setref ...dfmkdest {#1}@dosetq {#1-title}{Ytitle}
@dosetq {#1-pg}{Ypagenumbe...
...
l.17 @section @udotaccent{a}
?
! Illegal parameter number in definition of @next.
@crcr
@oalign ...z@skip @lineskip .25ex@ialign {##@crcr
#1@crcr }}
@udotaccent ...idewidth @sh@ft {-1ex}.@hidewidth }
}
@lastnode
-pg
@internalsetq #1#2->'xrdef {#1
}{@csname #2@endcsname }
@
