12 questions for FIXMEs

[Patrice Dumas]

Hello,

I have taken care of all the FIXME in tp I wanted to fix myself, some remain
that I don't want to fix right now, but for some I'd like your advice...

Here they are:


1. For --internal-links output, it is possible to output only if there are 
links, or always, maybe creating an empty file.  (Right now it is only 
output if there is something to output).

Which one is better?


2. Should there be a warning when an obsolete customization variable is 
accessed, or set? (like 'TOP_HEADING_AT_BEGINNING', 'USE_NLS'...).


3. For raw commands, like @verbatim, @macro body, @ignore, @html...
right now the regexp to find them is 

 /^(.*?)address@hidden([a-zA-Z][\w-]*)/ 

Should it be stricter, like 
   begin only at line beginning?
   only one space after @end?


4. Should something that remains after an @end ifhtml and similar command
on the like be ignored?  Or should there be an error message?  I think that
a @comment is valid, so not doing anything and keeping what is on the
line as is now and putting a comment in the code may be enough.


5. There is a new error message if the highest sectioning element before 
a @part is not at the chapter level, could you please check it:
  "No chapter-level command before address@hidden"


6. Should 'Prev', 'Next', 'Up' appearing in the error message
 "%s reference to nonexistent `%s'" 
(first %s, second is a node name) be translated?


7. For the 'Up' direction which is normally associated with sectioning command
when there is no such direction, the node up direction is used (the up node
directions is always associated with the 'NodeUp' direction).  Is it right
(I guess this one is a bit tricky...)


8. In most cases, @error{} leads to error-> or similar output.  Should the
error word be translated?


9. Right now @inforef is formatted in DocBook as in Info.  (like 
*note (file)node::).  It seems wrong to me.  How should it be formatted?


10. when doing HTML, the @image extension is tried first without . and then
with .:
      unshift @extensions, ".$extension";
      unshift @extensions, "$extension";
Is it right?


11. when TOP_NODE_FILE is not set (it is set to 'index' in the default case),
and output is SPLIT the top node file name is set to the document name, 
based on setfilename or the manual file name without extensions.  Is it right?
Another possiblity would be to do the same as for other nodes (and elements),
in that case the section name may be used, or the node name, or something 
along document_name-0.  What should be the right thing?



12. Should definition line formatting in Info/Plaintext be internationalized?
Currently it is 
' -- '.definition_category . ': ' . type . name address@hidden
With definition_category internationalized like gdt('{category} on {class}')
or gdt('{category} of {class}').
It could be along 
gdt(' -- {category} of {class}: {type} {name} {arguments}')


-- 
Pat