Gibberish string prepended to deleted text in the PDF obtained by compiling 'diff' file generated by...
I am using latexdiff for marking up corrections requested by the examiners to my PhD thesis. I have a strange issue with this.
Upon compiling the diff.tex file, I get a specific string 4.0pt=-.55ex at the beginning of each deleted text throughout the document. See this figure.

In the source file diff.tex, the highlighted entires correspond to these lines
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
The preamble generated by latexdiff for this diff.tex defines these commands as follows
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}} %DIF PREAMBLE
I have tried searching for the string 4.0pt=-.55ex in the diff.tex file, but not even a portion of this exists anywhere! From where is this spurious string originating, and how do I get rid of this problem?
strings debugging latexdiff changes bugs
add a comment |
I am using latexdiff for marking up corrections requested by the examiners to my PhD thesis. I have a strange issue with this.
Upon compiling the diff.tex file, I get a specific string 4.0pt=-.55ex at the beginning of each deleted text throughout the document. See this figure.

In the source file diff.tex, the highlighted entires correspond to these lines
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
The preamble generated by latexdiff for this diff.tex defines these commands as follows
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}} %DIF PREAMBLE
I have tried searching for the string 4.0pt=-.55ex in the diff.tex file, but not even a portion of this exists anywhere! From where is this spurious string originating, and how do I get rid of this problem?
strings debugging latexdiff changes bugs
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01
add a comment |
I am using latexdiff for marking up corrections requested by the examiners to my PhD thesis. I have a strange issue with this.
Upon compiling the diff.tex file, I get a specific string 4.0pt=-.55ex at the beginning of each deleted text throughout the document. See this figure.

In the source file diff.tex, the highlighted entires correspond to these lines
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
The preamble generated by latexdiff for this diff.tex defines these commands as follows
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}} %DIF PREAMBLE
I have tried searching for the string 4.0pt=-.55ex in the diff.tex file, but not even a portion of this exists anywhere! From where is this spurious string originating, and how do I get rid of this problem?
strings debugging latexdiff changes bugs
I am using latexdiff for marking up corrections requested by the examiners to my PhD thesis. I have a strange issue with this.
Upon compiling the diff.tex file, I get a specific string 4.0pt=-.55ex at the beginning of each deleted text throughout the document. See this figure.

In the source file diff.tex, the highlighted entires correspond to these lines
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
The preamble generated by latexdiff for this diff.tex defines these commands as follows
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}} %DIF PREAMBLE
I have tried searching for the string 4.0pt=-.55ex in the diff.tex file, but not even a portion of this exists anywhere! From where is this spurious string originating, and how do I get rid of this problem?
strings debugging latexdiff changes bugs
strings debugging latexdiff changes bugs
asked Dec 31 '18 at 15:58
KrishnaKrishna
956618
956618
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01
add a comment |
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01
add a comment |
1 Answer
1
active
oldest
votes
My crystal ball says that you are redefining ULdepth:
documentclass{article}
usepackage{color}
usepackage{ulem}
renewcommandULdepth{4.0pt} %<--- wrong
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}}
begin{document}
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
end{document}
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using theulempackage with this custom depth in my thesis. How can I make this work with theunderlinestyle provided bylatexdiff?
– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister withrenewcommandyou should set the length withsetlengthnot redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.
– David Carlisle
Dec 31 '18 at 19:06
1
UsesetlengthULdepth{4pt}instead.
– Ulrike Fischer
Dec 31 '18 at 20:03
1
@KrishnaULthicknessis a macro which should be redefined withrenewcommand, not a length register,
– David Carlisle
Dec 31 '18 at 20:16
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
|
show 3 more comments
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%2f468045%2fgibberish-string-prepended-to-deleted-text-in-the-pdf-obtained-by-compiling-dif%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
My crystal ball says that you are redefining ULdepth:
documentclass{article}
usepackage{color}
usepackage{ulem}
renewcommandULdepth{4.0pt} %<--- wrong
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}}
begin{document}
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
end{document}
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using theulempackage with this custom depth in my thesis. How can I make this work with theunderlinestyle provided bylatexdiff?
– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister withrenewcommandyou should set the length withsetlengthnot redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.
– David Carlisle
Dec 31 '18 at 19:06
1
UsesetlengthULdepth{4pt}instead.
– Ulrike Fischer
Dec 31 '18 at 20:03
1
@KrishnaULthicknessis a macro which should be redefined withrenewcommand, not a length register,
– David Carlisle
Dec 31 '18 at 20:16
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
|
show 3 more comments
My crystal ball says that you are redefining ULdepth:
documentclass{article}
usepackage{color}
usepackage{ulem}
renewcommandULdepth{4.0pt} %<--- wrong
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}}
begin{document}
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
end{document}
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using theulempackage with this custom depth in my thesis. How can I make this work with theunderlinestyle provided bylatexdiff?
– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister withrenewcommandyou should set the length withsetlengthnot redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.
– David Carlisle
Dec 31 '18 at 19:06
1
UsesetlengthULdepth{4pt}instead.
– Ulrike Fischer
Dec 31 '18 at 20:03
1
@KrishnaULthicknessis a macro which should be redefined withrenewcommand, not a length register,
– David Carlisle
Dec 31 '18 at 20:16
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
|
show 3 more comments
My crystal ball says that you are redefining ULdepth:
documentclass{article}
usepackage{color}
usepackage{ulem}
renewcommandULdepth{4.0pt} %<--- wrong
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}}
begin{document}
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
end{document}
My crystal ball says that you are redefining ULdepth:
documentclass{article}
usepackage{color}
usepackage{ulem}
renewcommandULdepth{4.0pt} %<--- wrong
providecommand{DIFdelbegin}{} %DIF PREAMBLE
providecommand{DIFdelend}{} %DIF PREAMBLE
providecommand{DIFdel}[1]{{protectcolor{red}sout{#1}}}
begin{document}
DIFdelbegin DIFdel{references are }DIFdelend
DIFdelbegin DIFdel{textbf{modified}}DIFdelend
DIFdelbegin DIFdel{Creative Commons Attribution ...}DIFdelend
DIFdelbegin DIFdel{they attribute it, that they :}DIFdelend
DIFdelbegin DIFdel{that they do not alter, transform ...}DIFdelend
end{document}
answered Dec 31 '18 at 18:33
Ulrike FischerUlrike Fischer
187k7292672
187k7292672
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using theulempackage with this custom depth in my thesis. How can I make this work with theunderlinestyle provided bylatexdiff?
– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister withrenewcommandyou should set the length withsetlengthnot redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.
– David Carlisle
Dec 31 '18 at 19:06
1
UsesetlengthULdepth{4pt}instead.
– Ulrike Fischer
Dec 31 '18 at 20:03
1
@KrishnaULthicknessis a macro which should be redefined withrenewcommand, not a length register,
– David Carlisle
Dec 31 '18 at 20:16
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
|
show 3 more comments
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using theulempackage with this custom depth in my thesis. How can I make this work with theunderlinestyle provided bylatexdiff?
– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister withrenewcommandyou should set the length withsetlengthnot redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.
– David Carlisle
Dec 31 '18 at 19:06
1
UsesetlengthULdepth{4pt}instead.
– Ulrike Fischer
Dec 31 '18 at 20:03
1
@KrishnaULthicknessis a macro which should be redefined withrenewcommand, not a length register,
– David Carlisle
Dec 31 '18 at 20:16
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using the
ulem package with this custom depth in my thesis. How can I make this work with the underline style provided by latexdiff?– Krishna
Dec 31 '18 at 18:53
@UlrikeFisher, happy new year. Prima facie, your crystal ball indeed seems to be correct. Only the underline based styles have a problem. I am already using the
ulem package with this custom depth in my thesis. How can I make this work with the underline style provided by latexdiff?– Krishna
Dec 31 '18 at 18:53
@Krishna it's always wrong to redefine a length resgister with
renewcommand you should set the length with setlength not redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.– David Carlisle
Dec 31 '18 at 19:06
@Krishna it's always wrong to redefine a length resgister with
renewcommand you should set the length with setlength not redefine it so it is no longer a length. that is true in general not just for ulem or latexdiff.– David Carlisle
Dec 31 '18 at 19:06
1
1
Use
setlengthULdepth{4pt} instead.– Ulrike Fischer
Dec 31 '18 at 20:03
Use
setlengthULdepth{4pt} instead.– Ulrike Fischer
Dec 31 '18 at 20:03
1
1
@Krishna
ULthickness is a macro which should be redefined with renewcommand, not a length register,– David Carlisle
Dec 31 '18 at 20:16
@Krishna
ULthickness is a macro which should be redefined with renewcommand, not a length register,– David Carlisle
Dec 31 '18 at 20:16
2
2
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
ULdepth and ULthickness is not the same.
– Ulrike Fischer
Dec 31 '18 at 20:18
|
show 3 more comments
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f468045%2fgibberish-string-prepended-to-deleted-text-in-the-pdf-obtained-by-compiling-dif%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
as always it would be much easier to help if you provided an example.
– David Carlisle
Dec 31 '18 at 18:01