Kerning table not read from TTF font #47725

Closed
opened 7 years ago by GottfriedHofmann · 11 comments

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

blender_kerning.png

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

**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 ![blender_kerning.png](https://archive.blender.org/developer/F289053/blender_kerning.png) **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](https://archive.blender.org/developer/F289052/telegrafico.ttf)
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @GottfriedHofmann

Added subscriber: @GottfriedHofmann
mont29 commented 7 years ago
Owner

Added subscriber: @mont29

Added subscriber: @mont29
mont29 commented 7 years ago
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
mont29 closed this issue 7 years ago
mont29 self-assigned this 7 years ago
mont29 commented 7 years ago
Owner

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.

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](http://wiki.blender.org/index.php/Dev:Source/Development/Todo/Tools#Text_Editing_.283D.29).
Collaborator

Added subscriber: @SebastianWitt

Added subscriber: @SebastianWitt
Collaborator

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!

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!
mont29 commented 6 years ago
Owner

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. ;)

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. ;)
Collaborator

Here is my new Approach, now in a diff. :)

Here is my new Approach, now in a diff. :) - > https://developer.blender.org/D2282

Added subscriber: @IanHuang

Added subscriber: @IanHuang

Added subscriber: @frameshift

Added subscriber: @frameshift
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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…
There is no content yet.