Re: DAVENPORT: Re: bug reports and patches for Norman's modular stylesheets

[Norman Walsh <ndw@xxxxxxxxxx>]

/ Mark Galassi <rosalia@xxxxxxxxxx> was heard to say:
|     Norman> For folks who haven't seen the patches; what Mark is
|     Norman> proposing is that different elements of the funcsynopsis
|     Norman> (function, parameters, etc.) get different typographical
|     Norman> treatment.
| 
|     Norman> Straw poll, does this sound like a good thing to you?
| 
| My opinion, of course, is to mark up the text.  If not, we should at
| least make it a verbatim representation (so it resembles the code, as
| you say), and the DocBook reference pages should mention that
| whitespace and line breaks are relevant.  It should not look like a
| normal paragraph!

A funcsynopsis is theoretically capable of producing either K&R
style or ANSI style output, so I don't think making whitespace
significant would help.

| Also keep in mind that most programnming editors mark up the code
| these days.  Emacs uses colors or boldface/italics to highlight
| function names in the function's definition.

You're absolutely right.  Ok, markup it is ;-)

| But we can all win: how about a customization option that turns my
| pathces off?  At which point this straw poll would simply determine
| which option is the default :-)

Yep.

|       Mark> * Feature request: a configuration option to put numbers
|       Mark>   in all levels of sectioning.  I think that's really
|       Mark>   important: it's nice to give proofreaders a version with
|       Mark>   each <sect?> numbered.
| 
| >> >From dbparam.dsl:
| 
| >> (define %section-autolabel%
[...]
| 
| I looked at that, and I use it, but I think it only numbers <sect1>
| tags, but in proofreading software design docs (and sometimes even in
| released docs) it can be useful to reference all level of sections by
| this kind of numbering.

It's supposed to number all sections that don't have an
explicit LABEL attribute.  If I format xsections.sgm from the 
test directory with %section-autolabel% #t, I get:

Chapter 1. Section Tests
Section Tests Subtitle

Table of Contents
1.1. a sect1 title
1.2. another sect1 title

some text. some text. some text. some text. some text...

1.1. a sect1 title
some text. some text. some text. some text. some text...

1.1.1. a sect2 title
some text. some text. some text. some text. some text...

What do you get?

--norm


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist