Skip to content

eSpeak voice parameters inappropriately change due to control+a characters or XML when reading #3334

@nvaccessAuto

Description

@nvaccessAuto

Reported by mdcurran on 2013-07-05 02:33
It is possible for eSpeak's voice parameters such as volume, pitch, rate, language etc to change if NVDA reads text containing eithe controlA (u+0001) characters, or raw less-than and greater-than commands. Filtering out of controlA chracters at least was fixed in NVDA 2009.1 #437 but then regressed in 2011.2 when espeak synthDriver's speakText method was replaced with a speak method. Simply, the resulting string after translating the bad characters was dropped rather than reassigned back to the string for speaking.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions