emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Juan Pechiar <juan@pechiar.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: DITAA and Unicode characters [babel]
Date: Mon, 25 Apr 2011 18:58:20 -0600	[thread overview]
Message-ID: <8739l5zv4j.fsf@gmail.com> (raw)
In-Reply-To: <20110426002740.GB4334@soloJazz.com> (Juan Pechiar's message of "Mon, 25 Apr 2011 21:27:40 -0300")

Juan Pechiar <juan@pechiar.com> writes:

> On Mon, Apr 25, 2011 at 01:13:41PM -0600, Eric Schulte wrote:
>> I just pushed up a change to ob-ditaa which adds a new header argument,
>> namely :java through which options can be passed to the java command.
>> With that patch the following should work
>>
>> #+begin_src ditaa :file ... :cmdline -e utf-8 -r -v :java -Dfile.encoding=UTF-8
>>   ...
>> #+end_src
>>
>> Now that there is a :java header argument for ditaa code, the following
>> could be put in a user's init file to set this flag for *all* ditaa code
>> run on their system.
>>
>> #+begin_src emacs-lisp
>>   (push '(:java . "-Dfile.encoding=UTF-8") org-babel-default-header-args:ditaa)
>> #+end_src
>
> Works perfectly! Thanks!
>
>> I wonder if there would be any downside to adding this as a default
>> value?  This could be added to `org-babel-default-header-args:ditaa' in
>> ob-ditaa.el.
>
> I think it'd be a reasonable default that will work out-of-the-box for
> most users.
>

OK, this is now part of the default ditaa header arguments, we'll see if
anyone complains...

Best -- Eric

>
> In case of not using UTF-8, the user can override this setting at
> will as you show above.
>
> Regards,
> .j.

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

      reply	other threads:[~2011-04-26  0:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 23:38 DITAA and Unicode characters [babel] Juan Pechiar
2011-04-25 19:13 ` Eric Schulte
2011-04-26  0:27   ` Juan Pechiar
2011-04-26  0:58     ` Eric Schulte [this message]

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=8739l5zv4j.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=juan@pechiar.com \
    /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).