Text object - Unreliable text_insert hotkey for utf8 characters #71625

New Issue

Reiner Prokein · 2019-11-16T11:04:47+01:00

Reiner Prokein commented

2019-11-16 11:04:47 +01:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-14 09:44, hash: 8ff9eb97fb
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

It's about this functionality here:

https://docs.blender.org/manual/en/2.80/modeling/texts/selecting_editing.html#accent-characters

I break my fingers with the suggested key combination of holding four keys simultaneously across the whole keyboard. I can usually get 1 out of 10 tries to show a utf8 character with the in the manual described hotkeys. Yes, i know the required order of the key presses. Key, then alt+backspace, then the special key. But this is not to manage. Usually i fill the whole text with the letter first.

This all when this hotkey even works. Lots of the in the manual described characters does not work here, no matter what i try. I smell a keyboard layout problem here. I use a german keyboard layout.

But the problem seems to be even deeper. Curious as i am, i tried to modify the menu to create special characters in the Edit menu in edit mode. And lots of characters like C, L , N , S etc. with accute does not work with their corresponding utf8 number. The character does simply not show up. So this seems to be more than one bug.

Note that i am not asking for help with modifying the menu or programming here. It is just the proof that your utf8 implementation is troubled somewhere, and that the problem may not only be a keyboard layout problem.

List of UTF8 characters, with utf8 and ascii numbers http://www.fileformat.info/info/charset/UTF-8/list.htm

As a side note, when the key combinations in the manual are just examples, how is the user meant to find out the rest of the possible combinations?

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Add Text object. Go to Edit Mode. Go through the in the manual mentioned possible combinations. Count how often you really manage to get it to work the first time. If even at all.

Open space_view3d.py. Go to line 4220. Change the utf8 character to C with acute and u0106. Test it. There is no error, but the character is not created. Curious enough, the python tooltip shows the correct sign.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15 **Blender Version** Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-14 09:44, hash: `8ff9eb97fb` Worked: (optional) **Short description of error** [Please fill out a short description of the error here] It's about this functionality here: https://docs.blender.org/manual/en/2.80/modeling/texts/selecting_editing.html#accent-characters I break my fingers with the suggested key combination of holding four keys simultaneously across the whole keyboard. I can usually get 1 out of 10 tries to show a utf8 character with the in the manual described hotkeys. Yes, i know the required order of the key presses. Key, then alt+backspace, then the special key. But this is not to manage. Usually i fill the whole text with the letter first. This all when this hotkey even works. Lots of the in the manual described characters does not work here, no matter what i try. I smell a keyboard layout problem here. I use a german keyboard layout. But the problem seems to be even deeper. Curious as i am, i tried to modify the menu to create special characters in the Edit menu in edit mode. And lots of characters like C, L , N , S etc. with accute does not work with their corresponding utf8 number. The character does simply not show up. So this seems to be more than one bug. Note that i am not asking for help with modifying the menu or programming here. It is just the proof that your utf8 implementation is troubled somewhere, and that the problem may not only be a keyboard layout problem. List of UTF8 characters, with utf8 and ascii numbers http://www.fileformat.info/info/charset/UTF-8/list.htm As a side note, when the key combinations in the manual are just examples, how is the user meant to find out the rest of the possible combinations? **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] Add Text object. Go to Edit Mode. Go through the in the manual mentioned possible combinations. Count how often you really manage to get it to work the first time. If even at all. Open space_view3d.py. Go to line 4220. Change the utf8 character to C with acute and u0106. Test it. There is no error, but the character is not created. Curious enough, the python tooltip shows the correct sign. ![try.jpg](https://archive.blender.org/developer/F8104098/try.jpg) ![cwithacute.jpg](https://archive.blender.org/developer/F8104124/cwithacute.jpg) ![cwithacuteinmenu.jpg](https://archive.blender.org/developer/F8104128/cwithacuteinmenu.jpg)

Reiner Prokein commented

2019-11-16 11:04:47 +01:00

Added subscriber: @tiles

Germano Cavalcante commented

2019-11-21 15:47:47 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-11-21 15:47:47 +01:00

It would be nice to describe a bug in few lines.
Blender's builtin font doesn't have this character.

It would be nice to describe a bug in few lines. Blender's builtin font doesn't have this character.

Reiner Prokein commented

2019-11-21 17:44:13 +01:00

Sorry for the longer description. I am also a fan of short and pregnant. But this issue was simply not to describe in one line.

Germano Cavalcante commented

2019-11-21 18:30:04 +01:00

I can't tell if this is a bug.
The code seems to work as intended (ignoring non ascii characters in the builtin font).
I recommend you use another font.

I can't tell if this is a bug. The code seems to work as intended (ignoring non ascii characters in the builtin font). I recommend you use another font.

Germano Cavalcante commented

2020-01-13 18:31:12 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2020-01-13 18:31:12 +01:00

I will confirm as being able to reproduce this problem.
But someone who understands this area better can tell if this is a bug or limitation.

I will confirm as being able to reproduce this problem. But someone who understands this area better can tell if this is a bug or limitation.

Reiner Prokein commented

2020-01-14 08:22:41 +01:00

After rereading it after a few weeks, note that this is more than one issue in one. But this all is connected somehow.

The hotkeys are hard to use. To press four hotkeys simultaneously in the right order is insane. This is a usability issue, and not really a bug. Maybe an expression dialog could help here instead of pressing a hotkey combination.
Hotkeys that are mentioned as working in the manual does not work. Either the manual is wrong here, or there is a bug in the input.
UTF8 characters (not ascii) that are not mentioned in the manual, but are part of the UTF8 table, and should work therefore, does not work.
And finally, the manual mentions just a small fraction of the possible characters from the UTF8 table. The user is left alone with the rest. The manual is incomplete here.

After rereading it after a few weeks, note that this is more than one issue in one. But this all is connected somehow. - The hotkeys are hard to use. To press four hotkeys simultaneously in the right order is insane. This is a usability issue, and not really a bug. Maybe an expression dialog could help here instead of pressing a hotkey combination. - Hotkeys that are mentioned as working in the manual does not work. Either the manual is wrong here, or there is a bug in the input. - UTF8 characters (not ascii) that are not mentioned in the manual, but are part of the UTF8 table, and should work therefore, does not work. - And finally, the manual mentions just a small fraction of the possible characters from the UTF8 table. The user is left alone with the rest. The manual is incomplete here.

Dalai Felinto commented

2020-01-14 16:22:52 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2020-01-14 16:22:52 +01:00

Hi, thanks for the report, but we can't handle multiple reports in a single one.

Hotkeys that are mentioned as working in the manual does not work. Either the manual is wrong here, or there is a bug in the input.

And from what I can see, the examples are working (tried with Ø and Ã and they both worked).

And finally, the manual mentions just a small fraction of the possible characters from the UTF8 table. The user is left alone with the rest. The manual is incomplete here.

The manual mentions Ctrl+C, Ctr+V, you can do wonders with this. There is no way Blender can cover all the utf8 chars there.

I will confirm as being able to reproduce this problem.

@mano-wiii what exactly did you try? Because here it works perfectly (e.g., A then Alt + Backspace, then Tilde = Ã)

Hi, thanks for the report, but we can't handle multiple reports in a single one. > Hotkeys that are mentioned as working in the manual does not work. Either the manual is wrong here, or there is a bug in the input. And from what I can see, the examples are working (tried with Ø and Ã and they both worked). > And finally, the manual mentions just a small fraction of the possible characters from the UTF8 table. The user is left alone with the rest. The manual is incomplete here. The manual mentions Ctrl+C, Ctr+V, you can do wonders with this. There is no way Blender can cover all the utf8 chars there. > I will confirm as being able to reproduce this problem. @mano-wiii what exactly did you try? Because here it works perfectly (e.g., A then Alt + Backspace, then Tilde = Ã)

Germano Cavalcante commented

2020-01-14 16:40:15 +01:00

The report has so much information that I ended up forgetting that these are two issues and not one.
I should at least have edited the description (for simplicity), but I trusted my previous (November) triage.

In #71625#848828, @dfelinto wrote:

@mano-wiii what exactly did you try? Because here it works perfectly (e.g., A then Alt + Backspace, then Tilde = Ã)

I refer to the second issue: "C with acute":

The report has so much information that I ended up forgetting that these are two issues and not one. I should at least have edited the description (for simplicity), but I trusted my previous (November) triage. > In #71625#848828, @dfelinto wrote: > > @mano-wiii what exactly did you try? Because here it works perfectly (e.g., A then Alt + Backspace, then Tilde = Ã) I refer to the second issue: `"C with acute"`: ![GIF.gif](https://archive.blender.org/developer/F8277993/GIF.gif)

Dalai Felinto commented

2020-01-14 16:53:02 +01:00

Changed status from 'Confirmed' to: 'Archived'

Dalai Felinto closed this issue

2020-01-14 16:53:02 +01:00

Dalai Felinto self-assigned this 2020-01-14 16:53:02 +01:00

Dalai Felinto commented

2020-01-14 16:53:02 +01:00

If you change your object font to a font that supports said character it will work fine.
The Blender UI font is not the same we use for the default Blender font object, that's why you see it working there.

If you change your object font to a font that supports said character it will work fine. The Blender UI font is not the same we use for the default Blender font object, that's why you see it working there.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Text object - Unreliable text_insert hotkey for utf8 characters #71625