Skip to content

Commit dcdd17d

Browse files
author
Aleksander Grinin
committed
Add articles to /java/developer-guide/complex-barcode/concepts/
1 parent 19aad9d commit dcdd17d

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

  • java/developer-guide/complex-barcode/concepts

java/developer-guide/complex-barcode/concepts/complex-generator/_index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "BarcodeGenerator vs ComplexBarcodeGenerator"
2+
title: "Using ComplexBarcodeGenerator"
33
description: "Learn when to use BarcodeGenerator and when to use ComplexBarcodeGenerator for Complex Barcode standards."
44
type: docs
55
weight: 25
@@ -17,7 +17,7 @@ Use `BarcodeGenerator` when the application already has the exact text that must
1717

1818
The complete source code for this article is available on GitHub:
1919

20-
<a href="https://github.com/aspose-barcode/Aspose.BarCode-for-Java/blob/master/src/test/java/com/aspose/barcode/guide/complex/concepts/ComplexBarcodeGenerator.java" target="_blank">View ComplexBarcodeGenerator.java</a>
20+
<a href="https://github.com/aspose-barcode/Aspose.BarCode-for-Java/blob/master/src/test/java/com/aspose/barcode/guide/complex/concepts/ComplexBarcodeGeneratorExample.java" target="_blank">View ComplexBarcodeGeneratorExample.java</a>
2121

2222
## Regular barcode generation
2323

@@ -59,7 +59,7 @@ In this workflow, the application fills a structured Java object. Aspose.BarCode
5959
| `BarcodeGenerator` | Ready-to-encode string | Plain barcodes and custom application data |
6060
| `ComplexBarcodeGenerator` | Typed complex codetext object | Supported Complex Barcode standards |
6161

62-
Both APIs can produce the same physical barcode if the final standardized payload is already known. However, only `ComplexBarcodeGenerator` lets the application work with a typed Complex Barcode object instead of manually building the standardized text.
62+
Both APIs can produce a barcode with the same encoded payload if the final standardized codetext is already known. However, only `ComplexBarcodeGenerator` lets the application work with a typed Complex Barcode object instead of manually building the standardized text.
6363

6464
## Encoding an already constructed payload
6565

@@ -91,7 +91,7 @@ Use `ComplexBarcodeGenerator` when:
9191
- the barcode represents a supported Complex Barcode standard;
9292
- the application should work with typed business fields;
9393
- the standardized payload should be constructed by Aspose.BarCode;
94-
- the same data must later be decoded back into a typed object.
94+
- the encoded data may later need to be decoded back into a typed object.
9595

9696
## Complete workflow
9797

java/developer-guide/complex-barcode/concepts/recognition-decoding/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ These two steps are intentionally separate. `BarCodeReader` recognizes barcode s
1717

1818
The complete source code for this article is available on GitHub:
1919

20-
<a href="https://github.com/aspose-barcode/Aspose.BarCode-for-Java/blob/master/src/test/java/com/aspose/barcode/guide/complex/concepts/RecognitionDecoding.java" target="_blank">View RecognitionDecoding.java</a>
20+
<a href="https://github.com/aspose-barcode/Aspose.BarCode-for-Java/blob/master/src/test/java/com/aspose/barcode/guide/complex/concepts/RecognitionVsDecoding.java" target="_blank">View RecognitionVsDecoding.java</a>
2121

2222
## Recognition reads the barcode symbol
2323

0 commit comments

Comments
 (0)