[arch-general] Setting prefered voice for espeakup
Hi, I was wondering if anyone can tell me how to set the default voice for espeakup? I have enabled the service file, which works great, and I have edited the file in /etc/conf.d/espeakup and added --default-voice=en-us to the args, but it still uses the default (UK) voice. Does anyone know what I am doing wrong? Thanks for the help Storm -- Registered Linux user number 508465: https://linuxcounter.net/user/508465.html My blog, Thoughts of a Dragon: http://www.stormdragon.us/ Do you get paid for tweeting? I do: http://spn.tw/r11uj "And for every crossing where two roads diverged. I fell one false decision. But still you find me on this earth." Van Canto - I Stand Alone
Actually, I don't think you're doing anything wrong at all. I think the problem is in the systemd service file, and it's all my fault. I see I'm not even taking arguments from /etc/conf.d/espeakup as I should be doing. I am a bit unsure how to take arguments from this file when running from a systemd unit, so any patches to /usr/lib/systemd/system/espeakup.service are definitely welcome. As this file is Arch specific for now, patches against this file can probably be submitted via the bug tracker. Otherwise, as I sent the original service file to this list, I don't think there will be any problem sending patches to it the same way. Since Tom Gundersen added my file to the package, he is probably the best person to discuss how patches or rewrites should be submitted. Meanwhile, I'll research how to pull command line arguments from the config file and incorporate them into the service, and if I can do this, I'll submit the line to add or a patch here in this thread. ~Kyle http://kyle.tk
On Wed, Nov 7, 2012 at 10:07 PM, Kyle <kyle@gmx.ca> wrote:
Actually, I don't think you're doing anything wrong at all. I think the problem is in the systemd service file, and it's all my fault. I see I'm not even taking arguments from /etc/conf.d/espeakup as I should be doing.
The current behaviour is correct. It gives a decent default. If you want to override it you could copy the service file to /etc/systemd/servic/ and edit it there to add whatever command line options you want to ExecStart=. The reason we don't want to be using /etc/conf.d/* is that it is Arch-specific, and hopefully we will one day be using a service file provided by upstream, which would not know anything about conf.d. Ideally, espeakup would have its own config file where you could specify this option, but failing that making a copy of the service file as I outlined above should hopefully be ok. Cheers, Tom
According to Tom Gundersen: # The reason we don't want to be using/etc/conf.d/* is that it is # Arch-specific, and hopefully we will one day be using a service file # provided by upstream, which would not know anything about conf.d. Oh thanks Tom. Good to know I did the right thing after all. I knew conf.d was Arch-specific, but I thought I still needed to take the command tail from that file. This also answers the question of whether or not arguments can be passed to the daemon started by ExecStart= in a copied service file. So in the example given by the OP, the ExecStart line should look like ExecStart=/usr/bin/espeakup --default-voice=en-us and then the edited file should be saved to /etc/systemd/espeakup.service. Did I get this right, or does the symbolic link in /etc/systemd/system/multi-user.target.wants/espeakup.service need to be removed and replaced with the copy of the file with the modified ExecStart= line? ~Kyle http://kyle.tk
On Wed, Nov 7, 2012 at 11:09 PM, Kyle <kyle@gmx.ca> wrote:
So in the example given by the OP, the ExecStart line should look like
ExecStart=/usr/bin/espeakup --default-voice=en-us
and then the edited file should be saved to /etc/systemd/espeakup.service.
Correct.
Did I get this right, or does the symbolic link in /etc/systemd/system/multi-user.target.wants/espeakup.service need to be removed and replaced with the copy of the file with the modified ExecStart= line?
That's not necessary. -t
According to Tom Gundersen: #> So in the example given by the OP, the ExecStart line should look like #> > #> >ExecStart=/usr/bin/espeakup --default-voice=en-us #> > #> >and then the edited file should be saved to /etc/systemd/espeakup.service. # Correct. In that case, it looks like it's safe to remove /etc/conf.d/espeakup from the package, since it is ignored by the systemd service, and appears to have been shipped with the Arch package for compatibility with conf.d and the rc.d initscripts rather than being an upstream configuration file. I'm currently working with Chris on testing new Talking Arch releases, and will be helping to update the wiki documentation for Talking Arch installation as well, so I'll document the service file override when command line options are needed. ~Kyle http://kyle.tk
Actually, I don't think you're doing anything wrong at all. I think the problem is in the systemd service file, and it's all my fault. I see I'm not even taking arguments from /etc/conf.d/espeakup as I should be doing. I am a bit unsure how to take arguments from this file when running from a systemd unit, so any patches to /usr/lib/systemd/system/espeakup.service are definitely welcome. As this file is Arch specific for now, patches against this file can probably be submitted via the bug tracker. Otherwise, as I sent the original service file to this list, I don't think there will be any problem sending patches to it the same way. Since Tom Gundersen added my file to the package, he is probably the best person to discuss how patches or rewrites should be submitted. Meanwhile, I'll research how to pull command line arguments from the config file and incorporate them into the service, and if I can do this, I'll submit the line to add or a patch here in this thread. ~Kyle http://kyle.tk
Actually, I don't think you're doing anything wrong at all. I think the problem is in the systemd service file, and it's all my fault. I see I'm not even taking arguments from /etc/conf.d/espeakup as I should be doing. I am a bit unsure how to take arguments from this file when running from a systemd unit, so any patches to /usr/lib/systemd/system/espeakup.service are definitely welcome. As this file is Arch specific for now, patches against this file can probably be submitted via the bug tracker. Otherwise, as I sent the original service file to this list, I don't think there will be any problem sending patches to it the same way. Since Tom Gundersen added my file to the package, he is probably the best person to discuss how patches or rewrites should be submitted. Meanwhile, I'll research how to pull command line arguments from the config file and incorporate them into the service, and if I can do this, I'll submit the line to add or a patch here in this thread. ~Kyle http://kyle.tk
Wow sorry for all the duplicate posts. Apparently GMX is having a bit of trouble sending mail. 3 times has to be a record I think. ~Kyle http://kyle.tk
participants (3)
-
Kyle
-
Storm Dragon
-
Tom Gundersen