none
Calculating line spacing leading in Docx RRS feed

  • Question

  • I have some questions on how to calculate the line spacing between lines in a Docx file.

    My requirement is to exactly match Word, not necessarily the OOXML spec, in the spacing between lines in a simple paragraph.

    In order to try to do this, I have built a tool to analyze the differences between my layout and Word's layout. To do so it does the following:

    1. First it generates a (or many) docx files.
    2. Next it creates pdfs from the docx files. It uses Word to render the docx to PDF, and my program to render the docx to PDF. "word.pdf", and "me.pdf"
    3. Then it analyzes the resulting PDFs for differences in layout.

    So, my tool would say:

    1. create a document "template.docx" with 1000 "a" characters in a single run of text with the same properties.
    2. make a "word.pdf" and "me.pdf" from this docx
    3. calculate info from the pdfs, in particular, calculating the line spacing in terms of the calculated leading between a lines ascent and the previous lines descent (our (Ascent + Descent) are identical-ish, so all that differs is the whitespace between lines). I often think of it as the lines whitespace...

    This tool showed me that the leading varies greatly from font to font.

    To depict this, I used the tool to make thousands of these comparisons, in particular generating for:

    1. For each font in system
    2. For "a", "y", and a mix of letters and spaces.
    3. For different font sizes.
    4. For different line spacing types (Single, One and a half, and Double)

    I was hoping to find groupings, such as "this type of font has 1.3 times my calculation of leading". 

    I was able to conclude far less than I had hoped, and was wondering if you could help me further with the issue of calculating line spacing. I'm providing you with a file that is best downloaded and opened in Excel while using the filters in the header row. Note that its not totally complete, there are missing entries, but I doubt they will be a problem for anyone, and I'm going to regenerate it soon but its pretty slow, so I'm finishing up some changes to it first.

    Here is a comparison of the layout of our software, vs the layout of Word's for every font installed on my system, etc. 

    I'm not positive, but I believe the issue could be one of the following:

    1. Word is using a different process than we are to calculate the "leading" of a font. We don't parse the font files ourselves, instead rely on libraries to get font sizing information, and perhaps in the "world of font files" I am missing something, and word is parsing the fonts directly and differently.
    2. Word has some sort of lookup table that handles groups of fonts, or an algorithm, that scales a fonts leadings up or down based on some criteria I am unaware of.
    3. Word is using an additional criteria besides leading, ascent, and descent, to determine line spacing.

    Please feel free to email me at nathanb@windward.net









    Wednesday, August 24, 2016 8:56 PM

Answers

  • Hi Nathan, 

    As we discussed offline, the information you are asking about is an implementation detail that—by design of the standard—is left up to each developer, and which isn’t necessary for file format interoperability.  The information therefore falls outside the scope of our documentation program.  

    Best regards,
    Tom Jebo
    Sr Escalation Engineer
    Microsoft Open Specifications

    Tuesday, September 27, 2016 11:50 PM
    Moderator

All replies

  • Hi Nathan,

    Thank you for your question.  An engineer from the protocols team will contact you soon.


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Thursday, August 25, 2016 12:00 AM
    Moderator
  • Hi Nathan, 

    As we discussed offline, the information you are asking about is an implementation detail that—by design of the standard—is left up to each developer, and which isn’t necessary for file format interoperability.  The information therefore falls outside the scope of our documentation program.  

    Best regards,
    Tom Jebo
    Sr Escalation Engineer
    Microsoft Open Specifications

    Tuesday, September 27, 2016 11:50 PM
    Moderator