[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: many questions
From: |
Patrice Dumas |
Subject: |
Re: many questions |
Date: |
Tue, 4 Aug 2009 00:55:09 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Mon, Aug 03, 2009 at 04:06:21PM -0500, Karl Berry wrote:
>
> * makeinfo in title, for @code{something} leads to `something'. In
> texi2html all the style commands are removed without extra formatting.
> Is it right?
>
> Given that @code leads to `...' in general, I don't see why it should
> simply be ignored in titles. It isn't ignored in titles in any other
> kind of output, so why in Info?
In fact I was very unclear. Here I am speaking about title in html
(and more generally strings in attributes in html, but also in @copying
comment). makeinfo formats this kind of text in html like text in
--plaintext or info, while texi2html has a simpler formatting. Which one
is better?
In any case, there is no such thing as a title in Info?
> * makeinfo don't warn for empty deffn, but texi2dvi cannot process them
>
> Well, that's a bug in texi2dvi. I'll take a look when I have a chance
> (or Oleg ... ?).
>
> should there be a warning?
>
> I presume texi2html can handle them ok, in which case I'd say, no
> warning (regardless of what we can do in texinfo.tex). Not everyone
> cares about processing through TeX.
I didn't meant a warning for TeX. But I think a warning would make sense,
in my opinion an empty @def* is almost surely a mistake, no?
> * the code of xml.c in makeinfo shows specific treatement of & in
> definition arguments. Could you please explain what it is meant to
> be?
No answer, here?
> * makeinfo warn when there is no @settitle nor @top. Guess it is for
> <title>
> texi2html uses @settitle @title @shorttitlepage @titlefont for <title>.
>
> What should be the best?
>
> texi2html's behavior is better.
Should @top be used if there is none of
@settitle @title @shorttitlepage @titlefont (I don't know)?
and if there is no title should there be a warning if producing html
(I believe so)?
> * What are the encodings known by info/makeinfo?
> unrecognized encoding name `ascii'.
>
> See the documentencoding node in texinfo.txi. US-ASCII, because that's
> what the HTML likes, as I recall. I did not put in the zillion possible
> synonyms and map them all to the HTML name that works.
Recent Perl do that (and I have a hash for most common older ones as well
as those from makeinfo). But what does the info reader support? Does it
support more than the encodings you listed?
> * should @OE{} be associated with '00D8' or '0152'?
>
> @OE{} is the OE ligature (analogous to @AE{} -> AE), so 0152.
>
> Isn't 00D8 "O with stroke" completely different? I don't understand ...
Ok, I am confusing things, let's forget about that, the issue is with
transliteration.
In makeinfo, @O{} is { "Oslash", 0xD8, 0x00D8, "OE" }, which means that it
is transliterated to OE. Is it on purpose that it is not O?
--
Pat