(I tried to insert a video into the post when I first wrote it, but community regulations limit this. So I share the link to the Vimeo profile where I uploaded the bug video. https://vimeo.com/user230662649 )
Hello, I am a Korean literature major who is using Scrivener well.
I’m currently trying to report two bugs that happen using the latest version. (I don’t know if I had this bug before.)
First of all, one is ‘Korean font error’.
Unlike the English alphabet, Korean is used by ‘combining’ symbols. Therefore, in order to implement this on the computer, the font program ‘prepares’ appropriate fonts to match the letters in advance during the encoding process.
For example, ‘혹’, a combination of ‘ㅎ’, ‘ㅗ’, and ‘ㄱ’, is ‘prepared’ because it is commonly used in Korean. However, since ‘혻’, which only adds ‘ㅅ’ to this, is a character that is not used in Korean, some fonts provide unexpected errors.
The problem is that in order to use the general expression ‘혹시’, you have to go through ‘혻’ > ‘ㅎ’ > ‘호’ > ‘혹’ > ‘혻’ > ‘혹시’ )
Therefore, in most programs, the font is broken at the moment it is ‘broken’, but as soon as it moves on to ‘next’, the font returns to its original state. However, Scrivener does not support this.
Please watch the video below.
Since ‘몫’ is a word that is often used in Korean, I put it on the side as a contrast. Pages does not support ‘혻’ and clearly expresses ‘몫’ in a different font, but the system still shows that you are using the same font. Therefore, it does not affect the previous and subsequent letters. However, in Scrivener, ‘혻’ is completely changed to the ‘Apple Myungjo’ font. So, even if you move on to ‘혹시’, only ‘혹’ remains a different font. This bug actually makes users uncomfortable enough to disable fonts that cannot display ‘혻’.
The second bug is one where you often don’t see the next line when you go back to the middle of the text and press Enter to split the row.
Sentences aren’t actually gone, but sentences aren’t visible until you update the display, such as writing the next sentence or scrolling down.
This bug isn’t consistently implemented, but I’ve found one situation that definitely happens. This usually happens when you go back to just before the last sentence of the text and type Enter.
I hope these problems will be resolved as soon as possible.
And since I reported the bug, I would like to add a suggestion.
Character spacing (not row spacing) is too hidden in text format settings, and it’s not visible as a numerical value. I wish I could specify character spacing in style or default format settings as well.
I can do a great job with scrivener, when I’m writing poems and papers. I hope this program will be further improved so that I can use it forever. Thank you.