Talk:Code 39

I think I have noticed a thin white space (Format 2: 'w') between each character in this barcode fromat. Is this worth mentioning in the article?--Commander Keane 11:02, 11 Feb 2005 (UTC)

That space is definately there. That's why Code 39 is a 'discrete' code, rather than a 'continuous' code (eg, Code 128). It's probably worth mentioning, but then there's a bunch of other things worth mentioning too. Are we trying to put the full specification of Code 39 here? :) Personally, I think that would be cool :) -- Ch'marr 19:14, 15 March 2006 (UTC)

I added a link to a specification page in another Wiki. Up to now, however, this seems to include less information than this Wikipedia article. wr 87.139.81.19 13:25, 31 October 2007 (UTC)

The space doesn't have to be a thin one, see this example: [1] --Tilman (talk) 14:27, 13 June 2008 (UTC)

A better way of representing the code.

Personally, I dislike the 'NwN' and 'bWb' nomenclature for representing the code. There's too much of a 'disconnect' between this nomenclature and how it's represented in real life (as black and white regions). Does anyone else do it this way? Ideally we should be using graphics, but I can certainly understand that that isn't feasible here. Instead, I propose using '#' and '_' characters to represent a dark and light region. For example, use this for the letter L:

#_###_#_#___###

. This would also be useable for the other barcoding standards. -- Ch'marr 19:19, 15 March 2006 (UTC)

Looks cute, but it's hard to count consecutive underscore characters. 141.189.251.1 (talk) 13:30, 19 November 2009 (UTC)

Maybe some other characters would be better e.g.

11OO10011

or

#'###'#'#'''###

141.189.251.1 (talk) 13:37, 19 November 2009 (UTC)

#'###'#'#'''###

or

#.###.#.#...###

look good to me, should work well when copy-pasting to text editors as well. Single and double quotes are always tricky as they are interpreted differently and formatted to UTF-8 characters.

Gabelstaplerfahrer (talk) 20:17, 5 April 2010 (UTC)

External Links

This section needs to be pruned. There are far too many links providing too little information. Most of them are not much more than thinly veiled links to commercial software. --Millbrooky 16:09, 24 October 2006 (UTC)

Please refer to the Talk:European Article Number page for further discussion. --Millbrooky 16:53, 24 October 2006 (UTC)

Code 39 Extension

Does anyone know of the US Code 39 Extension coding? If so, please post its specifications. Thanks. 75.31.138.94 19:12, 7 January 2007 (UTC)

Order of Table

The table which shows the encoding of each character, places the punctuation at the top, followed by the digits and finally the letters. Given that the checksum encoding places the characters in a different order, and uses that order in its calculations, could we rearrange the table to have the same ordering. The description of the checksum simply refers to the ordinal value of the character, and you have to look at the sample code to see that what that order is. —Preceding unsigned comment added by David ORourke (talk • contribs) 13:11, 15 September 2008 (UTC)

Done 141.189.251.1 (talk) 13:29, 19 November 2009 (UTC)

upside down and backwards

type 39 barcodes can be read backwards -- in this case, the characters will be re-mapped. In perl:

$backwards='PAEJJAAFFP';

$forward='*00116641*';

$backwards=reverse $backwards;

$backwards=~tr/\ \$\%\*\+\-\.\/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ/S\%\$P\/ML\+FAHGEDJCBI1875403296U\.\-YX\*WV\ ZKRQONT/;

if ($forward eq $backwards){print "matched\n";}

Useful in the case of a fax cover sheet that can be fed in either way.

67.206.60.188 (talk) 18:54, 15 April 2009 (UTC)

This is just too implementation specific to be useful here. 141.189.251.1 (talk) 13:32, 19 November 2009 (UTC)

Missing references, [3] link is dead

I tried the [3] link (http://www.dscp.dla.mil/subs/support/specs/crds/milstan.asp) but its dead: "Ups! Page not found" And I cannot find any references to the table "Code 39 Characters". Where did you guys get this table with all of the characters? — Preceding unsigned comment added by 88.69.220.226 (talk) 22:10, 21 August 2012 (UTC)