From: Jonathan Nogueira <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Subject: Re: Problems with babel reading Japanese paths in Windows
Date: Mon, 14 Mar 2022 21:16:05 +0900 [thread overview]
Message-ID: <CAH112=-47qPETB_QWjjcEHR51ZhgGVBC_FFc04X14TY3b4OvQQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
I did and it seems to work fine, I also tested this using plantuml-mode's
normal compliation procedure.
This seems to specifically be a problem with org-mode and babel's
Thanks for your help!
On Sat, Mar 12, 2022 at 9:49 PM Ihor Radchenko <firstname.lastname@example.org> wrote:
> Jonathan Nogueira <email@example.com> writes:
> > Hi all,
> > I've been working with emacs and org on Windows 10.0.19042 and was
> > trying to get babel to produce plantuml diagrams.
> > I've managed to (I think) narrow the issue down to Babel either not being
> > able to read/write Japanese paths to shell commands, as when I attempt to
> > build the diagrams in folders with only ASCII paths, they build fine, but
> > when babel attempts to execute any source code for paths that contain
> > Japanese characters, babel gives back the cmd error "The System Cannot
> > the Path Specified."
> I do not use Windows, but I recall somewhat relevant discussion on
> planuml recently:
> It seems that plantuml might have some issues with UTF unless you pass
> relevant command line args.
> Did you try to run plantuml manually from windows cmd using the
> problematic path?
[-- Attachment #2: Type: text/html, Size: 2136 bytes --]
next prev parent reply other threads:[~2022-03-14 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:47 Jonathan Nogueira
2022-03-12 12:48 ` Ihor Radchenko
2022-03-14 12:16 ` Jonathan Nogueira [this message]
2022-03-21 7:12 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).