emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Josh Berry <taeric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] Couple of small fixes in exporting node.js and css content.
Date: Tue, 5 Aug 2014 11:44:53 -0400	[thread overview]
Message-ID: <CAG9v9NndWu-6zT_yX00PH=NYANkHEEPtf3J-vruXJfA2pan9_w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

I've got a toy paper I'm writing where I ran into a couple of issues
exporting to html.  The first issue is related to exporting the source of a
css block that contains proprietary properties.  In short, it looks like a
list is generated for the font face, where a single value was expected.

The second issue may be my fault, so if there is a setting I should change
on my end, apologies and I'll set said setting.  Basically, there is a
cutoff value whereby node.js will insert newlines into the results.  This
was incredibly frustrating as what was turning into a decent looking table
would suddenly become garbage.

In both cases, I did not add a test file.  If it is enough to just copy an
existing test file and trim it down to just these two items, I can
certainly do that.

Finally, apologies if I am doing this incorrectly.  I tried following the
directions on how to contribute as well as I could.

Thanks!

-josh

p.s.  The toy paper is here: http://taeric.github.io/DancingLinks.html
Feedback welcome!

[-- Attachment #2: Type: text/html, Size: 1378 bytes --]

             reply	other threads:[~2014-08-05 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 15:44 Josh Berry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-05 15:41 [PATCH] Couple of small fixes in exporting node.js and css content Josh Berry
2014-08-05  3:25 Josh Berry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG9v9NndWu-6zT_yX00PH=NYANkHEEPtf3J-vruXJfA2pan9_w@mail.gmail.com' \
    --to=taeric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).