dvipdfmx can not process .dvi, creating an error in the case using a single texlive2018 version
Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.
I encounter the error message in the second dvipdfmx saying,
DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a
DVI file? Output file removed.
Still the process continues and somehow looks to produce .pdf.
I would like to know the cause of this error and fix it.
Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.
Environment:
TeXstudio: 2.12.14
Qt: (I do not know ! )
OS: Windows10
TeX distribution: texlive 2018
Expected behavior:
It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1
At this point of processing, it might be like that a C compiler spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.
Actual behavior ( Sorry for some Japanese messages included):
The start of log message:
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written
プロセスは正常に終了しました
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.
プロセスはエラー終了しました
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written
プロセスは正常に終了しました
開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"
How to reproduce:
It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia society.
texlive dvi dvipdfmx
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
asked Feb 28 at 4:28
TomTom
1
add a comment |
Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.
I encounter the error message in the second dvipdfmx saying,
DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a
DVI file? Output file removed.
Still the process continues and somehow looks to produce .pdf.
I would like to know the cause of this error and fix it.
Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.
Environment:
TeXstudio: 2.12.14
Qt: (I do not know ! )
OS: Windows10
TeX distribution: texlive 2018
Expected behavior:
It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1
At this point of processing, it might be like that a C compiler spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.
Actual behavior ( Sorry for some Japanese messages included):
The start of log message:
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written
プロセスは正常に終了しました
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.
プロセスはエラー終了しました
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written
プロセスは正常に終了しました
開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"
How to reproduce:
It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia society.
texlive dvi dvipdfmx
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
asked Feb 28 at 4:28
TomTom
1
1
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it tomwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!
– Kurt
Feb 28 at 5:00
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
1
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36
add a comment |
Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.
I encounter the error message in the second dvipdfmx saying,
DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a
DVI file? Output file removed.
Still the process continues and somehow looks to produce .pdf.
I would like to know the cause of this error and fix it.
Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.
Environment:
TeXstudio: 2.12.14
Qt: (I do not know ! )
OS: Windows10
TeX distribution: texlive 2018
Expected behavior:
It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1
At this point of processing, it might be like that a C compiler spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.
Actual behavior ( Sorry for some Japanese messages included):
The start of log message:
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written
プロセスは正常に終了しました
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.
プロセスはエラー終了しました
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written
プロセスは正常に終了しました
開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"
How to reproduce:
It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia society.
texlive dvi dvipdfmx
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
asked Feb 28 at 4:28
TomTom
1
Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.
I encounter the error message in the second dvipdfmx saying,
DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a
DVI file? Output file removed.
Still the process continues and somehow looks to produce .pdf.
I would like to know the cause of this error and fix it.
Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.
Environment:
TeXstudio: 2.12.14
Qt: (I do not know ! )
OS: Windows10
TeX distribution: texlive 2018
Expected behavior:
It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1
At this point of processing, it might be like that a C compiler spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.
Actual behavior ( Sorry for some Japanese messages included):
The start of log message:
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written
プロセスは正常に終了しました
開始されたプロセス: upbibtex.exe "xxxxxx"
This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex
xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.
プロセスはエラー終了しました
(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)
プロセスは正常に終了しました
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written
プロセスは正常に終了しました
開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"
How to reproduce:
It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia society.
texlive dvi dvipdfmx
texlive dvi dvipdfmx
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
asked Feb 28 at 4:28
TomTom
1
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
asked Feb 28 at 4:28
TomTom
1
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
edited Feb 28 at 5:04
Stefan Pinnow
20.1k83276
20.1k83276
asked Feb 28 at 4:28
TomTom
1
asked Feb 28 at 4:28
TomTom
1
asked Feb 28 at 4:28
TomTom
1
1
1
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it tomwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!
– Kurt
Feb 28 at 5:00
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
1
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36
add a comment |
1
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it tomwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!
– Kurt
Feb 28 at 5:00
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
1
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36
1
1
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it to
mwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!– Kurt
Feb 28 at 5:00
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it to
mwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!– Kurt
Feb 28 at 5:00
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
1
1
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477086%2fdvipdfmx-can-not-process-dvi-creating-an-error-in-the-case-using-a-single-texl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477086%2fdvipdfmx-can-not-process-dvi-creating-an-error-in-the-case-using-a-single-texl%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Welcome to TeX.SE! You need not to show us the original document, copy it, rename it to
mwe.tex, reduce it by using dummy text to be minimal, but resulting in your error. Add this minimal tex code to your question. Then we can copy it and play with it to find the problem. Without any code it is nearly sure impossible to help you!– Kurt
Feb 28 at 5:00
Hi there are a few Japanese W32TeX supporters here but your heading as it is may not attract their attention. Myself and many other users may not be aware of the sequencing you need to go through but my understanding is that it would only be one dvipdfmx at the end of uplatex file > upbibtex file > uplatex file > uplatex file > dvipdfmx file this is based on my understanding of the advice here mytexpert.osdn.jp/index.php?BibTeX however there is additional related guidance here that may help ? texwiki.texjp.org/?upTeX,upLaTeX
– KJO
Feb 28 at 5:14
1
I doubt that this is a tex problem, it looks as if the following platex call is starting before dvipdfmx has finished (and so deletes the dvi).
– Ulrike Fischer
Feb 28 at 9:43
The command sequence is automatically determined by TexStudio setting and not by me. I now notice the seqence is totall different from that in Bibtex document; mytexpert.osdn.jp/index.php?BibTeX. I do not know how to change that sequence in texstudio ! Why is it set like this ? Shall I go back to Texstudio forum again ?
– Tom
Mar 1 at 3:36