On Thu, 2005-09-08 at 12:45 -0700, Karsten Wade wrote > For this reason, we may have mandatory and recommended usages. I don't > know if this is the best thing, however. > > For example, we may say this style is mandatory: > > <screen> > cd foo > ./bar -o baaz > cat baaz > quux > </screen> > > and this is recommended or preferred: > > <screen> > <userinput><command>cd</command> <filename>foo</filename> > <command>./bar</command> <option>-o baaz</option> > <command>cat</command> <filename>baaz</filename></userinput> > <computeroutput>[contents of baaz]</computeroutput> > </screen> > > Crazy, eh? But sure helpful when you need to parse that content into a > Braille reader, keyboard, and low-vision console. > > I think we need to decide for these cases i) what is mandatory, and ii) > what is recommended. I think it does have to be driven by the requirements of the targets. Piling on tags makes it harder to edit and review documents, and it's easier to mandate more complex requirements if there is a reason. "This ensures that braille readers can handle your documentation" is a good positive incentive. -- Stuart Ellis stuart@xxxxxxxx Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
