HTeuMeuLeu’s avatarHTeuMeuLeu’s Twitter Archive—№ 22,876

          1. I recently stumbled upon a Microsoft document named “[MS-OI29500].pdf”. It’s a masterpiece detailing how Microsoft Office (including Outlook) differs from standards it implements. And yes, it is 922 pages long. Here are a few points that caught my eyes.👇#emailgeeks #emailpeeps
        1. …in reply to @HTeuMeuLeu
          Outlook doesn’t support the value auto for properties like margin, width or height. I’ve known this for a while from experience. But this is the first time I see this written in an official documentation.
      1. …in reply to @HTeuMeuLeu
        In VML, any unit inside a <v:group> will just result in the same value. And that value will be based on the coordsize attribute of the group.
    1. …in reply to @HTeuMeuLeu
      There’s also an explanation behind the reasoning behind the mso-width-percent property and its weird values. Yup, that’s right, the property is named “percent” but the expected value must be “between 10 and 10,000, where each unit is a tenth of a percent”. 🤦‍♂️
  1. …in reply to @HTeuMeuLeu
    And then there’s this section about fonts: “Word reads [TrueType] fonts if the value of the fontKey attribute is equal to 00000000-0000-0000-0000-000000000000.” I know that @​font-face is supported in The Outlooks but never managed to get a font to load. Could this be a key?
    1. …in reply to @HTeuMeuLeu
      Anyway I'm sure this document is full of other wonders to be discovered about Word’s rendering engine. 🔍 Here’s a direct link to the PDF: interoperability.blob.core.windows.net/files/MS-OI29500/%5bMS-OI29500%5d.pdf (17 Mb) The content is also readable and searchable online: docs.microsoft.com/en-us/openspecs/office_standards/ms-oi29500/1fd4a662-8623-49c0-82f0-18fa91b413b8