[OT and unrelated but it struck me, so I thought I'd share:
if you visit http://dir.gmane.org/index.php?prefix=gmane.emacs
you will see (well, you are probably going to see something larger
than this when you visit):
100093 gmane.emacs.orgmode Org-Mode for GNU Emacs
That's the fourth largest
On 08/26/2015 06:40 PM, Pip Cet wrote:
Okay, I just checked (sorry, had to regenerate the files and that took
some time), and with the current version of Firefox the code I pasted is
unnecessary.
The problem I had with previous Firefox versions is that those decided
on a scale for displaying the
On 08/26/2015 06:35 PM, Rasmus wrote:
Scott Randby writes:
I will experiment a bit to see if I can get the tag solution
working for me. But given the short amount of time I have to get my
pages up (by Sunday), I will probably put the desired HTML code into
the Org file directly until the issu
Okay, I just checked (sorry, had to regenerate the files and that took some
time), and with the current version of Firefox the code I pasted is
unnecessary.
The problem I had with previous Firefox versions is that those decided on a
scale for displaying the SVG that differed from its preferred res
Scott Randby writes:
> I will experiment a bit to see if I can get the tag solution
> working for me. But given the short amount of time I have to get my
> pages up (by Sunday), I will probably put the desired HTML code into
> the Org file directly until the issue is resolved.
Since time is of
Hi,
Pip Cet writes:
> let found = false;
> for (let el of svgdoc.getElementsByTagName("svg")) {
> let width = el.getAttribute("width");
> let height = el.getAttribute("height");
>
> let width_pt = width.match(/^([0-9]*)pt$/)[1];
> let height_pt = height.ma
On 08/26/2015 02:06 PM, Rasmus wrote:
If you can provide a (html) solution that takes into consideration the
issues mentioned on SO that would of course be great. In the age of d3.js
interactivity COULD be an issue (I would always load "interactive svgs"
via JS, but I'm a pretty naïve svg user
I've used interactive SVGs with ox-html output quite a lot, and I found it
necessary to add the following horrible code; I'm not sure it's still
required:
let svgdoc = object.contentDocument;
let svgid = object.id;
if (!svgdoc) {
if (object.parentNode /* XXX why is this n
On 08/26/2015 02:06 PM, Rasmus wrote:
Hi Scott,
Thanks for your bug report.
Scott Randby writes:
When did Org start using the tag for inline image HTML
export?
You should use git-blame to find out if you care.
I don't use the git repository for Org, so I'll just have to leave that
ques
Hi Scott,
Thanks for your bug report.
Scott Randby writes:
> When did Org start using the tag for inline image HTML
> export?
You should use git-blame to find out if you care.
> The problems with the second bit of exported code is that it doesn't
> scale the image to fit the block with 50%
When did Org start using the tag for inline image HTML export?
This is a horrible bug.
I use many SVG images in my documents. Here is a sample bit of Org code:
#+ATTR_HTML: :width 50% :style display: block; margin-right: auto;
margin-left: auto;
[[./graphic-1.svg]]
I used to get this when e
11 matches
Mail list logo
