On 15.05.2025 10:44, Sung-Jae, Cho wrote:
I'll try again with openSUSE Tumbleweed. :)
Please, wait a day. I'll try with virtual machines and real machines, both. And if you can bring some hardware information with a video card driver, xorg-driver, etc,
it'll be helpful for finding the cause.

Operating System: openSUSE Tumbleweed 20250512 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.5-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: llvmpipe Manufacturer: HP Product Name: HP ProBook 640 G3

Extended renderer info (GLX_MESA_query_renderer):

Vendor: Intel (0x8086)

Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)

Version: 25.0.5

Accelerated: yes

Video memory: 3909MB

Unified memory: yes

Preferred profile: core (0x1)

Max core profile version: 4.6

Max compat profile version: 4.6

Max GLES1 profile version: 1.1

Max GLES[23] profile version: 3.2

OpenGL vendor string: Intel

OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2)

OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.5

OpenGL core profile shading language version string: 4.60

OpenGL core profile context flags: (none)

OpenGL core profile profile mask: core profile

EGL driver name: iris

EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,

EGL driver name: iris

EGL_MESA_gl_interop, EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,

EGL driver name: iris

EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,

EGL driver name: iris

EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,

EGL driver name: swrast

EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,


On Thu, May 15, 2025 at 4:38 PM Igor Mironchik <igor.mironc...@gmail.com> wrote:


    On 15.05.2025 08:49, Konstantin Kharlamov wrote:
    > On Thu, 2025-05-15 at 08:37 +0300, Igor Mironchik wrote:
    >> On 15.05.2025 08:29, Konstantin Kharlamov wrote:
    >>> On Thu, 2025-05-15 at 06:29 +0300, Igor Mironchik wrote:
    >>>> Hi.
    >>>>
    >>>> Are any Korean here? I'm curious if they have very bad
    >>>> performance of
    >>>> rendering Korean text in any Qt application? Or is this just
    >>>> because
    >>>> of
    >>>> missing some fonts on my system? I see a huge performance
    >>>> slowdown on
    >>>> Korean text rendering.
    >>> How did you measure? I'm not a Korean, but I tried pasting a
    Korean
    >>> wiki article to Kate with "Droid Sans [1ASC]" font and scrolling
    >>> and I
    >>> don't see any change in performance. Perhaps some more scientific
    >>> method required.
    >>
    >> I paste in Kate a Korean text (~1kB), it took so much time to paste
    >> and
    >> render it (~5 seconds), and Kate starts to think a lot even on
    >> navigating in menu.
    >>
    >> The same with English or Russian text - I don't see any delays,
    Kate
    >> is
    >> responsive.
    > I see. Seems something specific to your system — I just created
    a 158K
    > text file by copy-pasting a Korean Wiki article a dozen of
    times, and
    > when I open it in Kate, everything is smooth and nice.
    >
    > Is it maybe the font? What font do you use? Can you try going to
    Kate
    > settings and changing the font to "Droid Sans [1ASC]" (on
    Archlnux it's
    > a `ttf-droid` package) and seeing if that makes any difference?

    I guess too this is system specific. I'm on openSUSE Tumbleweed.
    Changing editor's font to Droid Sans doesn't help.

    Ok. I see that this issue is system specific, so my question is
    answered. Maybe somebody can check this issue on Tumbleweed only?

    Thank you.

Reply via email to