Conversation
harvestcore
reviewed
Apr 29, 2026
luiisgallego
approved these changes
Apr 30, 2026
thebassplayer1234
approved these changes
Apr 30, 2026
harvestcore
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to the official OOXML specification, the valid value is
exact(see https://c-rex.net/samples/ooxml/e1/Part4/OOXML_P4_DOCX_ST_LineSpacingRule_topic_ID0ERZ42.html ), but the OOXML documentation contains some ambiguity, as in certain sections the term exactly is mentioned (see https://c-rex.net/samples/ooxml/e1/Part4/OOXML_P4_DOCX_spacing_topic_ID0EA1OM.html). As a result, this led to setexactlyas a possible value which it has no effect because it is not recognized as a valid value by the specification. That's whyexactlyis replaced withexact