From 260aa2b9b4dab3e97e47ced8e10baba67564628b Mon Sep 17 00:00:00 2001 From: vladislav-todorov Date: Thu, 9 Oct 2025 12:06:40 +0300 Subject: [PATCH] chore: replaced cyrillic letters with latin ones --- getting-started/download-product-files.md | 2 +- knowledge-base/import-export-save-load-workbook.md | 2 +- .../radpdfprocessing/editing/radfixeddocumenteditor.md | 4 ++-- libraries/radpdfprocessing/editing/table/overview.md | 2 +- libraries/radpdfprocessing/editing/table/tablecell.md | 2 +- .../features/digital-signature/pdfstreamsigner.md | 2 +- libraries/radpdfprocessing/model/annotations/widgets.md | 2 +- libraries/radspreadprocessing/features/data-validation.md | 2 +- .../radspreadprocessing/features/headers-and-footers.md | 2 +- libraries/radspreadprocessing/features/named-ranges.md | 2 +- .../radspreadprocessing/features/styling/document-themes.md | 2 +- libraries/radspreadprocessing/getting-started.md | 2 +- .../working-with-cells/cell-value-types.md | 6 +++--- .../working-with-cells/insert-remove-cells.md | 4 ++-- libraries/radspreadstreamprocessing/getting-started.md | 4 ++-- libraries/radwordsprocessing/model/bookmark.md | 4 ++-- release-notes/2024/release-notes-2024-1-305 .md | 2 +- release-notes/2025/release-notes-2025-1-205.md | 2 +- 18 files changed, 24 insertions(+), 24 deletions(-) diff --git a/getting-started/download-product-files.md b/getting-started/download-product-files.md index cfde59e3..ffdd2e54 100644 --- a/getting-started/download-product-files.md +++ b/getting-started/download-product-files.md @@ -32,7 +32,7 @@ Since the **Telerik Document Processing** is a part of several [Telerik bundles] * Documentation files -Тo download these files, follow the steps below: +To download these files, follow the steps below: 1\. Log into [your Telerik account](https://www.telerik.com/account/) and click the **Downloads** option: diff --git a/knowledge-base/import-export-save-load-workbook.md b/knowledge-base/import-export-save-load-workbook.md index 9b73634c..f2abb50f 100644 --- a/knowledge-base/import-export-save-load-workbook.md +++ b/knowledge-base/import-export-save-load-workbook.md @@ -180,7 +180,7 @@ public Workbook LoadFromUploadedFile(UploadedFile uploadedFile) // Telerik RadAs The SQL table used for the example below has the `FileContent` column as `varbinary(MAX)`. ````C# -// the XLSX format provider is used for demo purposes and can be replaced with any format provider implementing the IBinaryWorkbookFormatProvider interfacе +// the XLSX format provider is used for demo purposes and can be replaced with any format provider implementing the IBinaryWorkbookFormatProvider interface IBinaryWorkbookFormatProvider formatProvider = new Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.XlsxFormatProvider(); // ReadFileFromDatabaseAsByteArray is demo method declared in the code snippet below diff --git a/libraries/radpdfprocessing/editing/radfixeddocumenteditor.md b/libraries/radpdfprocessing/editing/radfixeddocumenteditor.md index 9f9d9767..51b56473 100644 --- a/libraries/radpdfprocessing/editing/radfixeddocumenteditor.md +++ b/libraries/radpdfprocessing/editing/radfixeddocumenteditor.md @@ -157,13 +157,13 @@ The character properties that are responsible for the look of the runs are liste * __Subscript__: A baseline that is aligned at the subscript position of the containing box. * __Superscript__: A baseline that is aligned at the superscript position of the containing box. -* __UnderlinePattern__: Тhe underline pattern. Two patterns are supported. +* __UnderlinePattern__: The underline pattern. Two patterns are supported. * __None__: There is no underline. This is the default value. * __Single__: The underline is a single line. * __UnderlineColor__: The color of the underline. -* __StrikethroughPattern__: Тhe strikethrough pattern. Two patterns are supported. +* __StrikethroughPattern__: The strikethrough pattern. Two patterns are supported. * __None__: There is no strikethrough. This is the default value. * __Single__: The strikethrough is a single line. diff --git a/libraries/radpdfprocessing/editing/table/overview.md b/libraries/radpdfprocessing/editing/table/overview.md index b00fed0b..d32b52de 100644 --- a/libraries/radpdfprocessing/editing/table/overview.md +++ b/libraries/radpdfprocessing/editing/table/overview.md @@ -54,7 +54,7 @@ If you want to apply default styling to all the cells in a table, you can use Ta * __Background__: Specifies the background of the cell. -__Еxample 2__ shows how to use the __DefaultCellProperties__ of a table +__Example 2__ shows how to use the __DefaultCellProperties__ of a table #### __[C#] Example 2: Use DefaultCellProperties of Table__ diff --git a/libraries/radpdfprocessing/editing/table/tablecell.md b/libraries/radpdfprocessing/editing/table/tablecell.md index 9f3943b6..fbbd698b 100644 --- a/libraries/radpdfprocessing/editing/table/tablecell.md +++ b/libraries/radpdfprocessing/editing/table/tablecell.md @@ -21,7 +21,7 @@ __TableCell__ class represents a single cell in a [Table]({%slug radpdfprocessin ## Inserting a TableCell -In order to add a cell to а __Тable__, you should add it in the __TableCellCollection__ of a __TableRow__. +In order to add a cell to a __Table__, you should add it in the __TableCellCollection__ of a __TableRow__. The code snippet in __Example 1__ shows how to create a table with a single row and add a cell in the first row. diff --git a/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner.md b/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner.md index f90ea437..01565325 100644 --- a/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner.md +++ b/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner.md @@ -16,7 +16,7 @@ As of **Q2 2025** RadPdfProcessing introduces the **PdfStreamSigner**. The **Sig |Method|Description| |----|----| -|**PdfStreamSigner(Stream outputStream)**|Creates a new instance of thе PdfStreamSigner and specifies the output stream of the signed document.| +|**PdfStreamSigner(Stream outputStream)**|Creates a new instance of the PdfStreamSigner and specifies the output stream of the signed document.| |**SignDocument(Stream originalStream, SignatureField signatureField, int pageIndex, TimeSpan? timeout)**|Adds a [Digital Signature]({%slug radpdfprocessing-features-digital-signature%}) to the PDF document| The following example shows how to insert multiple [Digital Signatures]({%slug radpdfprocessing-features-digital-signature%}) into a PDF document using the PdfStreamSigner: diff --git a/libraries/radpdfprocessing/model/annotations/widgets.md b/libraries/radpdfprocessing/model/annotations/widgets.md index f7793ac4..013fcfcb 100644 --- a/libraries/radpdfprocessing/model/annotations/widgets.md +++ b/libraries/radpdfprocessing/model/annotations/widgets.md @@ -117,7 +117,7 @@ This class corresponds to WidgetContentType.PushButtonContent enum value and rep * **Content**: Provides the AnnotationContentSource, used to visualize the button in the PDF viewer. This property is with higher priority compared to AppearanceCharacteristics property. -* **AppearanceCharacteristics**: А [PushButtonAppearanceCharacteristics class]({%slug radpdfprocessing-model-interactive-forms-dynamic-appearance-properties%}#pushbuttonappearancecharacteristics-class) instance providing information on how to dynamically recalculate the widget appearance. This property is used only when the [AcroForm class]({%slug radpdfprocessing-model-interactive-forms-acroform %}) has ViewersShouldRecalculateWidgetAppearances property set to *true*, which forces the PDF viewer to ignore the provided AnnotationContentSource. In order to apply these properties, you should call **RecalculateContent()** method, which will modify the Content property value so that it corresponds to the appearance characteristics. +* **AppearanceCharacteristics**: A [PushButtonAppearanceCharacteristics class]({%slug radpdfprocessing-model-interactive-forms-dynamic-appearance-properties%}#pushbuttonappearancecharacteristics-class) instance providing information on how to dynamically recalculate the widget appearance. This property is used only when the [AcroForm class]({%slug radpdfprocessing-model-interactive-forms-acroform %}) has ViewersShouldRecalculateWidgetAppearances property set to *true*, which forces the PDF viewer to ignore the provided AnnotationContentSource. In order to apply these properties, you should call **RecalculateContent()** method, which will modify the Content property value so that it corresponds to the appearance characteristics. ### TwoStatesButtonWidget Class diff --git a/libraries/radspreadprocessing/features/data-validation.md b/libraries/radspreadprocessing/features/data-validation.md index 220bfca9..1adcd700 100644 --- a/libraries/radspreadprocessing/features/data-validation.md +++ b/libraries/radspreadprocessing/features/data-validation.md @@ -58,7 +58,7 @@ The __AnyValueDataValidationRuleContext__ class exposes the following properties __SingleArgumentdataValidationRuleContext__ exposes the properties which the __AnyValueDataValidationRuleContext__ class has, but extends them with the following properties: * __IgnoreBlank__: Specifies if the validation will ignore blank values and this way consider them as valid values. -* __Argument1__: Тhe argument needed for the validation. +* __Argument1__: The argument needed for the validation. * __CellIndex__: The cell index of the cell based on which the validation rule is created. * __Worksheet__: The worksheet in which the data validation rule is created. diff --git a/libraries/radspreadprocessing/features/headers-and-footers.md b/libraries/radspreadprocessing/features/headers-and-footers.md index a39f84aa..7224c54b 100644 --- a/libraries/radspreadprocessing/features/headers-and-footers.md +++ b/libraries/radspreadprocessing/features/headers-and-footers.md @@ -148,7 +148,7 @@ The following list describes all valid uses of the ampersand symbol sequences. I * **&A**: This text sequence allows you to insert a **Sheet name** field. This field is evaluated as the Sheet Name property value. -**Example 3** demonstrates how you could insert a date field in the header, a page number filed combined with а number of pages field in the footer of a worksheet . +**Example 3** demonstrates how you could insert a date field in the header, a page number filed combined with a number of pages field in the footer of a worksheet . #### **[C#] Example 3: Insert fields in header/footer** diff --git a/libraries/radspreadprocessing/features/named-ranges.md b/libraries/radspreadprocessing/features/named-ranges.md index a620b8df..2706778c 100644 --- a/libraries/radspreadprocessing/features/named-ranges.md +++ b/libraries/radspreadprocessing/features/named-ranges.md @@ -75,7 +75,7 @@ Note that qualifier for a workbook name is required only if the current workshee ## Types of Names -Тhe document model has support only for Defined Names. +The document model has support only for Defined Names. __Defined name__: A name that can contain any value that can be stored in a cell: a number or text constant, a formula, or a cell reference. You can create your own defined names. Note that you can edit the name, value and comment of the already created defined name, however, you cannot change its scope. diff --git a/libraries/radspreadprocessing/features/styling/document-themes.md b/libraries/radspreadprocessing/features/styling/document-themes.md index 52f77f3b..1f768660 100644 --- a/libraries/radspreadprocessing/features/styling/document-themes.md +++ b/libraries/radspreadprocessing/features/styling/document-themes.md @@ -145,7 +145,7 @@ In order to use the document theme's fonts, you need to use __ThemableFontFamily * Passing a __FontFamily__ object or a string representing a FontFamily name – the result would be a static FontFamily, meaning it will not be changed when the document theme is changed. -When you need to create а font that depends on the current document theme, you can use the __ThemableFontFamily__ objects. +When you need to create a font that depends on the current document theme, you can use the __ThemableFontFamily__ objects. __Example 4__ shows how to create a ThemableFontFamily. diff --git a/libraries/radspreadprocessing/getting-started.md b/libraries/radspreadprocessing/getting-started.md index 99d6c2a7..992e667a 100644 --- a/libraries/radspreadprocessing/getting-started.md +++ b/libraries/radspreadprocessing/getting-started.md @@ -100,7 +100,7 @@ In order to use the model of the __RadSpreadProcessing__ library in your project ->note Needed when exporting to PDF format a document containing images different than Jpeg and Jpeg2000 or ImageQuality different than High. The **Telerik.Documents.ImageUtils.dll** assembly depends on **SkiaSharp**. In order to use this assembly, you will need to add а reference to [SkiaSharp](https://www.nuget.org/packages/SkiaSharp/). With the [R2 2023 changes](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/changes-and-backward-compatibility/backward-compatibility#whats-different-in-2023-r2) SkiaSharp replaced ImageSharp as the required dependency. +>note Needed when exporting to PDF format a document containing images different than Jpeg and Jpeg2000 or ImageQuality different than High. The **Telerik.Documents.ImageUtils.dll** assembly depends on **SkiaSharp**. In order to use this assembly, you will need to add a reference to [SkiaSharp](https://www.nuget.org/packages/SkiaSharp/). With the [R2 2023 changes](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/changes-and-backward-compatibility/backward-compatibility#whats-different-in-2023-r2) SkiaSharp replaced ImageSharp as the required dependency. ## Creating a Workbook diff --git a/libraries/radspreadprocessing/working-with-cells/cell-value-types.md b/libraries/radspreadprocessing/working-with-cells/cell-value-types.md index c10a079a..7a79158a 100644 --- a/libraries/radspreadprocessing/working-with-cells/cell-value-types.md +++ b/libraries/radspreadprocessing/working-with-cells/cell-value-types.md @@ -15,11 +15,11 @@ This article briefly describes how to work with the __Value__ property of the ce Since cells are the atomic data units of a worksheet, their __Value__ property is used frequently. The property is of type __ICellValue__ – an interface that is implemented by all five concrete value types supported by the document model: EmptyCellValue, BooleanCellValue, NumberCellValue, FormulaCellValue and TextCellValue. The __ICellValue__ interface exposes several properties and methods: -* __RawValue__: Тhe property holds the string value entered by the user, opposed to the result value displayed in the cell. For example, when the user enters the string "=1+2" in a cell, the Value of the cell becomes a *FormulaCellValue* instance with result value of "3" and RawValue of "=1+2". +* __RawValue__: The property holds the string value entered by the user, opposed to the result value displayed in the cell. For example, when the user enters the string "=1+2" in a cell, the Value of the cell becomes a *FormulaCellValue* instance with result value of "3" and RawValue of "=1+2". -* __ValueType__ and __ResultValueType__: Тhe two properties are of type CellValueType and provide information about the type of the Value and its result. For example, the FormulaCellValue with RawValue of "=1+2" has a *Formula* ValueType and a *Number* ResultValueType. Similarly, the string "=CONCATENATE("abc", "def")" produces a FormulaCellValue with *Formula* ValueType and *Text* ResultValueType. +* __ValueType__ and __ResultValueType__: The two properties are of type CellValueType and provide information about the type of the Value and its result. For example, the FormulaCellValue with RawValue of "=1+2" has a *Formula* ValueType and a *Number* ResultValueType. Similarly, the string "=CONCATENATE("abc", "def")" produces a FormulaCellValue with *Formula* ValueType and *Text* ResultValueType. -* __GetValueAsString()__ and __GetResultValueAsString()__: Тhe two methods require a **CellValueFormat** argument that specifies how to present the Value and the ResultValue of the ICellValue object as strings. +* __GetValueAsString()__ and __GetResultValueAsString()__: The two methods require a **CellValueFormat** argument that specifies how to present the Value and the ResultValue of the ICellValue object as strings. To access the Value property of cells, first you need to create a CellSelection object that designates the cell or region of cells you would like to work with. Just like all other properties of the worksheet's cells, the Value property has three methods that respectively set, get and clear its value: SetValue(), GetValue() and ClearValue(). diff --git a/libraries/radspreadprocessing/working-with-cells/insert-remove-cells.md b/libraries/radspreadprocessing/working-with-cells/insert-remove-cells.md index 828b5c08..36e418e7 100644 --- a/libraries/radspreadprocessing/working-with-cells/insert-remove-cells.md +++ b/libraries/radspreadprocessing/working-with-cells/insert-remove-cells.md @@ -50,10 +50,10 @@ The __CellSelection__ class exposes an __Insert()__ method that takes one argume In order to remove cells, you need to create a __CellSelection__ object that indicates the region of cells you would like to remove. Also, you have to specify the direction of the shift. -Whenever you remove cells, all values that appear to the right or below the CellSelection region are shifted. There are two shift directions: left and up. When you choose to shift cells to the left, all cells that appear to the right of the selected region аре shifted to the left. Similarly, choosing to shift the values up moves all values in the selected region columns upwards. +Whenever you remove cells, all values that appear to the right or below the CellSelection region are shifted. There are two shift directions: left and up. When you choose to shift cells to the left, all cells that appear to the right of the selected region are shifted to the left. Similarly, choosing to shift the values up moves all values in the selected region columns upwards. -The __CellSelection__ class exposes a __Remove()__ method that takes one argument which indicates the direction of the shift. Тhe class also offers a __CanInsertOrRemove()__ method that determines if the removal is possible. __Example 2__ shows how to remove cells using methods mentioned above. +The __CellSelection__ class exposes a __Remove()__ method that takes one argument which indicates the direction of the shift. The class also offers a __CanInsertOrRemove()__ method that determines if the removal is possible. __Example 2__ shows how to remove cells using methods mentioned above. #### __[C#] Example 2: Remove cells__ diff --git a/libraries/radspreadstreamprocessing/getting-started.md b/libraries/radspreadstreamprocessing/getting-started.md index b01dc507..a6e0ef9a 100644 --- a/libraries/radspreadstreamprocessing/getting-started.md +++ b/libraries/radspreadstreamprocessing/getting-started.md @@ -60,7 +60,7 @@ In order to use **RadSpreadStreamProcessing** in your project, you will need to This section will explain how a document could be created. If you need more detailed information about the classes that export the different document elements, you can check the articles from the [Model section]({%slug radspreadstreamprocessing-model-workbook%}). -When creating a document with **RadSpreadStreаmProcessing**, the order in which the elements are created is very important. In order to minimize resource consumption, the library writes the content directly to a stream, and due to the structure of the file format, it is necessary to create the elements in the following order: +When creating a document with **RadSpreadStreamProcessing**, the order in which the elements are created is very important. In order to minimize resource consumption, the library writes the content directly to a stream, and due to the structure of the file format, it is necessary to create the elements in the following order: 1. Create a Workbook @@ -141,7 +141,7 @@ When creating a document with **RadSpreadStreаmProcessing**, the order in which ## Read Existing Document -When reading a document with **RadSpreadStreаmProcessing**, the order of parsing the content is very important. To minimize resource consumption, the library parses only the parts required by the user and, due to the file structure, it is necessary to read the desired elements in the following order: +When reading a document with **RadSpreadStreamProcessing**, the order of parsing the content is very important. To minimize resource consumption, the library parses only the parts required by the user and, due to the file structure, it is necessary to read the desired elements in the following order: 1. Read the Workbook diff --git a/libraries/radwordsprocessing/model/bookmark.md b/libraries/radwordsprocessing/model/bookmark.md index c241ee56..78f35020 100644 --- a/libraries/radwordsprocessing/model/bookmark.md +++ b/libraries/radwordsprocessing/model/bookmark.md @@ -23,7 +23,7 @@ A __Bookmark__ refers to a location in the document and has a unique name, which __Example 1__ shows how to create a __Bookmark__ and add its BookmarkRangeStart and BookmarkRangeEnd elements in a [Paragraph]({%slug radwordsprocessing-model-paragraph%}): -#### __[C#] Example 1: Add а bookmark to а paragraph__ +#### __[C#] Example 1: Add a bookmark to a paragraph__ {{region cs-radwordsprocessing-model-bookmark_0}} Bookmark bookmark = new Bookmark(document, "MyBookmark"); @@ -40,7 +40,7 @@ Note, that the paragraph should belong to the same document that is passed to th Inserting a __Bookmark__ in the document can also be done with the [RadFlowDocumentEditor]({%slug radwordsprocessing-editing-radflowdocumenteditor%}) class like shown in __Example 2__: -#### __[C#] Example 2: Insert а bookmark using RadFlowDocumentEditor__ +#### __[C#] Example 2: Insert a bookmark using RadFlowDocumentEditor__ {{region cs-radwordsprocessing-model-bookmark_1}} RadFlowDocumentEditor editor = new RadFlowDocumentEditor(new RadFlowDocument()); diff --git a/release-notes/2024/release-notes-2024-1-305 .md b/release-notes/2024/release-notes-2024-1-305 .md index e7847aff..4d2eeca2 100644 --- a/release-notes/2024/release-notes-2024-1-305 .md +++ b/release-notes/2024/release-notes-2024-1-305 .md @@ -25,7 +25,7 @@ position: 99 * A strange symbol is added as a name when embedding a file with an empty string as its name argument. * A NullReferenceException is thrown when importing a document with embedded files. * A NullReferenceException is thrown when importing a document with a signature and parsing the linejoin operator. -* А NullReferenceException is thrown when importing and then exporting a document containing Type1Font with a missing FontInfo table. +* A NullReferenceException is thrown when importing and then exporting a document containing Type1Font with a missing FontInfo table. * Merging two documents having embedded files with same names repeats adding number 2. * Unicode characters from Supplementary Multilingual Plane are skipped during the PDF export. diff --git a/release-notes/2025/release-notes-2025-1-205.md b/release-notes/2025/release-notes-2025-1-205.md index 9a44bd41..b86618b2 100644 --- a/release-notes/2025/release-notes-2025-1-205.md +++ b/release-notes/2025/release-notes-2025-1-205.md @@ -64,7 +64,7 @@ position: 99 * A NotSupportedException is thrown when parsing CFF Type1 font. * A NotSupportedException is thrown when exporting an image with ICCBased color space and the default ImageCompression is changed. * Some text is missing when the culture is German. -* А KeyNotFoundException is thrown when reading glyph data with Type1Font. +* A KeyNotFoundException is thrown when reading glyph data with Type1Font. * A KeyNotFoundException is thrown when loading a document with unsupported annotation. * An InvalidOperationException: 'Position is out of range.' is thrown while reading the font in the import process. * An InvalidCastException is thrown when parsing the font for a specific document.