Skip to content

code cleanup: remove ssml_ignore_l_angle.#886

Merged
valdisvi merged 1 commit into
espeak-ng:masterfrom
jaacoppi:readclause
Mar 2, 2021
Merged

code cleanup: remove ssml_ignore_l_angle.#886
valdisvi merged 1 commit into
espeak-ng:masterfrom
jaacoppi:readclause

Conversation

@jaacoppi

Copy link
Copy Markdown
Collaborator

It looks like ssml_ignore_l_angle is just dead code. Can you find any use for it?

It is only set in AnnouncePunctuation if end_clause != 0. Even when manually setting ssml_ignore_l_angle there seems to be no effect on anything.

For example, this doesn't change after the commit:
src/espeak-ng -m --punct "<speak>Here's a &lt; and a &amp;, and < and &. This is still &lt;(&lt;)(&lt;)</speak>"

If a use case for this is found it should be better documented.

looks like commit 1a2f454 from 2008 was first to have ssml_ignore_l_angle in AnnouncePunctuation.

It is supposed to be used with SSML for reading < (&lt;) and & (&amp;)
when invoking espeak-ng --punct -m.

However, it looks like the code is dead since removing it doesn't fail
the ssml reference test.
@valdisvi

Copy link
Copy Markdown
Member

@michaelDCurran, @feerrenrut, probably NVDA community is the most active users of SSML features of the eSpeak NG. Can you comment on this?

@valdisvi valdisvi merged commit 2d633b7 into espeak-ng:master Mar 2, 2021
@valdisvi

valdisvi commented Mar 2, 2021

Copy link
Copy Markdown
Member

I think, we can throw that part out.

@jaacoppi jaacoppi deleted the readclause branch March 4, 2021 15:09
@feerrenrut

Copy link
Copy Markdown
Contributor

We can update the version of espeak used by NVDA. Then this will get some testing with our alpha users.

See also: #857

@jaacoppi

jaacoppi commented Mar 18, 2021 via email

Copy link
Copy Markdown
Collaborator Author

@feerrenrut feerrenrut mentioned this pull request Mar 19, 2021
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants