How about the barcode?
"Actually this says, that the [FNC1] should be translated to 0x1D(GS), but not if it's the first or second «character»." -- Correct -- =================== The quoted paragraphs are just references. I cannot post the standards because they are copyright protected by ISO. ================================== "What to do with the leading [FNC1]?" If the symbology identifier is also included in the scan string it must be set properly and the FNC1 must be deleted from the string. If the software is "knowing" the data structure behind then it expects and parses the GS1 Applications identifier data structure gives the data back in an already presorted way. ATTENTION - This is leaving the pure decoder and goes into data interpretation. The question is if a decoder library may provide such a data related functionality or not. If it is in the decoder then this is a function which is used in the same way for all symbologies containing GS1 structured data. (except GS1 Databar - no leading FNC1 is allowed, this symbology is designed for GS1 structured data only) With no symbology identifier and no data structure parsing the first FNC1 is also deleted from the string. Its then however useless because the application which receives the data does not get anymore the information which data structure type has been used. I suggest therefore to translate, by default setting, the found symbology together with the 1st/2nd to the appropriate symbology identifier and send this together with the decoded data. ================================================================== *apologies. Tab-Sent prematurely* Just noticed, that you sent this reply to me ONLY. (I took the wrong anwer button, sorry) Unless there is some hush-hush about this you should send the reply to the List instead, so that other users and the developers can see it. Actually this says, that the [FNC1] should be translated to 0x1D(GS), but not if it's the first or second «character». What to do with the leading [FNC1]? I can not get the meaning of the quoted paragraphs. The wording is too complex for me. 2013/2/12 Wilfried Weigelt <wwreav...@gmail.com>:
ISO/IEC 15417 Annex B describes the handling of FNC 1 characters. This is normative. "FNC1 in the third or subsequent character position is transmitted as the ASCII character 29 (GS)." Code 128 Annex C, Symbology Identifier ]C0 GS1-128 is Code 128 Annex C, Symbology Identifier ]C1 (FNC1 at the first position) Concatendation of data : Annex C, Symbology Identifier ]C4 - controlled by ISBT-128 ISO/IEC 16022 DataMatrix FNC1 handling Chapter 5.2.4.6 ; 5.6.4 ; 11.1 ; 11.2 ; 11.5 ; Annex N Symbology Identifier, (similar to Code 128, but more options) ISO/IEC 18004 QR-Code FNC1 Handling Chapter 6.3.8 FNC1 mode Table 2 Chapter 6.4.4 "In FNC1 mode symbols the FNC1character may occur in the data. It is represented in Alphanumeric mode by the character %. Refer to 6.4.8.1, 6.4.8.2 and 13.4 for details of the encoding and transmission of FNC1 and %. " Chapter 6.4.8 FNC1 modes (depending : Byte modes - translate to ASCII 29, alphanumeric mode - translate to % becasue only 43 characters available in alphanumeric mode) Chapter 13.4 Annex F - Symbology Identifier Am 12.02.2013 02:13, schrieb Lachezar Dobrev:
I'm not sure about DM or QR usa of [FNC1], but in GS1-128 (which is a CODE-128 with specification for content) uses [FNC1] to combine multiple «instructions» into a single bar-code. I would like to raise a hand and propose the reader to strip [FNC1] from the text. This is what most (if not all) hand-held bar-code readers do by default. If anyone is interested in handling the [FNC1] then they should process the raw bytes anyway. The Wikipedia article on GS1-128 has a bit of information on the subject, I believe can shed some light.