Conversation
|
|
||
| const pPr = node.elements?.find((el) => el.name === 'w:pPr'); | ||
| const styleTag = pPr?.elements?.find((el) => el.name === 'w:pStyle'); | ||
| const nestedRPr = pPr?.elements?.find((el) => el.name === 'w:rPr'); |
There was a problem hiding this comment.
@harbournick sometimes empty paragraphs could have run properties with font details defined. We don't parse it and that is why SuperToolbar shows default font for such paragraphs. Since there is no text we can't apply marks. I decided to implement it through additional attributes but will be happy to hear your thoughts
@artem-harbour if you have any ideas or suggestions I will be happy to hear as well
|
|
||
| const beforeSpacing = inLineSpacing?.['w:before'] || lineSpaceBefore || pDefaultSpacing?.['w:before']; | ||
| if (beforeSpacing) spacing.lineSpaceBefore = twipsToPixels(beforeSpacing); | ||
|
|
There was a problem hiding this comment.
@harbournick I tried to parse spaces and indents as accurate as possible but here is a document with w:beforeAutospacing and w:afterAutospacing defined. As far as I understood Word has its own way to handle it and I didn't found any specifics about it. I parse spaces based on font size in this case (according chatgpt suggestion).
VladaHarbour
force-pushed
the
har-9432_spacing
branch
from
d166d55 to
4673e8e
Compare
VladaHarbour
force-pushed
the
har-9432_spacing
branch
from
4673e8e to
96ef975
Compare
2 participants
No description provided.