It'd be nice if inaudible text was a first-class citizen in the editor, like "highlights."
I'll explain more... When my employee can't understand a word, she does one of two things.
First, if she thinks she knows the word, she puts it in square brackets to show that she *thinks* she knows the word, but isn't sure. So, like: "I went to the store and bought [apples] and grapes."
Second, if she can't make it out at all, she types: "I went to the store and bought [inaudible] and grapes."
So when I reviewed my first Trint, I did a browser "find" for "[" to find all these references. I ran into a problem. Specifically, all timestamps on the Trint are surrounded by square brackets, so I found myself finding timestamps 99% of the time. To work around this, I asked her to use squiggly brackets, which she's been doing. This workaround works, but it does violate an established convention for transcriptionists, so it's not ideal.
At some point, it'd be nice if a user could select a word and mark it as either [apple] (i.e. "I'm not sure what this is, but I think it's apple") or [inaudible] (e.g. "I have no idea what this word is"). Maybe she could do this just by typing brackets around a word?
And to get even greedier, it'd be nice if a user with native English could then click "fix inaudible words" and then hit "next" a bunch of times while surfing a Trint to find "inaudible" type words and fix them.
Please sign in to leave a comment.