View Issue Details

IDProjectCategoryView StatusLast Update
0004200ScribusPlug-inspublic2014-01-10 00:17
Reporteraxelb Assigned Tojghali  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.4.3 
Summary0004200: Improvment to the barcode generator
DescriptionSuggested improvments to the barcode generator
===============================================
This tool is really great, but still I will ask for some small
improvements :-)

1. Change EAN -> GTIN
     http://en.wikipedia.org/wiki/GTIN
The former EAN is now named GTIN, should be changed in the GUI, perhaps
like this:
GTIN 13 (EAN 13)
to help the users catch up with the change?

2. Add the convertation of ISSN-numbers
     http://en.wikipedia.org/wiki/ISSN
As of now, I can do this by manually adding 977 in front of my issn,
then two digits for the number of my publication and use GTIN-13. But
then I cant become the ISSN-number as text over the barcode :-(

3. Make GTIN 13 + Add-on in one operation
Still concerning barcodes:
Would it be possible to also use the so called «add-on» (=EAN 2, I
think)? That is an extra barcode after the standard barcode (for
instance after GTIN 13) to show the number of the publication.
Some distributors (for instance ours, Narvesen in Norway :-) asks for this.
As is now, I see I can first make my GTIN 13 and then an add-on and then
put them beside each other, but I consider this a workaround (or am I
missing something? If this is possible in one step already, please tell
me how :-)

++**++**++**++**++**++**++**++**++**++**++**++**++**++**++**

3. Saving the scrapbook-content as a file
===========================================
Perhaps a real bug, not only an asking for improvments:
I am not able to save the content of my scrap book.
I can look through directories when I press «save», but «OK» gives no
effect (is grayed out) and the windows does not close itself.
TagsNo tags attached.
Patch

Relationships

has duplicate 0007039 closedsubik Add ISSN temlpate to BarCode Generator 

Activities

axelb

2006-08-31 20:48

reporter   ~0012388

Last edited: 2006-08-31 20:49

oops, the part about the scrapbook should have been a second bug. Is it ok to leave it here, or should I file a new one for that?

terryburton

2006-09-13 23:15

reporter   ~0012514

Hi,

I'm Terry who wrote the BWIPP backend.

I am intending to improve the backend to address these issues in the following ways:

1. Change EAN -> GTIN

Good idea. More generally, I shall add comments at the beginning of each encoder from which frontends such as Scribus can extract the friendly description of the encoder as well as an example of valid input data. Something like this:

%--DESC: GTIN 13 (EAN 13)
%--EXAM: 9771473968012

If Scribus devs (or other frontend devs) have any thoughts on this then please let me know (cc: postscriptbarcode@googlegroups.com).


2. Add the convertation of ISSN-numbers

I may add a new encoder similar to ISBN, or maybe add an ISSN option to the existing ISBN encoder, or maybe amend the EAN encoder... requires some careful thought, but ISSN will be cleanly supported.


3. Make GTIN 13 + Add-on in one operation

Again, more generally I will probably create a single meta-encoder to handle each of the valid EAN/UPCs with addons. This again requires a bit of careful thought.


I'll get to work on this as soon as I can find time but that will probably not be for a couple of weeks or so and the changes are not likely happen all at once.

I will announce significant releases of the backend to this ticket as and when they occur.

terryburton

2006-09-14 21:13

reporter   ~0012520

1. Change EAN -> GTIN

Progress made for the general case that I previously described...

Latest release 2006-06-14 of BWIPP contains functional comments from which Scribus can extract the friendly name of the symbology and the example input to pre-populate the data field.

However, I have decided that I will not at this point in time refer to the symbology as GTIN-13 since this is a label for an international standard describing the structure of data contained in a symbol, rather than a description of the symbology itself. I fully expect that the proper terminology will be "officially" misused within the near future, at which point I will start refering to the symbology as GTIN-13.

Please let me know if there are any difficulties with updating Scribus to extract this data.

I will address the remaining issues as I find time.


Have fun,

Tez

JussiP

2006-11-28 21:22

reporter   ~0013606

ISBN codes will change from 10 to 13 digits at the start of next year. Support for these would be nice.

AFAICR ISBN-13 codes will directly work as EAN codes.

terryburton

2014-01-09 23:32

reporter   ~0031007

This can be closed. All point resolved some time ago.

Issue History

Date Modified Username Field Change
2006-08-31 20:47 axelb New Issue
2006-08-31 20:48 axelb Note Added: 0012388
2006-08-31 20:49 axelb Note Edited: 0012388
2006-08-31 21:12 plinnell Status new => assigned
2006-08-31 21:12 plinnell Assigned To => subik
2006-09-13 23:15 terryburton Note Added: 0012514
2006-09-14 21:13 terryburton Note Added: 0012520
2006-11-28 21:22 JussiP Note Added: 0013606
2008-05-20 13:44 jghali Relationship added has duplicate 0007039
2014-01-09 23:32 terryburton Note Added: 0031007
2014-01-10 00:17 christoph_s Status assigned => resolved
2014-01-10 00:17 christoph_s Resolution open => fixed
2014-01-10 00:17 christoph_s Assigned To subik => jghali
2014-01-10 00:17 christoph_s Status resolved => closed
2014-01-10 00:17 christoph_s Fixed in Version => 1.4.3