Can’t sure where to start, so I decide to say hello to the people on the forum first.
I’m considering to buy Scrivener app on Mac, as a part of investment for my novelist career. I’ve been tried enough applications and online services for my writings and it seems like I missed out on Scrivener this whole time.
Maybe that’s because I always had been a Korean speaker exclusively but, I don’t know. It seems many Koreans also using this app for their writing process while ago.
While I search more information on this, new application, for me anyway, I found this dedicated forum. Hope I can find many helps and tips in the future.
Form is correct, but that “-하-” should change to “-해-” in this case, grammatically.
If you don’t mind me to explaining it,
Study (Korean) : (한국어-를) 공부-하-다.
(I am) studying (Korean) : (저-는) (한국어-를) 공부-해-요.
Korean grammar really gets complicating when you attempt to dissect it but, in just normal speaking, I feel like knowing the difference in that is enough. I’m happy that foreign people learn to use “저” rather than “나” to be honest.
Full transparency: the text engine we use in Scrivener (on Mac it is the native text engine, like what you see in TextEdit), it can sometimes break Korean words into individual characters, at the end of the line. From what I understand it is not something that will carry over when you export/compile and open in Word or whatever, it’s a visual problem, but it has stopped some people from using the software as it can be hard to work with.
We’d love to fix it, but it’s one of those things that is “beneath” the software, if that makes sense. It would be like fixing how a scrollbar works, but way more complicated given how fonts are displayed and all that. It is frustrating because it used to work quite well, but an Apple update broke it a few years ago and they haven’t fixed it since.
I heard about how Mac breaking Hangul, especially when you send them to Windows environment. But when I use Notes and Pages, never suffered any issues with it. Maybe TextEdit has some specific problem.
Thank you for your transparency. I’m planning to get this app next month. Hopefully it will work great for me, for my future and current career.
Pages uses a different text engine than TextEdit and Scrivener. (I’m not sure what exactly powers Notes.) Unfortunately Apple chose to keep that one for themselves, while devs have to do with the aging TextKit or the just-partly-ready TextKit 2. Or invent their own.
(It’s not a “macOS problem” in general. Obsidian also occasionally tends to “decompose” combined Unicode characters and the worst part is that you can’t tell by just looking at a given text.)
Yup, and that’s probably a big part of the problem. If their iWork department was forced to use the same text engine we have to use, it would probably be amazing.
Hopefully it doesn’t get too much in the way though, and you are able to enjoy the features of the software around the editor enough to put up with it when it happens.