Re: [xml2rfc-dev] [Ext] RFC 7991 issue #39: Schema Issue, RFC 7991, New Section 2.20.4, "indent" Attribute

[Henrik Levkowetz <[e-mail]>]

On 2018-10-07 22:20, Paul Hoffman wrote:
> On Oct 7, 2018, at 8:18 AM, Henrik Levkowetz <[e-mail]> wrote:
>> The reason I expressed this in en-space is that as a rule of thumb, the
>> average character width in a proportional font is 1 en.  If we apply the
>> indent figure as number of em-spaces, the visual impression will be a
>> much larger indentation when using proportional fonts than for monospaced
>> fonts.
> 
> This makes sense, but the reason I proposed using the em unit earlier
> is that em is defined in CSS, but (I'm pretty sure) en is not. This
> would make the HTML much easier to render directly, I think.

I understand, but I think I covered this in both my first (and second,
just now) proposal.  

---
2.20.4.  "indent" Attribute

   Indicates the indentation to be used for the second and following
   lines of item rendering (the first line starts with the term, and
   is not indented).  The indentation is to be interpreted as characters
   in text/plain rendering, and en-space units when using renderings
   with richer typographic support, such as html or pdf.  One en-space is
   assumed to be the length of 0.5 em-space in CSS units.
---

The reason to use en-space is to get a comparable rendering.  Equating
one character step with an em-space results in very different renderings.
Using steps of 0.5em in CSS is trivial.

If it makes you happier, we could change the text above to say

   ... the length 0.5em in CSS units.



	Henrik