Australian Post decoding

Aspose.BarCode Product Family
1

I am having trouble with the Australian-Post barcode recognition.
I have attached a .jpg of the barcode in question.

When using the Aspose DEMO scanner, the following value is
returned "6292561807066619MP1X02673"

My handheld scanner returns
62,92561807,2223123123123003221101203002123,00 26 07 03

Bar Sequence:
ATDHHDTHHDADDHHADDHHDADDDTADTADTADTHHTDDAAHADHTHHDADTHHHADDHATHHTAT

I expected the 31 char field “2223123123123003221101203002123”
to be returned.

I think this is type 62 (Customer-3) which has 8-chars of DPID,
and 31-chars of customer info.

How am I to interpret this Returned value?

THANK YOU!
– Byron Tiller –
workingjoe

2

Hi Byron,


Thanks for posting the sample image. We will look into it and will get back to you soon. Sorry for the inconvenience.
3

Hello…
Any further words on this issue? Thank You.

4

Hi Byron,

Please try the attached dll.

* Why this happened:

62,92561807,2223123123123003221101203002123,00 26 07 03

62 means this is a barcode contains customer information( 2223123123123003221101203002123 ).

It can be interpreted using CTable or NTable or user defined proprietory techniques (“Customer

Barcoding Technical Specifications”, Page 6,Australia Post 1998).

In Aspose.BarCode, it interprets the customer information using
CTalbe, that’s why the characters “066619MP1X” was showed.

* What’s new:
1. New enum CustomerInformationInterpretingType was added as below:
public enum CustomerInformationInterpretingType
{
///


/// Use CTable to interpret the customer information
///
CTable,
///
/// Use NTable to interpret the customer information
///
NTable,
///
/// Do not interpret the customer information, return the raw values.
///
Other
}
2.New property CustomerInformationInterpretingType was introduced into BarCodeReader, it’s set Other as default.

Thanks

5

That’s excellent! However, I can’t get this DLL to work in my environment.

Can you rebuild it for me? I need a .NET Aspose.barcode.dll to match my existing .NET components.

THANK YOU!!

6

Could you tell me why it doesn't work? Is there any exceptions?

Thanks

7

Hello,

I am using Aspose.BarCode.dll for .NET version 3.0.1.1211



Since the programming interface and name-space do not match the provided DLL I can’t use it in my environment.



If I try and match name-spaces and adapt your DLL into our tools, there
are lots of undefined classes errors and items that are not present.



Is there an UPGRADE or HOTFIX available for me that includes this change in the Aspose.barCode.dll for .NET ??



THANK YOU

– Byron Tiller –

(workingjoe)

8

Hi,

The interface had been changed since v3.1.0, however I will provide a "compatibility kit" to you tomorrow for this issue.

Thank you

9

The attached file is the Aspose.BarCode.CompatibilityKit.dll, this kit dll will be able to help you to use the new reader with the old API. The only change to the existed code may be setting the license, you will need to set the license once before using the reader as below:

BarCodeReader.SetLicense(@"C:\ Aspose.BarCode.lic");

10

The issues you have found earlier (filed as 19056) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
11

For the AustrailianPost barcode with Customer data:

I’ve gotten the Aspose.BarCode for .NET 3.7.0 partially working in my application. My problem now is that I can’t find features which WERE returned by the older DLL interface.

For instance, there used to be an “Orientations::East” (or West, North, South) that was returned, but I can’t find the equivalent information in the newer DLL interface. Is this information available somehow?

Also, there are 4 “Drawing::Points” returned by the GetRegion() call - each with an X,Y pair. Is there documentation as to which points are [0] index and what points are [1] index?

IF the barcode was “Orientation::West” will the value of the Drawing::Points be different than if the barcode was “Orientation::East” ?

THANKS!!



12

Hi,


We are working on the orientation of barcodes and will inform you when it becomes available.

The points returned are in the following sequence:
  1. top left
  2. top right
  3. bottom right
  4. bottom left
workingjoe:

IF the barcode was “Orientation::West” will the value of the Drawing::Points be different than if the barcode was “Orientation::East” ?
The points returned would be same, provided that the barcode is placed exactly at the same coordinates in both cases.
13

Thank you.

So, just to be clear… in the old version of the DLL the “top-left” coordinate was related to the “orientation” – but currently the interface will always assume ZERO rotation (Orientation::East) right?

Thanks again.
14

Is there any projected time frame when the orientation of barcodes will be available? I have two customers now, who are awaiting upgrades that I am unable to provide because we require the orientation information to be available – as the older interface provided.

THANK YOU.

Byron Tiller
Pitney Bowes/DMT Software

15

Hi Byron,


I will get back to you with an ETA shortly.
16

I look forward to hearing from you. Thank you Saqib.


>> Byron Tiller <<
17

Hello Byron,
<!–[if gte mso 9]>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:DrawingGridVerticalSpacing>7.8 磅</w:DrawingGridVerticalSpacing>
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>
<w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>ZH-CN</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:SpaceForUL/>
<w:BalanceSingleByteDoubleByteWidth/>
<w:DoNotLeaveBackslashAlone/>
<w:ULTrailSpace/>
<w:DoNotExpandShiftReturn/>
<w:AdjustLineHeightInTable/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
<w:UseFELayout/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=“Cambria Math”/>
<m:brkBin m:val=“before”/>
<m:brkBinSub m:val="–"/>
<m:smallFrac m:val=“off”/>
<m:dispDef/>
<m:lMargin m:val=“0”/>
<m:rMargin m:val=“0”/>
<m:defJc m:val=“centerGroup”/>
<m:wrapIndent m:val=“1440”/>
<m:intLim m:val=“subSup”/>
<m:naryLim m:val=“undOvr”/>
</m:mathPr></w:WordDocument>
<![endif]–><!–[if gte mso 10]>

/* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.5pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-font-kerning:1.0pt;}

<![endif]–>

This feature will be available in the middle of next month.

Thanks


18

The issues you have found earlier (filed as 15727) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.