Hi David, and others
The script that converts manual.audacityteam.org into the local manual
has a list of domains that it will keep the URLs intact, all others
are lost. The list is currently 'creativecommons.org',
'wxwidgets.org', 'gnu.org', 'mediawiki.org'.
I could add 'chowo.co.uk' to that list temporarily for 1.3.10, but
that is not a long-term solution to the problem.
One of the ideas behind the 'local manual' is that people with a
poor/no internet connection (say in that place in Kenya that I went to
in the summer) could get Audacity somehow (maybe on a CD, or
pre-installed) and then use it (including the help) without the use of
the internet. Including people using screen readers.
If there is a way to drop a copy of
into the wiki when you update it then that would be a minimal-effort
solution. It would appear in the local help and you wouldn't have to
maintain 2 versions. And it would use the more readable style-sheet.
In the longer term perhaps we could make this page 'an exception' in
the script, but that would set a precedent that I'm not sure we could
maintain, long term. And I don't know how to do it.
So I want
in the local dump, but I'm not sure the best way to do it.
Gale Andrews wrote:
> | From David Bailes <drbailes@...>
> | Fri, 27 Nov 2009 10:41:11 +0000
> | Subject: [Audacity-devel] External links in the manual
>> For 1st december beta release I was planning to just include an
>> external link in the accessibility page to my Jaws guide. However,
>> external links don't seem to appear as links in the installed version
>> of the manual of 1.3.10 rc1. (other examples external links not
>> appearing include the link to the audacity wiki). What is the policy
>> on external links in the manual?
> I haven't got rc1 to hand at the moment, I still have to download it.
> But external links were working in the 1.3.9 help, for example the link
> to Creative Commons. The syntax for the JAWS link appears to be
> correct in the page, so nothing can be corrected there.
> For 2.0, I think the "policy" would be to keep use of external links to
> a minimum since many users will be using the offline version (and
> eventually we would hope to get an export script going again or
> otherwise produce a paged format which could be printed).
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> audacity-devel mailing list