Oct. 16, 2020
Asking for features in Scrivener, an app
I strongly encourage the development team to introduce the keywords feature in the iOS version. Without that, I have to keep my private journal in a different app.
And as a Korean user who writes in Korean and English back and forth, the font support is far from satisfactory. When I do switching between Korean and English inputs that happens quite frequently, the font will be set as the default system font in the course of switching, regardless of my initial choice of fonts. On the other hand, Apple's native apps, such as Pages, have a different mechanism. In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or san-serif. When I switch back to English input, the font will be set as the selected one rather than the corresponding English font of the Korean fonts, as is the case for Scrivener. To maintain the English typeset, I have to choose the font every time I switch to English back from Korean input. If the app handles default Korean (or any other non-Latin language) and English fonts separately, this feature could be more desirable.
Correction Settings
I strongly encourage the development team to introduce the keywords feature in the iOS version.
I strongly encourage the development team to introduce the keyword feature in the iOS version.
Either is fine but I think keyword feature sounds a little bit better.
When I do switching between Korean and English inputs tha, it happens quite frequently, that the font will be set as the default system font in the course of switching, regardless of my initial choice of fonts.
When I switch between Korean and English input, it happens quite frequently that the font will be set as the default system font in the course of switching, regardless of my initial choice of fonts.
In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or sans-serif. In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or sans-serif.
If the app handles default Korean (or any other non-Latin language) and English fonts separately, this feature cwould be more desirable.
If the app handles default Korean (or any other non-Latin language) and English fonts separately, this feature would be desirable.
Feedback
Well written feedback report! Scrivener looks like a convenient app. I hope they will amend the app accordingly if you send them the feedback.
Oct. 19, 2020
Thank you. Scrivener is a writing app for longer-length drafts, of which I am a huge fan. By the way, would you like to give a little bit of explanation on the difference between "could" and "would" in the last sentence? I also wonder whether "desirable" could be accompanied by "more" or not.
Oct. 19, 2020
I just thought it sounded a little bit better, but you can ignore my last correction actually.
Oct. 19, 2020
Did you say to both the questions? Thank you!
When I do switching between Korean and English inputs that happensas I do quite frequently, the font will be sets as the default system font in the course of switching, regardless of my initial choice of fonts.
When I switch between Korean and English inputs as I do quite frequently, the font sets as the default system font, regardless of my initial choice of fonts.
Generally you dont use "do" before the present progressive (-ing endings) and saying "in the course of switching" here is redundant since you already said it earlier in the sentence and sounds a bit unnatural
Oct. 19, 2020
Thank you. Would you like to give a little bit of explanation why "sets" is suitable rather than "will be set" in this sentence? The reason might be that "switch" is given as present tense so that matching the tenses is more natural and the problem arises every time I do. But I am not sure.
Oct. 25, 2020
Ya exactly, just keeping things consistent in the present tense sounds better. When describing a problem it seems more natural to say “when I do X, (present) Y happens as a result” instead of “when I will do X (future), Y will happen” because you’re describing an experience you’ve already had that is happening again in the present
Oct. 26, 2020
Thanks a lot! Your explanation enables me to aware a bit more of the characteristics of English.
|
Asking for features in Scrivener, an app |
|
I strongly encourage the development team to introduce the keywords feature in the iOS version.
I strongly encourage the development team to introduce the keyword Either is fine but I think keyword feature sounds a little bit better. |
|
Without that, I have to keep my private journal in a different app. |
|
And as a Korean user who writes in Korean and English back and forth, the font support is far from satisfactory. |
|
When I do switching between Korean and English inputs that happens quite frequently, the font will be set as the default system font in the course of switching, regardless of my initial choice of fonts.
When I Generally you dont use "do" before the present progressive (-ing endings) and saying "in the course of switching" here is redundant since you already said it earlier in the sentence and sounds a bit unnatural
When I |
|
On the other hand, Apple's native apps, such as Pages, have a different mechanism. |
|
In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or san-serif. In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or sans-serif. In that app, when I choose a font that does not have a corresponding Korean typeset, it automatically matches the system Korean fonts according to whether the original one is serif or sans-serif. |
|
When I switch back to English input, the font will be set as the selected one rather than the corresponding English font of the Korean fonts, as is the case for Scrivener. |
|
To maintain the English typeset, I have to choose the font every time I switch to English back from Korean output. |
|
If the app handles default Korean (or any other non-Latin language) and English fonts separately, this feature could be more desirable.
If the app handles default Korean (or any other non-Latin language) and English fonts separately, this feature |
|
To maintain the English typeset, I have to choose the font every time I switch to English back from Korean input. |
You need LangCorrect Premium to access this feature.
Go Premium