Hi Robert,
I haven't had any issues with character encoding in the past. Do you know
which characters were causing the problem? I use a few different editors,
such as notepad++, and visual studio code.
Notepad++'s guess at the encoding is ansi. If I get it to convert it to
utf-8 I don't see any changes, and on opening again, its best guess is
still ansi.
Concerning the guide and NVDA, I'm still pondering this one. I could add
any NVDA specifics to the guide at some stage.
Why do you think that reading the track info is NVDA specific?
David.
On 12 December 2017 at 13:22, Robert Hänggi <aarjay.robert@xxxxxxxxx> wrote:
Hi David
I've pulled in your JAWS guide.
It was somewhat a pain to let it display correctly within the add-on.
I had to convert it to UTF-8 because at least one character caused
problems.
How do you write the html?
I was thinking if it wouldn't be nicer to adapt it to NVDA.
Of course, the differences are negligible. However, the wrong screen
reader name gives a bad taste of its own.
And there are some NVDA specific things, such as reading the track info.
Cheers
Robert
On 07/12/2017, David Bailes <drbailes@xxxxxxxxx> wrote:
Audacity 2.2.1 is mainly a maintenance release to fix some bugs whichwere
found after 2.2.0 was released.
These are the release notes:
https://wiki.audacityteam.org/wiki/Release_Notes_2.2.1
Note that on the File menu, the "save other" sub menu in 2.2.0 has been
renamed the export sub menu in 2.2.1.
For windows, the direct link to the installer is:
https://www.fosshub.com/Audacity.html/audacity-win-2.2.1.exe
My jaws guide to Audacity 2.2.0 has been updated to also cover 2.2.1, and
is still available at:
http://vip.chowo.co.uk/wp-content/uploads/jaws/Audacity-2.2.0-Guide.html
David.
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
