Skip to main content
Participant
December 6, 2010
Question

Kerning/Letterspacing Problems with TLF - and more

  • December 6, 2010
  • 1 reply
  • 1162 views

Hello,

I have some troubles with TLF (RichEditableText - editable) and Letterspacing/Kerning.

Problem is, that I my application uses a different rendering-engine on the server-side. Textediting happens with a Flash/Flex Client displaying serverside stored layouts, mass-printing/spoolfile generating again is being done on the server side.

Now Text looks terrible  (currently most annoying when using Verdana , size 10pt). Even when typing the same word twice letterspacing of the two words looks (and is by one Pixel) diffferent.

I could life with some differences happening here and there but the Layout and resulting Paragraph height it is a complete mess. Word wrapping accours on different words in almost every line compared to the serverside template-document.

Last hope is that I am doing things wrong.

Is this correct: 10 point fontsize equals 10 pixel fontsize in Flash (as flash.system.Capabilities always says DPI is 72)?

Fonts being used are embedded in MXML style declaration.

Thanks for any help

Regards

  Andreas

This topic has been closed for replies.

1 reply

December 6, 2010

You don't mention what your server side rendering engine is. Different font rendering and line breaking engines tend to produce different results.

When you are talking about typing the same word twice, do you mean typing it twice in Flash, or are you comparing once in Flash versus once in the other rendering engine?

fwAndiAuthor
Participant
December 6, 2010

The server side rendering engine is a complex system wich produces multiple output formats like PDF, AFP, PCL and so on using own and 3rd Pary Modules. Resulting (printed) Documents do always match each other. I know, that there can be slight differences resulting in an unwanted Linebreak.

But in the TLF output almost nothing looks like it should - it just does not match the template (screenrendering own C# Windows Textengine) or the print output. It is not about pixel, it's such a huge difference, sadly resulting in additional lines:

Picture shows Text in our Design Tool (Windows .NET Application)  - Text is Verdana (regular/bold) 10pt

TLF Version - FontFamily "Verdana", Font-Size: 10

Same Text layouted in Word 2007 matching exaktly our Layout-Tool.

Typing twice I ment typing the same word in tlf editor.

Charspace between "M" and "ü" differs between 3 and 4 pixel, the same happens with "ü" and "l" - which is not a pretty look as you can see in the image.

Regards

  Andreas

December 6, 2010

Using different text engines is going to produce different results.

The issue of line breaks is (mostly) separate from the issue of glyph placement within words. The variance in glyph placement depends on where the word falls on the pixel grid and how the antialiasing routines handle strokes that do not fit perfectly on a pixel line. It's not just TLF that will render the same word differently - your first screenshot shows a difference in how the lowercase ll pair is rendered in the two instances of Müller on the second line. Smaller point sizes are going to give you more visible variances.

But line breaks are another difference you're going to see, and you can't have an expectation that two different line breaking algorithms are going to produce exactly the same output. It looks to me like the TLF text may be slightly larger at 10 pixels than your text in Word at 10 points. You might get a better result by setting the TLF text at 9.9 pixels or some such. But you are never going to be able to iron out all of the differences for arbitrary runs of text.