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

Realistic, logical way for men with medieval-era weaponry to compete with much larger and physically stronger foes

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

I am caught when I was about to steal some candies

Why didn't the people of King's Landing riot when the Great Sept of Baelor was destroyed?

Is Jesus the last Prophet?

Why didn't all the iron and heavier elements find their way to the center of the accretion disc in the early solar system?

How do I type a hyphen in iOS 12?

Why does there seem to be an extreme lack of public trashcans in Taiwan?

Do they make "karaoke" versions of concertos for solo practice?

When editor does not respond to the request for withdrawal

About the paper by Buekenhout, Delandtsheer, Doyen, Kleidman, Liebeck and Saxl

Am I being scammed by a sugar daddy?

If the pressure inside and outside a balloon balance, then why does air leave when it pops?

Is it true that "only photographers care about noise"?

How can powerful telekinesis avoid violating Newton's 3rd Law?

Changing the PK column of a data extension without completely recreating it

What is the language spoken in Babylon?

A life of PhD: is it feasible?

Is all-caps blackletter no longer taboo?

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

Why is isotope an issue in reading mass spectra?

Is there a frequency comparator device?

Why is the concept of the Null hypothesis associated with the student's t distribution?

Simple log rotation script



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
usepackagechanges
usepackagesiunitx
begindocument
This is a new length of SI8meter;
This is a new length of deletedSI8meter.
This is a new length of replacedSI8meterSI3meter.
enddocument


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










share|improve this question




























    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
    usepackagechanges
    usepackagesiunitx
    begindocument
    This is a new length of SI8meter;
    This is a new length of deletedSI8meter.
    This is a new length of replacedSI8meterSI3meter.
    enddocument


    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










    share|improve this question


























      3












      3








      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
      usepackagechanges
      usepackagesiunitx
      begindocument
      This is a new length of SI8meter;
      This is a new length of deletedSI8meter.
      This is a new length of replacedSI8meterSI3meter.
      enddocument


      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










      share|improve this question
















      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
      usepackagechanges
      usepackagesiunitx
      begindocument
      This is a new length of SI8meter;
      This is a new length of deletedSI8meter.
      This is a new length of replacedSI8meterSI3meter.
      enddocument


      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















      share|improve this question













      share|improve this question




      share|improve this question








      edited 5 hours ago







      BambOo

















      asked 8 hours ago









      BambOoBambOo

      3,1151527




      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
          usepackagechanges
          usepackagesiunitx
          begindocument
          This is a new length of SI8meter;
          This is a new length of deletedmboxSI8meter.
          This is a new length of replacedmboxSI8metermboxSI3meter.
          enddocument





          share|improve this answer

























          • Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?

            – BambOo
            7 hours ago


















          5














          You can provisionally redefine SI to use mbox around it.



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          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


          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          setdeletedmarkuptextcolorred#1

          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


          enter image description here






          share|improve this answer























          • 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
            6 hours ago











          • BTW, I just opened an issue on the git repo of the package

            – BambOo
            6 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
            5 hours ago












          • @Rmano I did not see that, you're right !

            – BambOo
            5 hours ago











          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


















          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















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          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
          usepackagechanges
          usepackagesiunitx
          begindocument
          This is a new length of SI8meter;
          This is a new length of deletedmboxSI8meter.
          This is a new length of replacedmboxSI8metermboxSI3meter.
          enddocument





          share|improve this answer

























          • Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?

            – BambOo
            7 hours ago















          9














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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx
          begindocument
          This is a new length of SI8meter;
          This is a new length of deletedmboxSI8meter.
          This is a new length of replacedmboxSI8metermboxSI3meter.
          enddocument





          share|improve this answer

























          • Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?

            – BambOo
            7 hours ago













          9












          9








          9







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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx
          begindocument
          This is a new length of SI8meter;
          This is a new length of deletedmboxSI8meter.
          This is a new length of replacedmboxSI8metermboxSI3meter.
          enddocument





          share|improve this answer















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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx
          begindocument
          This is a new length of SI8meter;
          This is a new length of deletedmboxSI8meter.
          This is a new length of replacedmboxSI8metermboxSI3meter.
          enddocument






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 7 hours ago









          BambOo

          3,1151527




          3,1151527










          answered 8 hours ago









          Ulrike FischerUlrike Fischer

          205k9313705




          205k9313705












          • Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?

            – BambOo
            7 hours ago

















          • Thanks for your answer. Is there a way to apply such mbox to all deleted calls, with a renewcommand maybe ?

            – BambOo
            7 hours ago
















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

          – BambOo
          7 hours ago





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

          – BambOo
          7 hours ago











          5














          You can provisionally redefine SI to use mbox around it.



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          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


          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          setdeletedmarkuptextcolorred#1

          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


          enter image description here






          share|improve this answer























          • 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
            6 hours ago











          • BTW, I just opened an issue on the git repo of the package

            – BambOo
            6 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
            5 hours ago












          • @Rmano I did not see that, you're right !

            – BambOo
            5 hours ago















          5














          You can provisionally redefine SI to use mbox around it.



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          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


          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          setdeletedmarkuptextcolorred#1

          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


          enter image description here






          share|improve this answer























          • 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
            6 hours ago











          • BTW, I just opened an issue on the git repo of the package

            – BambOo
            6 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
            5 hours ago












          • @Rmano I did not see that, you're right !

            – BambOo
            5 hours ago













          5












          5








          5







          You can provisionally redefine SI to use mbox around it.



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          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


          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          setdeletedmarkuptextcolorred#1

          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


          enter image description here






          share|improve this answer













          You can provisionally redefine SI to use mbox around it.



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          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


          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


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



          documentclass[]article
          usepackagechanges
          usepackagesiunitx

          setdeletedmarkuptextcolorred#1

          begindocument

          This is a new length of SI8meter;
          This is a new length of deletedSI8meter.
          This is a new length of replacedSI8meterSI3meter.

          enddocument


          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 6 hours ago









          egregegreg

          748k8919553298




          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
            6 hours ago











          • BTW, I just opened an issue on the git repo of the package

            – BambOo
            6 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
            5 hours ago












          • @Rmano I did not see that, you're right !

            – BambOo
            5 hours ago

















          • 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
            6 hours ago











          • BTW, I just opened an issue on the git repo of the package

            – BambOo
            6 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
            5 hours ago












          • @Rmano I did not see that, you're right !

            – BambOo
            5 hours ago
















          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
          6 hours ago





          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
          6 hours ago













          BTW, I just opened an issue on the git repo of the package

          – BambOo
          6 hours ago





          BTW, I just opened an issue on the git repo of the package

          – BambOo
          6 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
          5 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
          5 hours ago














          @Rmano I did not see that, you're right !

          – BambOo
          5 hours ago





          @Rmano I did not see that, you're right !

          – BambOo
          5 hours ago

















          draft saved

          draft discarded
















































          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.




          draft saved


          draft discarded














          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















          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







          Popular posts from this blog

          Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

          Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

          François Viète Contents Biography Work and thought Bibliography See also Notes Further reading External links Navigation menup. 21Google Bookspp. 75–77Google BooksDe thou (from University of Saint Andrews)ArchivedGoogle BooksGoogle BooksGoogle BooksGoogle booksGoogle Bookscc-parthenay.frL'histoire universelle (fr)Universal History (en)ArchivedAdsabs.harvard.eduPagesperso-orange.frArchive.orgChikara Sasaki. Descartes' mathematical thought p.259Google BooksGoogle BooksGoogle Bookspp. 152 and onwardGoogle BooksGoogle BooksScribd.comGoogle Books1257-7979Google BooksGoogle BooksGoogle BooksGoogle BooksGoogle BooksGoogle BooksGallica.bnf.frGoogle BooksGoogle Books"François Viète"Francois Viète: Father of Modern Algebraic NotationThe Lawyer and the GamblerAbout TarporleySite de Jean-Paul GuichardL'algèbre nouvelle"About the Harmonicon"cb120511976(data)1188044800000 0001 0913 5903n82164680ola2013766880073431702w6vt1sb70287374827140948071409480