Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

newly typed text does not follow custom font setting #858

Open
Artoria2e5 opened this issue Sep 5, 2024 · 4 comments
Open

newly typed text does not follow custom font setting #858

Artoria2e5 opened this issue Sep 5, 2024 · 4 comments
Labels

Comments

@Artoria2e5
Copy link

Platform: Windows 10 19045.4842
Version: 3.5 (7223)

I use poedit for localizing terminal programs, so I use a monospace font as the custom font. However, newly typed text in "translation" almost never follows custom font setting; I have to always use Ctrl-UP then Ctrl-DOWN to force it to be redrawn in the correct font.

image

@vslavik vslavik added the Windows label Sep 6, 2024
@vslavik
Copy link
Owner

vslavik commented Sep 6, 2024

Your subject says that text [always] does not the setting. You then say that it almost never does. These are very different things and the distinction matters! So which is it?

There's also some crucial piece of information missing because I cannot reproduce what you claim happens. I rather suspect this may have something to do with you using a font that doesn't have Chinese coverage. In any case, please provide detailed reproduction steps including your exact settings, what exactly you do to reproduce ("type text" can mean many subtly different things and something you consider obvious may not be and may be the trigger). See this too.

@Artoria2e5
Copy link
Author

Good question! I really should make a screen recording of that — so I can figure out the real frequency and reason.

Rest assured though, I use a font with correct character coverage (Sarasa Mono SC, designed for the very purpose of being a CJK Mono/Duospace.)

@Artoria2e5
Copy link
Author

Artoria2e5 commented Sep 9, 2024

Here's a screen recording. Across three attempts, I get 3/3 failures. These were recorded using the Windows built-in Chinese IME in "English" mode, the Chinese IME in Chinese mode, and the built-in EN-INTL keyboard. (I don't remember it working at all, really.)

2024-09-09 10-36-20.zip

@vslavik
Copy link
Owner

vslavik commented Sep 9, 2024

I don't need screen recording, I need steps to reproduce that describe the setup and steps in sufficient detail for me to reproduce it... The fact is that I cannot reproduce this and nobody else reported the same issue. This strongly suggests it is something - as of yet unknown - specific to your setup. Until I have enough information to reproduce your setup, I can't debug and fix it. But it's unclear to me what could be relevant too :(

My hunch still is that it is Chinese- or IME-related. To test IME properly, you'd need to disable it completely first, then launch Poedit and try, not make changes while the app is already running. Can you try that?

Would you have another computer to try on by a chance?

I don't remember it working at all, really.

Does that mean you did see the behavior in 3.4 too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants