[Feature Request] Arguments
See original GitHub issueHello,
I’d like to request arguments for phones_for_word
such as stress_marks=False
. That would be brilliant.
And also the ability to convert multiple words in a single string. Perhaps a for_phone_in_words
function
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Feature Request: Content Parameters/Arguments
Hello,. Writing to request the following feature: The ability to add parameters to the shortcode that will replace text in the content. Like...
Read more >3 ways to manage software feature request - Amoeboids
Some best practices to consider include: · Keep all feature requests in one place. · Create a process for updating it. · Communicate...
Read more >pass arguments automatically and individually in pipelines ...
Feature request A form of pipeline that automatically passes its first input argument on to the next actor, along with any additional ...
Read more >Feature Request: Parameter automation - Decent Sampler Q&A
Hi Dash. Thanks for your question. The problem we've been facing is that JUCE, the audio library that DecentSampler is based on, ...
Read more >Feature request: support for vectorized parameters in httpstan
As of version 4.5.0, httpstan's log_prob endpoint does not support models which define vectors of parameters. My team is interested in integrating Stan...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
These are great suggestions, thank you! In the first case, it’s easy enough to implement on your own, something like:
In the second case, I’m hesitant to introduce word tokenization logic into the library, since it’s such a can of worms, and I feel like most of the bug reports I would get would be about the word tokenization algorithm being wrong or insufficient (instead of what the library is supposed to be about, e.g., getting pronunciation information about words). I’d encourage users instead to make a decision about their own method of tokenizing words for their particular use case and work from there. E.g., with
nltk
:Though on second thought that is kind of a mouthful. I’ll take it into consideration and would also be happy to consider a pull request with this feature…
That’s a fair point. What other features do you think would be useful? Maybe an implementation of the logios tool in python would be a good addition to this library.