code that I was running
"python -m manim by_me.py AddingText -pl"
error
"Sorry, but latex did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:\Users\ABDUL BASID\AppData\Local\MiKTeX\2.9\miktex\log\latex.log
Traceback (most recent call last):
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\extract_scene.py", line 153, in main
scene = SceneClass(*scene_kwargs)
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\scene\scene.py", line 54, in __init__
self.construct()
File "by_me.py", line 63, in construct
my_first_text=TextMobject("Hi Boys And Girls.")
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\mobject\svg\tex_mobject.py", line 144, in __init__
self, self.arg_separator.join(tex_strings), *kwargs
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\mobject\svg\tex_mobject.py", line 45, in __init__
self.template_tex_file_body
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\utils\tex_file_writing.py", line 19, in tex_to_svg_file
dvi_file = tex_to_dvi(tex_file)
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\utils\tex_file_writing.py", line 67, in tex_to_dvi
"See log output above or the log file: %s" % log_file)
Exception: Latex error converting to dvi. See log output above or the log file: C:\Users\ABDUL BASID\Desktop\manim\manimlib\files\Tex\aea35df66c5e66f2.log"
generated files are-
latex.log
7699645c4ce2f717.log
please help! I have got stuck
it's painful to not figure out what's happening and also searching on google does not help much.
thankyou in advance
@abecus I made a fork that solves this issue. You can ignore the installation requirements that I modified. It basically involved putting double quotes around the paths to solve the problem. I suspect that the space in "ABDUL BASID" is causing the problem as the OS splits commands separated by spaces. Putting the path in double quotes tells the OS to treat the path string as one whole argument.
@abecus I made a fork that solves this issue. You can ignore the installation requirements that I modified. It basically involved putting double quotes around the paths to solve the problem. I suspect that the space in "ABDUL BASID" is causing the problem as the OS splits commands separated by spaces. Putting the path in double quotes tells the OS to treat the path string as one whole argument.
indeed it worked by just changing the "tex_file_writing.py" file to yours.
thank you very much!!!
that was pain bro...
code that I was running
"python -m manim by_me.py AddingText -pl"error
"Sorry, but latex did not succeed.The log file hopefully contains the information to get MiKTeX going again:
C:\Users\ABDUL BASID\AppData\Local\MiKTeX\2.9\miktex\log\latex.log
Traceback (most recent call last):
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\extract_scene.py", line 153, in main
scene = SceneClass(scene_kwargs)
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\scene\scene.py", line 54, in *init
self.construct()
File "by_me.py", line 63, in construct
my_first_text=TextMobject("Hi Boys And Girls.")
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\mobject\svg\tex_mobject.py", line 144, in init
self, self.arg_separator.join(tex_strings), kwargs
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\mobject\svg\tex_mobject.py", line 45, in *init
self.template_tex_file_body
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\utils\tex_file_writing.py", line 19, in tex_to_svg_file
dvi_file = tex_to_dvi(tex_file)
File "C:\Users\ABDUL BASID\Desktop\manim\manimlib\utils\tex_file_writing.py", line 67, in tex_to_dvi
"See log output above or the log file: %s" % log_file)
Exception: Latex error converting to dvi. See log output above or the log file: C:\Users\ABDUL BASID\Desktop\manim\manimlib\files\Tex\aea35df66c5e66f2.log"generated files are-
latex.log
7699645c4ce2f717.logplease help! I have got stuck
it's painful to not figure out what's happening and also searching on google does not help much.
thankyou in advance
I met the same problem like yours, and I searched the Stack Overflow. I installed MIkTex, this problem has been solved. I think this problem is caused by lack of font library.
Hey I am getting the same problem. Can anyone guide me how to go about things. Please use simple words. I am slow at absorbing things
It will be very easy if you use docker to deploy the development environment for manim.
can you please share the steps on how to do that?
my env
root@golemECS2:~# uname -a
Linux golemECS2 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Steps
- Install
dockeranddocker-compose
Refer to docker and docker-compose- Set envionment variables
INPUT_PATHandOUTPUT_PATH
shell root@golemECS2:~# cd ~ && cat << EOF > .bashrc export INPUT_PATH=/root/manim/code export OUTPUT_PATH=/root/manim/output EOF- test
shell git clone https://github.com/3b1b/manim.git && cd manim cp example_scenes.py docker-compose.yml $INPUT_PATH && cd $INPUT_PATH docker-compose run manim example_scenes.py SquareToCircle -l
Thanks for the reply. Will try
On Tue, 26 May 2020, 06:58 Golem, notifications@github.com wrote:
my env
root@golemECS2:~# uname -a
Linux golemECS2 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxSteps
- Install docker and docker-compose
Refer to docker https://docs.docker.com/ and docker-compose
https://docs.docker.com/compose/install/Set envionment variables INPUT_PATH and OUTPUT_PATH
root@golemECS2:~# cd ~ && cat << EOF > .bashrc>export INPUT_PATH=/root/manim/code>export OUTPUT_PATH=/root/manim/output>EOF
test
git clone https://github.com/3b1b/manim.git && cd manim
cp example_scenes.py docker-compose.yml $INPUT_PATH && cd $INPUT_PATH
docker-compose run manim example_scenes.py SquareToCircle -l—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/3b1b/manim/issues/453#issuecomment-633762884, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APWOXR6CVXAFRV3D2U4YS3LRTMLLPANCNFSM4GZZRXAA
.
Most helpful comment
@abecus I made a fork that solves this issue. You can ignore the installation requirements that I modified. It basically involved putting double quotes around the paths to solve the problem. I suspect that the space in "ABDUL BASID" is causing the problem as the OS splits commands separated by spaces. Putting the path in double quotes tells the OS to treat the path string as one whole argument.