Kerning table not read from TTF font #47725
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#47725
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Ubuntu 15.10 Geforce GTX 970M
Blender Version
Broken: 2.76b official linux x64
Short description of error
This is an example where the kerning is not read from the TTF kerning table. It works fine in Inkscape 0.91 linux
Exact steps for others to reproduce the error
Download the following ttf, add a text object in Blender, type "av", apply this font:
telegrafico.ttf
Changed status to: 'Open'
Added subscriber: @GottfriedHofmann
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Thanks for the report, but this is more a TODO than a bug, this feature has never been implemented for our 3DText object afaik. Added a note to our TODO list.
Added subscriber: @SebastianWitt
I had a look at adding kerning support and here is my approach:
https://developer.blender.org/P407
I don't think it is a very elegant approach. It adds a new Hashtable to the "VFontData" struct which is quite big up to (36481) for systemfonts and the blender default font which doesn't even support kerning.
The Hashtable saves all possible character pairs. If there is a better datastruct to store the necessary data let me know. (ghash is also quite confusing)
I will experiment with other approaches, only saving the kerning values > 0.
For now I'm happy about every bit of feedback!
Thanks for the work and patch, but would indeed really not go that way… Thing is, we already have kerning support for all our UI code, using iirc freetype lib helpers for that. So suggest you check code in
blenfont
dir and see how to hook it into 3D fonts code? Really don’t think we need to bake all possible kernings into own ghash.Also, probably better to create a new diff to get review on your patch once ready, comments in closed bug report is not so handy to manage. ;)
Here is my new Approach, now in a diff. :)
Added subscriber: @IanHuang
Added subscriber: @frameshift