Note that this discussion has already taken place at https://github.com/jgm/pandoc/issues/261 (over the course of a couple of years). Adding millimeter as a synonym for 0.1 centimeter was easy, but if you want to use vw and vh, just write ![](image.png){ style=50vw } or maybe better ![](image.png){ width=50% } which, depending on your CSS, has mostly the same effect. Finally, I'd rather stick to those units most people understand, If you really need an image that's 1 point wide (really?), you can still write 0.01389 inch. On Monday, July 27, 2015 at 11:56:49 PM UTC+2, BP Jonsson wrote: > > Den 2015-07-27 23:28, Tim St. Clair skrev: > > then if that's the case, what about vw and vh? These are formats used by > > html that are a width and height relative to the browser viewport. I've > > used them. I think once you set an arbitrary restriction in place, an > > exception for it immediately comes up. > > Probably a case can be made for supporting, at least as in passing > through, all units which CSS and LaTeX support. > > CSS: em, ex, ch, rem, vw, vh, vmin, vmax, %, cm, mm, in, px, pt, pc > > LaTeX: pt, mm, cm, in, ex, em, bp, pc, dd, cc, sp > > Note: a CSS "pt" is the same thing as a LaTeX "bp". Perhaps the > HTML reader could replace "pt" with "bp" and the HTML writer > replace "bp" with "pt"? > > The alphabetical list of all the unique abbreviations (thus > ignoring the ambiguity of "pt") is: > > % > bp > cc > ch > cm > dd > em > ex > in > mm > pc > pt > px > rem > sp > vh > vmax > vmin > vw > > /bpj > > > > > On Tuesday, 28 July 2015 06:04:05 UTC+10, mb21 wrote: > >> > >> @BP Josson, added millimeters on my branch as well now: > >> https://github.com/mb21/pandoc/tree/new-image-attributes (although I > >> personally prefer writing 6cm to 60mm ;) > >> > >> On Monday, July 27, 2015 at 8:31:48 PM UTC+2, BP Jonsson wrote: > >>> > >>> Den 2015-07-26 20:22, mb21 skrev: > >>>> Okay, I rebased from master and implemented the link attributes: > >>>> https://github.com/mb21/pandoc/tree/new-image-attributes > >>>> > >>>> Still not quite sure where we're going with this... I don't think we > >>> need > >>>> Attr on every element (it's not worth the effort just for > consistency), > >>> but > >>>> at least on Table and Math, so we can reference tables and equations > in > >>>> documents? > >>>> > >>> > >>> The readme on that branch says: > >>> > >>>> The `width` and `height` attributes on images are treated specially. > >>> When > >>>> used without a unit, the unit is assumed to be pixels. However, any > of > >>>> the following unit identifiers can be used: `px`, `cm`, `in`, `inch` > >>> and > >>>> `%`. There must not be any spaces between the number and the unit. > >>> > >>> Why not `mm` as well? After all millimeters is the 'proper' unit > >>> to use for such things in the metric world. > >>> > >>> /bpj > >>> > >>> > > > > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ac3237e2-c984-4360-a3f2-4c1ff883ff4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.