# SayNextWord in web sources broken?

**URL:** https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813
**Category:** Web Sources Discussion
**Created:** [April 5, 2011, 7:31am UTC](https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813 "2011-04-05T07:31:31Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![anon40688970](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/898d66/32.png) [@anon40688970](https://community.mp3tag.de/u/anon40688970)
#### Post date: [April 5, 2011, 7:31am UTC](https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813/1 "2011-04-05T07:31:31Z")

</div>

Here is an debug excerpt which shows - in my opinion - that SayNextWord is broken. The log shows that SayNextWord only outputs the first character not the complete word. I expected mp3tag to output the text 'clearcut' in that particular case.

Thanks for reading

```
Script-Line : 243
Command : findinline
Parameter 1 : ><td><
Parameter 2 : >1<
Parameter 3 : >1<

Output : ><

Line and position:
<td>clearcut 2006 50 Min. - Originalhörspiel dt. </td></tr>
    ^

------------------------------------------------------------

Script-Line : 244
Command : saynextword

Output : >c<

Line and position:
<td>clearcut 2006 50 Min. - Originalhörspiel dt. </td></tr>
     ^

```

---

<div class="post-metadata">

### Author: ![pone](https://community.mp3tag.de/user_avatar/community.mp3tag.de/pone/32/272_2.png) [@pone](https://community.mp3tag.de/u/pone)
#### Post date: [April 5, 2011, 8:00am UTC](https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813/2 "2011-04-05T08:00:39Z")

</div>

seems like there is a problem

as a workaround, you can use:  
**sayuntil " "**  
if it is always a space which follows the word.

---

<div class="post-metadata">

### Author: ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [April 5, 2011, 8:14am UTC](https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813/3 "2011-04-05T08:14:53Z")

</div>

> [@anon40688970](#):
>
> ... The log shows that SayNextWord only outputs the first character not the complete word. ...

It seems that SayNextWord needs the boundary of a previous word to detect where the next word start, something of \b in a regexp.

DD.20110405.1215.CEST

---

<div class="post-metadata">

### Author: ![pone](https://community.mp3tag.de/user_avatar/community.mp3tag.de/pone/32/272_2.png) [@pone](https://community.mp3tag.de/u/pone)
#### Post date: [April 5, 2011, 8:19am UTC](https://community.mp3tag.de/t/saynextword-in-web-sources-broken/11813/4 "2011-04-05T08:19:11Z")

</div>

> [@DetlevD](#):
>
> It seems that SayNextWord needs the boundary of a previous word to detect where the next word start, something of \b in a regexp.

If so, try  
**findinline "\<td"**  
instead of  
**findinline ""**  
before the saynextword command. then the parser shoul be able to read **\>** as the word boundary before the word.