> - For users of screen readers, the single page html version would be
> useful. The heading heirarchy seems to have gone wrong in the this
> version - this is obviously crucial for navigating a long document.
You're right, that was a bug. It's fixed now.
> - the pictures and screenshots in all the versions need descriptive
> alternative text. I realise that this time consuming, not always easy,
> and may in some cases be describing parts of Audacity that aren't
> usable by screen readers anyway.
I've set it up so that we can have different versions of the manual
that share some content but not others. I think that some chapters
should be made accessible with good alt text. Other chapters simply
make no sense to someone using a screenreader (like Zooming, for
example) so they should be left out, and others should have a special
version for users with screenreaders.
> - navigating long documents using jaws is easier in html or tagged pdf
> rather than word.
> - keeping the links as links in word and tagged pdf as well as giving
> page numbers would be helpful
This is now done too. The first time you open the automatically
exported Word document, you have to choose "Update Fields" for it to
fill in the page numbers.
> On 27/05/07, Dominic Mazzoni <dominic@...> wrote:
>> Thanks for pointing this out! I think I have a good solution for
>> I'm using LaTeX to produce the PDF version. The benefit of using
>> LaTeX is that it's very robust, I can completely automate the
>> process, and I can do cool tricks with internal links, for example a
>> link to "Preferences Dialog" becomes "Preferences Dialog (Page 37)"
>> in the printed version, where the page number is computed
>> automatically. Unfortunately LaTeX does not support tagged PDF at
>> Luckily, I've also finished writing an RTF exporter, intended to be
>> opened by Microsoft Word. I wrote the translator carefully using
>> styles for all of the headings, so you can edit the document exactly
>> the way you would any other Word document.
>> I'm guessing that OpenOffice Writer will also do fine with the RTF -
>> if not I can probably debug it. From there we can convert to PDF
>> also - but unfortunately I can't do this step automatically. That's
>> not a big deal - when we release the official version of the manual
>> we can create .doc and tagged pdf versions for people who need that
>> format, we just won't be able to do that with the nightly "automatic"
>> updated manual. For people who want to print it out, the LaTeX-
>> produced PDF will probably be the best.
>> Here are links to the RTF, DOC, and DOC-PDF versions - I'd love to
>> hear how these work for you.
>> I also have a plain HTML version, with everything on one page:
>> Right now these don't have a table of contents, but Word or
>> OpenOffice ought to be able to generate one for you automatically.
>> I'll probably make it do that automatically soon. I'll also add an
>> Also, I realize that the manual is still a mess! Don't worry, the
>> pieces are coming into place now, I've got a bunch of images ready to
>> upload and a number of sections outlined - pretty soon major portions
>> of the manual will be rewritten and better than ever! In the
>> meantime general feedback like this is great. Let me know anything
>> else that would make the manual easier to work with!
>> - Dominic
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> Audacity-devel mailing list