On Fri, Jul 20, 2012 at 08:59:57PM -0700, Per Bothner wrote: > > <synopsis><indexterm > role="fn"><primary>make-process</primary></indexterm><emphasis > role="bold">Procedure</emphasis>: <function>make-process</function> > <replaceable>command</replaceable> > <replaceable>envp</replaceable></synopsis> > > This is a lot harder to deal with. There is no semantic information encoded > in the structure, just in the text. Nothing to indicate that the word > "Procedure" has special meaning. I.e. the translation has lost information. > Furthermore, getting rid of the colon is likely to be ugly,
I agree with the diagnostic. What about dropping completly the colon? Also I don't find a class attribute for phrase. Shouldn't it be role instead? > So I'd like to suggest the attached fix. It's simple, localized, and I've > verified that adjusting the xslt stylesheet is straightforward. > -- > --Per Bothner > [email protected] http://per.bothner.com/ > 2012-07-20 Per Bothner <[email protected]> > > * tp/Texinfo/Convert/DocBook.pm: Add phrase element around category, > for easier processing of the output. > > Index: tp/Texinfo/Convert/DocBook.pm > =================================================================== > RCS file: /sources/texinfo/texinfo/tp/Texinfo/Convert/DocBook.pm,v > retrieving revision 1.46 > diff -u -r1.46 DocBook.pm > --- tp/Texinfo/Convert/DocBook.pm 14 Jul 2012 11:41:55 -0000 1.46 > +++ tp/Texinfo/Convert/DocBook.pm 21 Jul 2012 03:48:15 -0000 > @@ -1178,7 +1178,7 @@ > if ($type eq 'spaces' or $type eq 'delimiter') { > $result .= $content; > } elsif ($type eq 'category') { > - $result .= "<emphasis role=\"bold\">$content</emphasis>:"; > + $result .= "<phrase class=\"category\"><emphasis > role=\"bold\">$content</emphasis>:</phrase>"; > } elsif ($type eq 'name') { > $result .= > "<$defcommand_name_type{$main_command}>$content</$defcommand_name_type{$main_command}>"; > } else {
