I get the feeling that a viable program produced locally was in itself a user feature.
While other global programs could be shoehorned into their use case, it still means poor customizability for specific Korean issues. In particular being optimized for the most common Korean use case vs western designers use cases.
There’s a lot of these local brew word processor in the CJK world, and it’s often more than just language support: there will be hooks for common legal formatting, better handling of common transformations, sometimes a dedicated IME working better for long form writing. It also means more culturally useful templates from first party source, which is surprisingly nice to have IMO.
It’s also interesting that local companies/gov. can pay for additional features or adaptations, have the talent move to other entities in the local economy, etc. which is a way higher hurdle for an Adobe or Microsoft.
While other global programs could be shoehorned into their use case, it still means poor customizability for specific Korean issues. In particular being optimized for the most common Korean use case vs western designers use cases.
There’s a lot of these local brew word processor in the CJK world, and it’s often more than just language support: there will be hooks for common legal formatting, better handling of common transformations, sometimes a dedicated IME working better for long form writing. It also means more culturally useful templates from first party source, which is surprisingly nice to have IMO.
It’s also interesting that local companies/gov. can pay for additional features or adaptations, have the talent move to other entities in the local economy, etc. which is a way higher hurdle for an Adobe or Microsoft.