Fast and easy to use cross-platform .NET library that creates or modifies Microsoft Word (DocX) and later also Excel (XLSX) files without installing any software. Library is based on Open XML SDK
MIT License
279
stars
49
forks
source link
[Possibly breaking change] Set HighAnsi, EastAsia and ComplexScript at the same time as FontFamily #125
In the begining of OfficeIMO we only supported FontFamily as part of Document.Settings.FontFamily and Paragraph.FontFamily. The thing is there are 3 other settings in FontFamily. Those are HighAnsi, ComplexScript and EastAsia. I've added FontFamilyHighAnsi to global settings as a separate option, but forgot to add it for Paragraph. While I could just add HighAnsi to Paragraph I believe this is not enough to address issue.
Most languages such as Polish have special chars. If we set FontFamily to Arial and we use mix of standard chars and special chars łążćźż it would only change FontFamily for standard chars and leave special chars on it's defaults. This makes no sense to treat special chars differently from my perspective. Therefore in this change:
If you change FontFamily on Document.Settings or Paragraph it will set it on Ascii, HighAnsi, EastAsia and ComplexScript.
If you want to then change it to a different font for those special chars or settings you can do it directly thru exposed properties.
This PR addresses:
In the begining of OfficeIMO we only supported FontFamily as part of
Document.Settings.FontFamilyandParagraph.FontFamily. The thing is there are 3 other settings in FontFamily. Those are HighAnsi, ComplexScript and EastAsia. I've addedFontFamilyHighAnsito global settings as a separate option, but forgot to add it for Paragraph. While I could just add HighAnsi to Paragraph I believe this is not enough to address issue.Most languages such as Polish have special chars. If we set FontFamily to Arial and we use mix of standard chars and special chars łążćźż it would only change FontFamily for standard chars and leave special chars on it's defaults. This makes no sense to treat special chars differently from my perspective. Therefore in this change:
This PR adds:
Paragraph.FontFamilyHighAnsiParagraph.FontFamilyEastAsiaParagraph.FontFamilyComplexScriptDocument.Settings.FontFamilyEastAsiaDocument.Settings.FontFamilyComplexScript