Impressions about CJK implementation (1.0.023)
-
@vectoradmin
Report on the following items (ver.1.0.027)
x) Japanese conversion bug
a) tate-chu-yoko
b) kenten
c) shatai
d) ruby
e) warichuf) mojikumi
g) kinsokuMaterial data (up to cloud)
-Input bug: mov
-Document: VSx)
issue: Blanks are entered when using the input mode selection keys (eiji, kana).
Corrective action: It should be corrected so that blanks are not input when switching the input mode. (Cf. Mov)
Other previous issues have been fixed.a)
issue: A little space appears on the characters.
Isn't the origin of the alphabet aligned with the full-width frame?
First-aid measures: Shift up to about 200/1000 and resolve.b)
Unfinished, but durable for general use.
issue: The default character is not partially reproduced. Dot, Fill Circle, Lozenge
Character input does not fully support Japanese "itaiji".
It's a feature that isn't used often, so I think it's better to mature it over time.c)
Horizontal composition: adjust rotation has been fixed.
Almost completedd)
Generally good.
groupe> center: As a graphic application, it would be great if this could be done. After that, I think that it should be aged over time.Items to consider: Need to visualize the subsumption relationship of nested setting items.
Inclusive relation display of nest items such as Font and Size is not implemented.
I want you to be able to see it.
When Rubi is set in VS, if "Arial" is displayed in the dialog, it will be ignored if it is set to HugenoMin in character style.In InDesign, inherited items are displayed as horizontal bars or blanks.
Ideally it should be like this.This issue is the same for kenten.
e)
issue: Horizontal composition; Aligned with the European baseline. It appears to shift above the full-width center.f), g)
Incomplete but working fine. I think it would be good to take time to complete the aging.
These features are important.
However, only some people, such as typesetting team leaders and font designers, can customize it accurately. General users divert those made by these trusted people.General request
When using the text tool, the function once used is inherited.
I want a function to clear all at once. -
@861475_VctSt Send me a link to the cloud files. Thanks!
-
The above post is
It should have been uploaded to "CJK, Japanese observation (1.0.024 ~)".
Next time, I will create a new topic. Please read as it is. -
said in Impressions about CJK implementation (1.0.023):
x)
issue: Blanks are entered when using the input mode selection keys (eiji, kana).
Corrective action: It should be corrected so that blanks are not input when switching the input mode. (Cf. Mov)
Other previous issues have been fixed.I had overlooked it, but I reported it again as a bug via email.
-
@861475_VctSt I will try to replicate and fix this
-
-
I decided to test this. Can report pre-conversion shows up as blanks momentarily in Windows 11 also and input is rather clunky. This is with version 1.3.011
Several issues:
-
Text input is lagging in general with output
-
Fonts can't be changed when textbox is empty. I don't remember this being an issue in the past.
-
Textbox can't be activated sometimes and even when appearing to be activated, doesn't take input (with the text caret icon visible with mouse).
-
The user has to look for the IME conversion window to the lower left of the program to see which candidates are available. It should be appearing closer to the text.
-
The conversion box moves back up towards the text if you try to adjust pre-converted text. This isn't true if starting a new sentence at the end of a line.
-
If there is a delay with converting a character, if you are still typing after that (say entering a "."), it completely misses that input and so the next word/character has to be redone.
Video showing all the problems (has audio):
https://1drv.ms/v/c/110a6c79485f87e5/IQCksyZcydqUQ5U-xDVe-D88AWZ28xBa54ZwsZWNIcB1Sj0?e=UsqE9a
-
-
I watched the video. With my language skills, I couldn't catch what was being said and couldn't fully understand it.
In short, it's about IME-related behavior being unstable, right?
I understand that the Japanese IME issue was resolved in 1.3.011, and I'm reasonably satisfied with that.Is the issue you're presenting from 1.3.011 onward, or was it present before that?
Are the following settings configured?
・Preferences > Applications > East Asian Options > ON
・Character Styles > Script > CJKThese settings are essential beforehand when working with Japanese text. It's also highly recommended to create Japanese-compatible character styles. On top of that, I suggest creating a template that includes these settings and working from it.
@Vectorstyler
I raised this issue in April 2021—five years ago. I'm a user in the specific environment of "Japanese." Furthermore, no other users reported this issue. Therefore, at that time, I judged that improving this issue offered little benefit to overall development and held off requesting a fix until VS development stabilized.
It's an issue that could be resolved by me removing a single space.Five years have passed since then. VS development seems to have entered a stable phase, so I resubmitted this issue and believed it had been resolved. However, due to the small number of Japanese users, I haven't been able to gather other opinions. Let's continue monitoring this matter.
-
Japanese Typesetting Reference Materials (Since I might forget myself)

https://
www.w3.org/TR/jlreq/?lang=ja#legend_of_table_3 -
@debraspicher @861475_vctst I will try to replicate these and fix if possible.
