Attachment diff.2.txt added by aleksey_s on 2008-11-09 13:33
Description:

Attachment diff.txt added by aleksey_s on 2008-11-22 22:13
Description:
bzr merge-directive

Comment by aleksey_s on 2008-11-02 14:11
(In #212) functionality, requested in this ticket is implemented in #219

Comment 2 by aleksey_s on 2008-11-09 00:56
initial GUI support added. now only dialog with multiselect list of all voices and synthesizers is required. diff.txt - bzr merge directive.

Comment 3 by aleksey_s on 2008-11-09 13:34
maked changes to reflect last revision

Comment 4 by aleksey_s on 2008-11-22 22:18
updated feature to match main branch. Core developers, are you going to review it?..

Comment 5 by ragb on 2008-11-27 16:27
Another related idea is to have application specific dictionaries. This was discuced in NVDA's portuguese list, it seems some users use it extensively in JAWS and request this feature in NVDA.
Should I fill another ticket for this suggestion?

Comment 6 by aleksey_s on 2008-11-28 22:49
for further progress, see bzr branch at http://bzr.nvaccess.org/nvda/smartDictionaries

Comment 7 by jteh on 2009-05-01 01:29
Changes:
Milestone changed from 0.6 to None

Comment 8 by Bernd on 2009-07-04 14:09
Hi, is someone still working on this enhancement?

Comment 9 by aleksey_s (in reply to comment 8) on 2009-07-04 15:06
Replying to Bernd:

Hi, is someone still working on this enhancement?

It is already done and waits the core developers decision about six months.

Comment 10 by Bernd on 2009-10-21 17:13
Hello core developers,

as I just saw, this ticket could be closed since more than a few months. Would it be possible to merge this ticket if 2009.1 is released?

Comment 11 by leonarddr on 2015-02-06 16:10
Changes:
State: closed

Comment 12 by bdorer (in reply to comment 11) on 2015-02-06 17:22
Replying to leonarddr:
please don't close tickets as fixed if they aren't.
Changes:
State: reopened

Comment 13 by leonarddr (in reply to comment 10) on 2015-02-09 13:53
I'm sorry, I misinterpreted comment 10 as a request for closure.
What is the current status of this? Is current patch even suitable for inclusion in the code, I wonder?

CC @bdorer

Anyone knows whether aleksey is available on github? I'd be happy to mention him if I know his github ident.

@jcsteh: May be you could reprovide the attachments?

No need; the code is available in the smartDictionaries branch in the official repo.

1. I've always been very dubious about this. It seems overly complex to me and I'm not clear on real world use cases.
2. We don't "support" manual editing of files these days, so a regular expression isn't a good fit.
3. Even if users used multiple synthesisers for a single language, would they go through the effort of configuring something like this?
4. I think profile specific dictionaries are probably more versatile.

I agree, we should continue with profile based dictionaries. Synth based dictionaries are hard to handle because it often depends on the voice you are using. This is fair too much work to maintain such things, especially for synths which are updated on a regular basis like Cereprog or eSpeak.

Closing as per #219 (comment), and also because no one is interested in actively working on this now.