> Yes, these priorities are useful. Since we are mostly compiler, runtime, > library hackers, and don't actually know much about the processes of the > doc-team, could you describe the "workflow" you would do? If you could > describe/show some sample input files, the stylesheets you would use, > the commands you would use to transform them and how you would expect > the rendered output files to look like that would be very helpful. Mark: Sorry I've not been watching this thread as carefully on f-devel-java-l. When you are ready for some testing from our toolchain, please post to fedora-docs-list. thx - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-java-list mailing list fedora-devel-java-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
