I've attempted to determine some information about the callout images used in fedora's documentation --- to no avail. So I bow to the mercy of the mailinglist and ask for help. What is the standardized styling and location of the callout images? I have built custom callouts for current development of my xml sources; but didn't want to stray from standard practice. Also I came across a peculiar problem declaring the xsl parameter using xmlto. For some reason due to the java implemented processor, I am getting a ColumnWidth error. The only alteration performed was to include an extension stylesheet for the declaration of a new image path. :-( Admittedly, I have never used xmlto and prefer xsltproc. However it might be a moot point if the standard path is acceptable. Thanks, Thomas

On Mon, 2005-05-16 at 11:46 -0500, Thomas Jones wrote: > > So I bow to the mercy of the mailinglist and ask for help. What is the > > standardized styling and location of the callout images? I have built > > custom callouts for current development of my xml sources; but didn't > > want to stray from standard practice. I have no previous experience with callouts, other than looking at how they're used in "DocBook:TDG." My chief concern with callouts would be the impaired-reader issue. How, if at all, do callouts affect readers who, for instance, are visually impaired and use audible reader software? I would think that if there is a way to avoid callouts that does not make the document overly cumbesome, it would be wise to do so.

AFAICT, there has not been a position taken on callouts. The impaired-reader issue is best solved by adding audio content because even with text-to-audio support NONE of the pictures and such can be rendered to audio, though pehaps the <textobject> tag might be picked up. DocBook has special audio-related tags when or if we get round to making an audio translation of the material.

Perhaps we could get Garrett LeSage, who did the "stylesheet-images/" icons for us, to render some peachy-keen callout digits. If not, I could probably SVG a few.

As for the crappy archive searches: YES! My solution was to get a gmail.com account and subscribe to the list from there in addition to my "working" account on my desktop. That lets me use their nifty search tools to scan the archives.

I'll figure out their disposition and, if possible, put them in CVS. Otherwise, Thomas can use the standard ones in the meantime.

Paul W. Frields wrote: > >I have no previous experience with callouts, other than looking at how >they're used in "DocBook:TDG." My chief concern with callouts would be >the impaired-reader issue. How, if at all, do callouts affect readers >who, for instance, are visually impaired and use audible reader >software? I would think that if there is a way to avoid callouts that >does not make the document overly cumbesome, it would be wise to do so. > > > I don't think that it is possible to retain both the visual and text element of a callout without alteration of the stylesheet. However, it is possible to use only text callouts. i.e. |(1) and (2) By setting the callout.graphics parameter to "0" from the makefile or a stylesheet extension. That may be an option.

I was playing with the look and feel of callout sections a few weeks back. Not only don't we have the fedora-style images, but I noticed that if you are showing command blocks that have cut'n'paste style code, the callout numbers interfere with your cut'n'paste. I had a large enough code block that I wanted to use callout's to break it down and explain various parts ... it just killed the cut'n'pastability once added. Thoughts?

P.S. I actually hadn't realized that docbook-style-dsssl provided stock callout images until I was about to launch this email: $ ls /usr/share/sgml/docbook/dsssl-stylesheets-*/images/callouts/ 1.gif 10.gif 2.gif 3.gif 4.gif 5.gif 6.gif 7.gif 8.gif 9.gif Thanks, James Laska On Mon, 2005-05-16 at 11:46 -0500, Thomas Jones wrote: > Thomas Jones wrote: > > > I've attempted to determine some information about the callout images > > used in fedora's documentation --- to no avail. > > > > So I bow to the mercy of the mailinglist and ask for help. What is the > > standardized styling and location of the callout images? I have built > > custom callouts for current development of my xml sources; but didn't > > want to stray from standard practice. > > > > Also I came across a peculiar problem declaring the xsl parameter > > using xmlto. For some reason due to the java implemented processor, I > > am getting a ColumnWidth error. The only alteration performed was to > > include an extension stylesheet for the declaration of a new image > > path. :-( > > > > Admittedly, I have never used xmlto and prefer xsltproc. However it > > might be a moot point if the standard path is acceptable. > > > > Thanks, > > Thomas > > > Bump. >