[Windows] With Microsoft IME PinYin, when it input "0" with fullwidth at text edit, it gets "0０". #94868

New Issue

Takahiro Shizuki · 2022-01-13T10:17:41+01:00

Takahiro Shizuki commented

2022-01-13 10:17:41 +01:00

System Information
platform: 'Windows-10-10.0.19043-SP0'
renderer: 'Intel(R) Iris(TM) Graphics 5100'

Blender Version
Broken:

version: 3.1.0 Alpha, branch: master, commit date: 2022-01-12 19:46, hash: 97c2c3991620, type: release

build date: 2022-01-13, 00:56:32

Short description of error
Exact steps for others to reproduce the error

With Microsoft IME PinYin with set fullwidth by IME toolbar, when it input "0" at text edit, it gets "0０".

**System Information** platform: 'Windows-10-10.0.19043-SP0' renderer: 'Intel(R) Iris(TM) Graphics 5100' **Blender Version** Broken: ``` version: 3.1.0 Alpha, branch: master, commit date: 2022-01-12 19:46, hash: 97c2c3991620, type: release ``` build date: 2022-01-13, 00:56:32 **Short description of error** **Exact steps for others to reproduce the error** With Microsoft IME PinYin with set fullwidth by IME toolbar, when it input "0" at text edit, it gets "0０". ![inputting 0 is to be 0０..PNG](https://archive.blender.org/developer/F12803518/inputting_0_is_to_be_0０..PNG)

Takahiro Shizuki commented

2022-01-13 10:17:41 +01:00

Added subscribers: @sntulix, @Harley, @hzuika

Philipp Oeser commented

2022-03-10 09:09:58 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-03-10 09:09:58 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2022-03-10 09:09:58 +01:00

@Harley : can you confirm (not on Windows here)?

Harley Acheson commented

2022-03-13 22:56:01 +01:00

@sntulix - Are you able to give some more information on what is the expected behavior and use case for this?

I realize that current behavior is wrong in some way. When pressing “0” (on main keyboard or numpad) while in Pinyin in "fullwidth" mode you get "0０", which is a regular zero (U+0030) followed by a fullwidth zero (U+FF10).

First note that this bug report applies to all number characters from 0-9, not just 0. Are you wanting keypresses while in fullwidth mode to insert fullwidth characters? Is this useful?

The fullwidth zero is not the same character as regular zero so there are lots of considerations. Would you want to enter fullwidth 3 into a numerical fields and be treated as 3? Or ignored?

When using these fullwidth numbers in names they won't sort correctly. I eventually want to do proper international sorting using the Unicode Collation algorithm (probably using ICU - International Components for Unicode), but that won't happen any time soon.

When using these fullwidth numbers in object names we won't be able to keep visual uniqueness or deal with their use in bones, etc. For example right now you can only have a single object called "Cube.001", but with these characters you could have a "Cube.０01", "Cube.0０1", "Cube.00１", etc. When duplicating "Cube.001" now we make a new one as ""Cube.002" but that can't happen with "Cube.０01" and I think you'd get something like ""Cube.０01.001"

So I guess I am just wanting to clarify what is needed, what is expected, etc

@sntulix - Are you able to give some more information on what is the expected behavior and use case for this? I realize that current behavior is wrong in some way. When pressing “0” (on main keyboard or numpad) while in Pinyin in "fullwidth" mode you get "0０", which is a regular zero (U+0030) followed by a fullwidth zero (U+FF10). First note that this bug report applies to all number characters from 0-9, not just 0. Are you wanting keypresses while in fullwidth mode to insert fullwidth characters? Is this useful? The fullwidth zero is not the same character as regular zero so there are lots of considerations. Would you want to enter fullwidth 3 into a numerical fields and be treated as 3? Or ignored? When using these fullwidth numbers in names they won't sort correctly. I eventually want to do proper international sorting using the Unicode Collation algorithm (probably using ICU - International Components for Unicode), but that won't happen any time soon. When using these fullwidth numbers in object names we won't be able to keep visual uniqueness or deal with their use in bones, etc. For example right now you can only have a single object called "Cube.001", but with these characters you could have a "Cube.０01", "Cube.0０1", "Cube.00１", etc. When duplicating "Cube.001" now we make a new one as ""Cube.002" but that can't happen with "Cube.０01" and I think you'd get something like ""Cube.０01.001" So I guess I am just wanting to clarify what is needed, what is expected, etc

Takahiro Shizuki commented

2022-03-14 04:31:14 +01:00

Hi. @Harley

Are you able to give some more information on what is the expected behavior and use case for this?

I don't expect a something about this. Because I'm not a End User of Chinese Language.
Also this is a just reporting I found.

Is this useful?

I think this has two points. The one is fullwidth inputting has used at Name in all around (in Japan) and it exists as a usable character in a character set. Another point is Auto naming rule of Object when duplicated ("Cube.001", "Cube.002").
But I think its are not same background problem. The one is a Language Problem on Computer, another is Blender's usability.

About ０-９ (fullwidth numeric): /* This is just think. */
The function auto converting the fullwidth to the halfwidth is useful at Numeric edit box. But if when ０-９ is used in a document like the naming specifications,
the auto converting is not useful in Text edit box, Because it is unlike previous, inconsistent. It could be a problem.

UPDATE:
If when I needed ０-９ (fullwidth) at Text edit box, I use "copy & paste" or negotiation with a customer.

Hi. @Harley >Are you able to give some more information on what is the expected behavior and use case for this? I don't expect a something about this. Because I'm not a End User of Chinese Language. Also this is a just reporting I found. >Is this useful? I think this has two points. The one is fullwidth inputting has used at Name in all around (in Japan) and it exists as a usable character in a character set. Another point is Auto naming rule of Object when duplicated ("Cube.001", "Cube.002"). But I think its are not same background problem. The one is a Language Problem on Computer, another is Blender's usability. About ０-９ (fullwidth numeric): /* This is just think. */ The function auto converting the fullwidth to the halfwidth is useful at Numeric edit box. But if when ０-９ is used in a document like the naming specifications, the auto converting is not useful in Text edit box, Because it is unlike previous, inconsistent. It could be a problem. UPDATE: If when I needed ０-９ (fullwidth) at Text edit box, I use "copy & paste" or negotiation with a customer.

blender-admin commented

2022-03-19 17:05:10 +01:00

This issue was referenced by 82c852f387

This issue was referenced by 82c852f38732a005a1da72f4fb7fb402ecd71ec0

Harley Acheson commented

2022-03-19 17:08:41 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Harley Acheson closed this issue

2022-03-19 17:08:41 +01:00

Harley Acheson self-assigned this 2022-03-19 17:08:41 +01:00

Harley Acheson commented

2022-03-19 17:08:41 +01:00