Text object doesn't work with accented letters. #103098

Closed
opened 2022-12-10 06:26:01 +01:00 by Fernando Monteiro · 25 comments

System Information
Operating system: Linux-5.15.0-56-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: (newest version of Blender that worked as expected)

Short description of error
Text objects doesn't work with dead-keys. if I type the sequence "p ~ a o", in any text editor this results in the word "pão". But in Blender text object, this results in the word "po".

Exact steps for others to reproduce the error

  • add a Text Object
  • go to edit mode
  • type the letters p~ao

You should get "pão", but will get "po".

What I am doing to get accented text is :

  • Open a external text editor, write in the wanted text, select and copy it.
  • Go to blender, select the Text Object, go to edit mode and paste.
**System Information** Operating system: Linux-5.15.0-56-generic-x86_64-with-glibc2.35 64 Bits Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: (newest version of Blender that worked as expected) **Short description of error** Text objects doesn't work with dead-keys. if I type the sequence "p ~ a o", in any text editor this results in the word "pão". But in Blender text object, this results in the word "po". **Exact steps for others to reproduce the error** - add a Text Object - go to edit mode - type the letters p~ao You should get "pão", but will get "po". What I am doing to get accented text is : - Open a external text editor, write in the wanted text, select and copy it. - Go to blender, select the Text Object, go to edit mode and paste.

Added subscriber: @Chimp

Added subscriber: @Chimp

Added subscribers: @Harley, @mod_moder

Added subscribers: @Harley, @mod_moder

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

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

It seems to me that this is a font problem, since you say that the character will appear on it simply will not be visible

May I ask you to take a look @Harley ?

It seems to me that this is a font problem, since you say that the character will appear on it simply will not be visible May I ask you to take a look @Harley ?

Added subscriber: @cassidy

Added subscriber: @cassidy

In #103098#1458070, @mod_moder wrote:
It seems to me that this is a font problem, since you say that the character will appear on it simply will not be visible

The glyph exists in Blender's default font, it's just that Blender doesn't process typing (p, ~, a, o) into "pão". And external text editor program does process it, like Microsoft Word, probably.

Screenshot (41).png

To be honest, to me this is not really a bug, but rather a lack of feature in Blender's part. Therefore this report is more like a feature request.

EDIT:
A spelling mistake.

> In #103098#1458070, @mod_moder wrote: > It seems to me that this is a font problem, since you say that the character will appear on it simply will not be visible The glyph exists in Blender's default font, it's just that Blender doesn't process typing (p, ~, a, o) into "pão". And external text editor program does process it, like Microsoft Word, probably. ![Screenshot (41).png](https://archive.blender.org/developer/F14049498/Screenshot__41_.png) To be honest, to me this is not really a bug, but rather a lack of feature in Blender's part. Therefore this report is more like a feature request. **EDIT:** A spelling mistake.
Member

Text object doesn't work with accented letters.

It does properly display accented letters. Or any characters if your font supports it.

{F14050102,width=100%}

Text objects doesn't work with dead-keys... type the letters p~ao

This is the issue, that you want to type "~" and then "a" to get an ã instead.

The fact that "~' is treated is a dead key for you is because of the operating system keyboard layout you have selected. When I personally do the exact thing in "any text editor" I just get "p~ao". In Word I am forced to press ctrl+shift+"~' then "a". In other programs users might have to press Alt-0227.

Languages use different layouts and use different means of adding accented and precomposed characters. Some user's keyboard layouts might treat tilde as dead, while other might use ` " ' ^ as dead keys. Other language layouts might pop up an entire window of alternative characters as they type. Others get entirely different characters coming out as they press the "regular" a - z keys.

Blender though, just interprets each key as you type it, without trying to guess a language-dependent intention. To get around this it is probably most convenient to just copy and paste the text into Blender from a text editor.

It might be nice to explore ways of entering precomposed characters but it is actually tricky to do in a language-independent way. Typing ~ + a to get ã might be convenient for Portuguese, Guaraní, Kashubian, Taa, Aromanian, and Vietnamese. But many other languages might want to easily enter ë or à and as more keys are treated as "dead" it becomes more confusing for other users.

I'll give it some thought, but this is really just a feature request.

> Text object doesn't work with accented letters. It does properly display accented letters. Or any characters if your font supports it. {[F14050102](https://archive.blender.org/developer/F14050102/image.png),width=100%} > Text objects doesn't work with dead-keys... type the letters p~ao This is the issue, that you want to type "~" and then "a" to get an ã instead. The fact that "~' is treated is a dead key *for you* is because of the operating system keyboard layout you have selected. When I personally do the exact thing in "any text editor" I just get "p~ao". In Word I am forced to press ctrl+shift+"~' then "a". In other programs users might have to press Alt-0227. Languages use different layouts and use different means of adding accented and precomposed characters. Some user's keyboard layouts might treat tilde as dead, while other might use ` " ' ^ as dead keys. Other language layouts might pop up an entire window of alternative characters as they type. Others get entirely different characters coming out as they press the "regular" a - z keys. Blender though, just interprets each key as you type it, without trying to guess a language-dependent intention. To get around this it is probably most convenient to just copy and paste the text into Blender from a text editor. It might be nice to explore ways of entering precomposed characters but it is actually tricky to do in a language-independent way. Typing ~ + a to get ã might be convenient for Portuguese, Guaraní, Kashubian, Taa, Aromanian, and Vietnamese. But many other languages might want to easily enter ë or à and as more keys are treated as "dead" it becomes more confusing for other users. I'll give it some thought, but this is really just a feature request.

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

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

Thank you for the answer

Thank you for the answer

Well guys. I got an older version of blender, the 2.80 and typing p~ao works perfectly. It give me pão. So, it is not exactly a feature request. I understand that it is related to keyboard layout and the OS (in my case, Ubuntu), but how 2.80 can do well and 3.3.1 can't ?

Well guys. I got an older version of blender, the 2.80 and typing p~ao works perfectly. It give me pão. So, it is not exactly a feature request. I understand that it is related to keyboard layout and the OS (in my case, Ubuntu), but how 2.80 can do well and 3.3.1 can't ?
Member

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'
Member

I see it working as expected in 3.3.1 with US International Keyboard, but not working in master. Can assume whatever is breaking on this layout will also break the OP's layout.

With this keyboard layout set, pressing single-quote then a gives you á, while pressing double-quote then e results in ë. 3.3.1 works as expected, master actually swallows both single and double-quote.

Nothing is jumping out in the change log for GHOST_SystemWin32.cpp. This might have to be bisected.

I see it working as expected in 3.3.1 with US International Keyboard, but not working in master. Can assume whatever is breaking on this layout will also break the OP's layout. With this keyboard layout set, pressing single-quote then a gives you á, while pressing double-quote then e results in ë. 3.3.1 works as expected, master actually swallows both single and double-quote. Nothing is jumping out in the change log for GHOST_SystemWin32.cpp. This might have to be bisected.

Tested various releases and found that the issue comes from 2.93.0. I mean, from 2.92.0 to 2.93.0, something changed in the code and brought this issue.

result of typing p~ao

blender 2.92.0
b2.92.0.png

blender 2.93.0
b2.93.0.png

Tested various releases and found that the issue comes from 2.93.0. I mean, from 2.92.0 to 2.93.0, something changed in the code and brought this issue. result of typing p~ao **blender 2.92.0** ![b2.92.0.png](https://archive.blender.org/developer/F14051399/b2.92.0.png) **blender 2.93.0** ![b2.93.0.png](https://archive.blender.org/developer/F14051402/b2.93.0.png)
Member

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

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

Whoops, did not see this is Linux. Can't confirm

Whoops, did not see this is Linux. Can't confirm
Member

This comment was removed by @Harley

*This comment was removed by @Harley*

It may work differently depending on the operating system.
I am using Ubuntu 22.04.1 LTS with br as keyboard layout and can't test in other OS.

I just tested version 3.3.2 and the problem persists.

The last version of blender that is working as expected (in my PC), is really 2.92.0

It may work differently depending on the operating system. I am using Ubuntu 22.04.1 LTS with **br** as keyboard layout and can't test in other OS. I just tested version 3.3.2 and the problem persists. The last version of blender that is working as expected (in my PC), is really 2.92.0
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Perhaps related to #95410 (Regression: Blender text editor lost support for dead keys)
@Chimp can you confirm?

Perhaps related to #95410 (Regression: Blender text editor lost support for dead keys) @Chimp can you confirm?

Yeah.
The support to "dead-keys" was broken in the migration from 2.92.0 to 2.93.0 and persist to current version.
OP of #95410is describing the same thing I am doing here, even though he is using the Text Editor and I am using the Text Objet in Edit Mode.

Yeah. The support to "dead-keys" was broken in the migration from 2.92.0 to 2.93.0 and persist to current version. OP of **#95410**is describing the same thing I am doing here, even though he is using the **Text Editor** and I am using the **Text Objet** in *Edit Mode*.
Member

Thanks, I think we can merge both the reports.

Thanks, I think we can merge both the reports.
Member

Before that, can you verify whether the same problem also happens in text editor?

Before that, can you verify whether the same problem also happens in text editor?

Hi, Pratik !

Sorry. I think I didn't clarify properly.
I had tested it before sending my last reply.

Blender 2.92.0 works (Text Editor / Text Object).
from Blender 2.93.0 to 3.3.4, "dead-keys" support is dead :-).

Hi, Pratik ! Sorry. I think I didn't clarify properly. I had tested it before sending my last reply. Blender 2.92.0 works (Text Editor / Text Object). from Blender 2.93.0 to 3.3.4, "dead-keys" support is dead :-).
Member

Closed as duplicate of #95410

Closed as duplicate of #95410
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#103098
No description provided.