Upgrade StorageRead Aloud: Don't skip citations if they are following keywords (e.g. "as in")
Right now, the read aloud feature skips every citation, which is already better than reading them out all the times. From my testing, this is annoying and confusing if the citation is built into the text as in the following sentence:
"As has been shown in [42], no relation between A and B blablabla"
As a hard-coded collection of just a few of these keywords would improve the behavior 99% of the time and there is no 100% perfect solution, I recommend adding the following
"in [1]", "from [2]", "within [3]",
"according to [4]", "as described by [5]", "proposed by [6]"
"based on [7]", "building upon [8]", "following [9]"
"compared to [10]", "unlike [11]", "similar to [12]"
I think the appropriate section of code is the getElidedRanges function in https://github.com/zotero/reader/blob/master/src/common/read-aloud/sdt-segments.ts
Also, while I'm not a zotero developer I'd really like to be one. Compared to other open source projects it feels hard for me to get involved because I'm not allowed to make any github issues, which I'd even help with given a "go ahead!". As I'll be using the read aloud feature a lot and already noticed a few other bugs, I hereby request permission to create github issues!
"As has been shown in [42], no relation between A and B blablabla"
As a hard-coded collection of just a few of these keywords would improve the behavior 99% of the time and there is no 100% perfect solution, I recommend adding the following
"in [1]", "from [2]", "within [3]",
"according to [4]", "as described by [5]", "proposed by [6]"
"based on [7]", "building upon [8]", "following [9]"
"compared to [10]", "unlike [11]", "similar to [12]"
I think the appropriate section of code is the getElidedRanges function in https://github.com/zotero/reader/blob/master/src/common/read-aloud/sdt-segments.ts
Also, while I'm not a zotero developer I'd really like to be one. Compared to other open source projects it feels hard for me to get involved because I'm not allowed to make any github issues, which I'd even help with given a "go ahead!". As I'll be using the read aloud feature a lot and already noticed a few other bugs, I hereby request permission to create github issues!