@UlrikeFischer isn't there anything that can be done from the miktex side to remind users about the dual update? We see this problem so often. Most users does not even know there is a difference.
@DavidCarlisle good point, there was updmap-sys as well. Would there be any issues in miktex if an admin update would automatically trigger a user update as well.
@daleif well on a "one user PC" it would be okay, but I don't think that it should be done if lots of users are involved - they probably wouldn't like it if the admin shrubs their personal style files.
@JosephWright @DavidCarlisle on a german list there was just a bit discussion about input normalization in luatex and I wonder if it would make sense to add something like this tex.stackexchange.com/a/229589/2388 to expl3 or some other place.
i don't expect anyone to go through and compile the whole thing. i figured someone would know how to remove the padding. the inputs are perfectly cropped by the way.
seems like my issue was the newline after \fontfamily{cmss} i just changed it to \fontfamily{cmss}% not expecting anything to change, but it worked for some reason. weird
@tjt263 it's not weird. It's a consequence of you not posting anything useful and expecting a useful answer. And then saying that you won't do even a slightest favour to someone willing to help you.
@Sigur \let\oldparindent\parindent makes \oldparindent into an alias for the name of the container, not for its value. Thus \hspace{\oldparindent} is exactly the same as \hspace{\parindent}, which extracts the current value of the parameter.
@Sigur \makeatletter\@ifdefinable{\normalparindent}{\newlength\normalparindent}\makeatother and then \AtBeginDocument{\setlength\normalparindent{\parindent}}. This assumes that, if \normalparindent is defined, it is a length register.