krastev wrote:Sorry, but that's not relevant here.
If you're going to be that way, NONE of our nattering is relevant here. What IS relevant is what L&L think.
krastev wrote:Aspell and Scrivener already support custom lists, so no hacking needed. The only thing that needs to be implemented is the ability to save and load those lists on a project basis.
OSX or iOS are also not relevant since there is no syncing of the customs lists even now, but that's OK.
What OP wants, and I support it, is, Scrivener for Windows to have such custom lists. If it's not much of a hassle.
What everyone who isn't a full-time software developer who makes their living from the product they directly write *AND SUPPORT* keeps forgetting is that's it's not just about whanging the bits around and getting the feature to work. L&L has made multiple commitments to get the Windows version up to par with the Mac version after years of it being behind, because they have a vocal set of customers who a) expect things to Just Work cross-platform and b) are upset when it doesn't.
(Yes, to answer an earlier question, there are many of us Windows users who have iPhones and iPads and use them for Scrivener. It was one of two major reasons that drove my adoption of iPhone after I had to abandon Windows Phone, the other being Android's incredibly messy security/patching/update situation.)
Scriv for Mac allows you to learn custom words, just like Sriv for Windows, across the entire installation (or at least across the logged-in user; I believe they are both across all platforms per-user. They don't sync, but at least it's consistent. Why would they change the project structure to include a feature that could only be implemented on one of the three platforms -- on the platform that (I am willing to bet) is their smallest -- and generate all those tickets for cross-platform scenarios AND get the macOS and iOS folks riled up agitating for an ability they can't/won't deliver on those platforms?
Because that is what it would take. It would take a change to the project structure. It would take (at a minimum) a patch to the macOS and iOS versions to ignore that change to the project structure. That would create yet another project incompatibility barrier.
And all for a feature that, while a few people want it, in the end is low priority given all the other requests/features that are on the list to do *after Windows Scrivener is finally released and caught up*. Features that apply across all platforms, or at least across both desktop platforms.
Windows users have been pissed off for years that Mac has features we don't have. I don't see L&L hurrying to turn the situation around. It doesn't make sense in the larger picture, unless it can be done on Windows *and* macOS at a minimum.