There are two bugs. (Display error(hiding line), Korean font broken error)

Scrivener
,
1

(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.

2

This is likely the solution. Some fonts are just not well implemented, e.g. sometimes they lack “unused” syllables. I tried 몫, 혻 and 혹시 with “Nanum Gothic” (installed by Apple, if I remember correctly) and they worked as expected.

(Pages unfortunately uses a proprietary text engine, unlike TextEdit or Scrivener, and whatever Apple fixes or adds there, it won’t help here.)

3

Yes, if you use a different font, this doesn’t happen. So, I’m using an alternative font first. However, the enough writing experience doesn’t meet me because it’s not close to the typography I want. :smiling_face_with_tear::smiling_face_with_tear: Also, I hope it’s solved because this basically doesn’t happen not only with pages but also with other commercial word processors (for example, the ‘아래한글’ program often used in Korea).

4

Apple needs to implement the same workaround in TextKit (clearly they saw the need and knew how to do it in Pages).

The underlying problem isn’t specific to Hangeul or the input method, though. Latin-based fonts lacking certain characters exhibit the same fallback behavior.

It’s just more obvious in that case, since the missing character is still missing and thus changed to a more complete font, while your “finished” syllable got damaged in the process (of cycling through other syllable combinations first). I hope this makes sense.

Right now, your options are limited to (1) using a font that looks nice and behaves while writing, or (2) writing in a font that behaves and then compiling to a font that looks nice(r).

I agree that this problem should be addressed, but from my perspective as a user, it’s Apple’s responsibility. (@AmberV is it?) 죄송합니다!

5

As a learner of Korean I find some problems with typing specific Hangul combinations, for example 기ㅜ is displayed wrongly but swapping the order of ㅜ & ㅣ around the correct/expected 귀 appears. Whether this is an error in Apple’s implementation of 2-set Korean or a user error I do not know. (Given my current grasp of Hangul I suspect the latter.)

6

@reepicheep Your suspicion is correct. :see_no_evil: The input order should be ㄱ ㅜ ㅣ.

7

I guess I breached an extension of the underlying left-to-right rule of writing the individual characters.

1 Like
8

Just remember that there’s no character (diphthong in this case) “ㅣㅜ”, but of course “위” is. So you type it in the order how it looks like. If that makes sense.

9

I know nothing about Korean.

I have seen the second bug:

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.