Jonathan-LeRoux
commented
3 years ago Hi,
Thanks for pointing these issues out. I thought I had fixed this back in v1.42, but apparently I hadn't :)
The problem is that multi-byte strings appear not to be handled well when saving them to the registry, and they get chopped.
A workaround for now is to add as many new lines after \end{document} as you have multi-byte characters. I guess somewhere in the pipeline, the length of the string gets counted as the number of characters instead of the number of bytes. It's actually surprising that the string doesn't get mangled instead of chopped.
I now realize that the "fix" introduced in v1.42 had 2 issues:
- it only applied to templates, not the code in the main window
- it didn't actually work, because adding 1 line is not enough; the number of lines to be added depends on the number of multi-byte characters (at least it does now in my current setup; I don't believe I would have let such an issue slip by, but who knows) The proper fix is probably to use the Windows API function RegSetValueExW (Unicode version) instead of RegSetValueExA (ANSI version). I need to look into this, as it may need quite a lot of changes. Here is a reference that looks relevant.
By the way, if anyone reads this and is getting "?????" instead of the Unicode characters, you probably need to setup the "Language for non-unicode programs" to either a locale that includes these characters, or "Beta: Use Unicode UTF-8 for worldwide language support".
Thanks, Jonathan
Your codes are very useful, and a great helper to me!
Before the problem started, I'm Korean. I have no ability to check about other languages. It seems there is a problem to hold "Make Default" 's information.
this is an original form of what I want to hold as a default
, base on this, and added my inputs:
"Generation" or "ReGenerate" correctly works (It is helpful).
After I make the 1'st one as "Default Make"
And "New LaTex display"
I get this form, some final parts of the default form are disappeared.
Please help me