Mdthbs

Am I allowed to determine tenets of my contract as a warlock?

A life of PhD: is it feasible?

In Pandemic, why take the extra step of eradicating a disease after you've cured it?

Can you open the door or die? v2

Can I use 220 V outlets on a 15 ampere breaker and wire it up as 110 V?

What do you call the action of "describing events as they happen" like sports anchors do?

My mom's return ticket is 3 days after I-94 expires

What is Gilligan's full name?

Do Veracrypt encrypted volumes have any kind of brute force protection?

Is the first of the 10 Commandments considered a mitzvah?

LWC: detect last element in for:each iteration

Is Jesus the last Prophet?

How do I type a hyphen in iOS 12?

What is the language spoken in Babylon?

How can calculate the turn-off time of an LDO?

Is it good practice to create tables dynamically?

If absolute velocity does not exist, how can we say a rocket accelerates in empty space?

Can I get a photo of an Ancient Arrow?

In The Incredibles 2, why does Screenslaver's name use a pun on something that doesn't exist in the 1950s pastiche?

Dedicated bike GPS computer over smartphone

Which are the methodologies for interpreting Vedas?

Why is my Taiyaki (Cake that looks like a fish) too hard and dry?

Can an open source licence be revoked if it violates employer's IP?

Approach sick days in feedback meeting

Undocumented incompatibility between changes and siunitx?

Differences between SIunits and siunitx packagesConflict between glossaries and siunitx (possibly via hyperref) when defining colorHow can I use SI from siunitx inside replaced from changes?Tracking changesIs there an incompatibility between siunitx and skmath packages?Incompatibility between siunitx and gb4eIncompatibility of siunitx and sansmath?Automatically recognize unit prefix in siunitxUndefined control sequence when running siunitxsiunitx spacing between 10 and exponent

3

I am currently using the changes package to track some modifications in a document, along with the siunitx package for number formatting.

Whenever I try to have a SI{}{} call iside a replaced{}{} or deleted{} call, pdflatex throws me an error though the ouput file seems fine.

This issue does not seem to be documented, either in the user manual or on the git repo.

Here is a MWE to illustrate the issue

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.

end{document}

Any idea how to remove this error, as it does not seem to impact the result ?

EDIT : Here is the link to the issue on the Git repo

siunitx changes

share|improve this question

edited 7 hours ago

BambOo

asked 9 hours ago

BambOoBambOo

3,1151527

add a comment | 

3

I am currently using the changes package to track some modifications in a document, along with the siunitx package for number formatting.

Whenever I try to have a SI{}{} call iside a replaced{}{} or deleted{} call, pdflatex throws me an error though the ouput file seems fine.

This issue does not seem to be documented, either in the user manual or on the git repo.

Here is a MWE to illustrate the issue

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.

end{document}

Any idea how to remove this error, as it does not seem to impact the result ?

EDIT : Here is the link to the issue on the Git repo

siunitx changes

share|improve this question

edited 7 hours ago

BambOo

asked 9 hours ago

BambOoBambOo

3,1151527

add a comment | 

I am currently using the changes package to track some modifications in a document, along with the siunitx package for number formatting.

Whenever I try to have a SI{}{} call iside a replaced{}{} or deleted{} call, pdflatex throws me an error though the ouput file seems fine.

This issue does not seem to be documented, either in the user manual or on the git repo.

Here is a MWE to illustrate the issue

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.

end{document}

Any idea how to remove this error, as it does not seem to impact the result ?

EDIT : Here is the link to the issue on the Git repo

siunitx changes

share|improve this question

edited 7 hours ago

BambOo

asked 9 hours ago

BambOoBambOo

3,1151527

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.

end{document}

share|improve this question

edited 7 hours ago

BambOo

asked 9 hours ago

BambOoBambOo

3,1151527

share|improve this question

edited 7 hours ago

BambOo

asked 9 hours ago

BambOoBambOo

3,1151527

asked 9 hours ago

BambOoBambOo

3,1151527

asked 9 hours ago

BambOoBambOo

3,1151527

2 Answers
2

active

oldest

votes

9

changes uses internally the ulem package, and this can't handle complicated macros. You normally should hide them in a mbox:

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{mbox{SI{8}{meter}}}.

This is a new length of replaced{mbox{SI{8}{meter}}}{mbox{SI{3}{meter}}}.

end{document}

share|improve this answer

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?
  
  – BambOo
  9 hours ago
  

  
  
  
  

add a comment | 

5

You can provisionally redefine SI to use mbox around it.

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



ExplSyntaxOn

RenewDocumentCommand SI { o m o m } {

 mbox{

   bool_set_false:N l__siunitx_font_set_bool

   IfNoValueTF {#1}

     { __siunitx_combined:nnnn { } {#2} {#3} {#4} }

     {

       keys_set:nn { siunitx } {#1}

       __siunitx_combined:nnnn {#1} {#2} {#3} {#4}

     }

 }

}

ExplSyntaxOff





begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

I'd prefer a changes method that avoids striking out (color would be sufficient).

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



setdeletedmarkup{textcolor{red}{#1}}



begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

share|improve this answer

answered 8 hours ago

egregegreg

748k8919553298

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I am flying blind here, but would it not be better to patch changes instead ? The error popped up with siunitx but it may also happen with other commands right.
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  BTW, I just opened an issue on the git repo of the package
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BambOo The problem is that mbox can not be broken across lines... that's not a problem for SI{}{}, but can be for long deleted{...} phrases...
  
  – Rmano
  7 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Rmano I did not see that, you're right !
  
  – BambOo
  7 hours ago
  

  
  
  
  

add a comment | 

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
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f495288%2fundocumented-incompatibility-between-changes-and-siunitx%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

9

changes uses internally the ulem package, and this can't handle complicated macros. You normally should hide them in a mbox:

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{mbox{SI{8}{meter}}}.

This is a new length of replaced{mbox{SI{8}{meter}}}{mbox{SI{3}{meter}}}.

end{document}

share|improve this answer

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?
  
  – BambOo
  9 hours ago
  

  
  
  
  

add a comment | 

9

changes uses internally the ulem package, and this can't handle complicated macros. You normally should hide them in a mbox:

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{mbox{SI{8}{meter}}}.

This is a new length of replaced{mbox{SI{8}{meter}}}{mbox{SI{3}{meter}}}.

end{document}

share|improve this answer

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?
  
  – BambOo
  9 hours ago
  

  
  
  
  

add a comment | 

changes uses internally the ulem package, and this can't handle complicated macros. You normally should hide them in a mbox:

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{mbox{SI{8}{meter}}}.

This is a new length of replaced{mbox{SI{8}{meter}}}{mbox{SI{3}{meter}}}.

end{document}

share|improve this answer

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}

begin{document}

This is a new length of SI{8}{meter};

This is a new length of deleted{mbox{SI{8}{meter}}}.

This is a new length of replaced{mbox{SI{8}{meter}}}{mbox{SI{3}{meter}}}.

end{document}

share|improve this answer

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

edited 9 hours ago

BambOo

3,1151527

edited 9 hours ago

BambOo

3,1151527

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

answered 9 hours ago

Ulrike FischerUlrike Fischer

206k9313705

5

You can provisionally redefine SI to use mbox around it.

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



ExplSyntaxOn

RenewDocumentCommand SI { o m o m } {

 mbox{

   bool_set_false:N l__siunitx_font_set_bool

   IfNoValueTF {#1}

     { __siunitx_combined:nnnn { } {#2} {#3} {#4} }

     {

       keys_set:nn { siunitx } {#1}

       __siunitx_combined:nnnn {#1} {#2} {#3} {#4}

     }

 }

}

ExplSyntaxOff





begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

I'd prefer a changes method that avoids striking out (color would be sufficient).

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



setdeletedmarkup{textcolor{red}{#1}}



begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

share|improve this answer

answered 8 hours ago

egregegreg

748k8919553298

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I am flying blind here, but would it not be better to patch changes instead ? The error popped up with siunitx but it may also happen with other commands right.
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  BTW, I just opened an issue on the git repo of the package
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BambOo The problem is that mbox can not be broken across lines... that's not a problem for SI{}{}, but can be for long deleted{...} phrases...
  
  – Rmano
  7 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Rmano I did not see that, you're right !
  
  – BambOo
  7 hours ago
  

  
  
  
  

add a comment | 

5

You can provisionally redefine SI to use mbox around it.

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



ExplSyntaxOn

RenewDocumentCommand SI { o m o m } {

 mbox{

   bool_set_false:N l__siunitx_font_set_bool

   IfNoValueTF {#1}

     { __siunitx_combined:nnnn { } {#2} {#3} {#4} }

     {

       keys_set:nn { siunitx } {#1}

       __siunitx_combined:nnnn {#1} {#2} {#3} {#4}

     }

 }

}

ExplSyntaxOff





begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

I'd prefer a changes method that avoids striking out (color would be sufficient).

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



setdeletedmarkup{textcolor{red}{#1}}



begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

share|improve this answer

answered 8 hours ago

egregegreg

748k8919553298

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I am flying blind here, but would it not be better to patch changes instead ? The error popped up with siunitx but it may also happen with other commands right.
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  BTW, I just opened an issue on the git repo of the package
  
  – BambOo
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BambOo The problem is that mbox can not be broken across lines... that's not a problem for SI{}{}, but can be for long deleted{...} phrases...
  
  – Rmano
  7 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Rmano I did not see that, you're right !
  
  – BambOo
  7 hours ago
  

  
  
  
  

add a comment | 

You can provisionally redefine SI to use mbox around it.

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



ExplSyntaxOn

RenewDocumentCommand SI { o m o m } {

 mbox{

   bool_set_false:N l__siunitx_font_set_bool

   IfNoValueTF {#1}

     { __siunitx_combined:nnnn { } {#2} {#3} {#4} }

     {

       keys_set:nn { siunitx } {#1}

       __siunitx_combined:nnnn {#1} {#2} {#3} {#4}

     }

 }

}

ExplSyntaxOff





begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

I'd prefer a changes method that avoids striking out (color would be sufficient).

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



setdeletedmarkup{textcolor{red}{#1}}



begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

share|improve this answer

answered 8 hours ago

egregegreg

748k8919553298

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



ExplSyntaxOn

RenewDocumentCommand SI { o m o m } {

 mbox{

   bool_set_false:N l__siunitx_font_set_bool

   IfNoValueTF {#1}

     { __siunitx_combined:nnnn { } {#2} {#3} {#4} }

     {

       keys_set:nn { siunitx } {#1}

       __siunitx_combined:nnnn {#1} {#2} {#3} {#4}

     }

 }

}

ExplSyntaxOff





begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

documentclass[]{article}

usepackage{changes}

usepackage{siunitx}



setdeletedmarkup{textcolor{red}{#1}}



begin{document}



This is a new length of SI{8}{meter};

This is a new length of deleted{SI{8}{meter}}.

This is a new length of replaced{SI{8}{meter}}{SI{3}{meter}}.



end{document}

share|improve this answer

answered 8 hours ago

egregegreg

748k8919553298

answered 8 hours ago

egregegreg

748k8919553298

answered 8 hours ago

egregegreg

748k8919553298