Re: a new release

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pat,

It will probably be this weekend before I get another chance to work on
this, so if you have time, go ahead and check in corrections for the
issues below.  I can review the english again when I get more time.

Dumas Patrice wrote:

|>Pat, if you wouldn't mind looking at the questions I've been leaving in
|>comments in the manual, I would appreciate it.  I've annotated all of my
|>questions with my initials (`DRP').
|
|
|About the node-files option ($NODE_FILES variable). It is true that files
|with the node name as file name are written for external manual cross refs
|in case this option is true.
|However the default is false for this option.


Hrm.  I thought the old version said that the _content_ would be in
nodes with $NODE_FILES set and otherwise the files would still be
generated but would only contain redirects.  Now that I think about it,
it makes sense that one is split and one is just file creation, but the
node will need to be rewritten again.

|--no-ifhtml is specified by using the --no-ifhtml command line switch. It
|cannot be specified in config file, though. Maybe we should change that by
|putting html in @EXPAND ? Any concern with that ?


I'm fine with that.  Especially as I just edited an earlier note in the
file that said there was an init file equivalent for each and every
command line option.  I think you said old init files are already broken
so we don't need to worry about this change being incompatible with them?

|default for --iso is false. Maybe we could set it to true in the
default case.
|It would be false for html3.2. It is allready true in xhtml.init.


This is fine by me.

It would be nice if more defaults could be noted in the manual too.
Preferably, the default behavior should be listed with every option and
variable we list.

|--css-include related stuff is badly explained. It is nicely explained in
|the texinfo manual and I didn't want to rewrite the whole explanation.
|
|For the '.' in temporary directory for latex2html, I have absolutely no
clue.
|Maybe Olaf knows the reason, or maybe we could look at the latex2html doc.


I haven't managed to get Olaf to respond to an email in years.  That's
why I moved texi2html to cvshome.org in the first place.

|>Finally, is there a good reason for the custhtml.texi and custpage.texi
|>sections being kept outside the texi2html.texi file?  Automake doesn't
|>know to update version.texi when those include files change.  It would
|>be easier to combine those files into texi2html.texi than to get the
|>Automake bug fixed, but maybe it is worth it?
|
|
|There is no good reason. I did it because the original manual was even
|more splitted. I see no problem in merging the files.
|
|I have a remark about your corrections.
|If we want to conform to the texinfo manual conventions, we should format
|variables like $SPLIT with @code and not with @var as @var (according to
|the texinfo manual) is specific for abstract variables (function
arguments).
|Should we conform with this style ? (it is really easy to change because
|it is in a @macro you rightly did).


Thanks.  I checked this fix in along with a fix for a problem in the
three macros which was causing odd spacing and placement requirements.

Derek

- --
~                *8^)

Email: [email protected]

Get CVS support at <http://ximbiot.com>!
- --
*                                                         *
- - Never look back.  The lemmings might be gaining on you. -
*                                                         *
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/jCFrLD1OTBfyMaQRAjmvAJ9KUmN2xa9TdBcAo/dXSAsUM7TPNgCg0FRi
g4jzwsKfk6fzPm4eyuomCOY=
=YJLo
-----END PGP SIGNATURE-----