Closed llcc closed 10 years ago
Dear John.
This time I put the code in a separate .el file and load it again, it works perfectly. But this is a little bug.
I use Japanese to write my papers, although I save the document as unicode, it seems the produced the .tex file is a kind of Japanese coding, which make Japanese word of the final pdf messed. I have changed all the related encoding to utf-8, but it still does not work.
Do you have any idea to solve it?
I cannot reproduce your first problem. With an org-file open, I type C-c C-e j s (I just added the s option, so you will need an updated version of ox-manuscript), and The resulting tex file is what I expect it to be.
For the second issue I have no idea. That seems like a latex issue to me. do you use this:
\usepackage[AUTO]{inputenc} \usepackage[T1]{fontenc}
in your file?
hm.. that is strange. That sounds like some kind of weird invisible character to me. How did you download the el file?
John
John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
On Fri, Apr 25, 2014 at 11:42 PM, llcc notifications@github.com wrote:
Dear John.
This time I put the code in a separate .el file and load it again, it works perfectly. But this is a little bug.
I use Japanese to write my papers, although I save the document as unicode, it seems the produced the .tex file is a kind of Japanese coding, which make Japanese word of the final pdf messed. I have changed all the related encoding to utf-8, but it still does not work.
Do you have any idea to solve it?
— Reply to this email directly or view it on GitHubhttps://github.com/jkitchin/jmax/issues/8#issuecomment-41458886 .
I copied the whole codes and put them in a file, then load, works well.
I have found the problems that make my .tex messed up, it is because i set the language to the Japanese. After i removed it, that problem disappeared.
I want to bind you ox-manuscript-build-submission-manuscript
to F3 with async property, i used the code below
(global-set-key [f3]
(lambda () (interactive)
(ox-manuscript-build-submission-manuscript t)))
but it does not work, there is something wrong of my binding?
On Sat, Apr 26, 2014 at 10:02 AM, llcc notifications@github.com wrote:
(global-set-key [f3](lambda %28%29 %28interactive%29 %28ox-manuscript-build-submission-manuscript t%29))
That looks right. I also cannot export with async t. Not even with the org export. I wonder if it is a bug in org-mode. I never use async, so I am not sure. If you remove the t from the command above, it works fine, just not asynchronously.
John
John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
Yes, when I remove t, it works perfect.
Thanks for your help, you really do me a great favor.
Best regards!
Great! I am glad it is working! Best wishes,
John
John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
On Sat, Apr 26, 2014 at 10:10 AM, llcc notifications@github.com wrote:
Yes, when I remove t, it works perfect.
Thanks for your help, you really do me a great favor.
Best regards!
— Reply to this email directly or view it on GitHubhttps://github.com/jkitchin/jmax/issues/8#issuecomment-41469697 .
Dear John.
I am the guy who asked the question about interrupting the org-export process in org-mode mailing list. I spent hours for reading your ox-manuscript.el, finally I think I got something really good.
Then I use your package in my org-mode. I leave a .tex in my exporting directory and called the
ox-manuscript-remove-image-extensions
, it successfully removes .png. However when i call theox-manuscript-build-submission-manuscript
, the .png still exists in the intermediate .tex file. But I have seen theox-manuscript-remove-image-extensions
in the latter command. Why it does nothing?Thank you very much for your help.