[Kbarcode] release 3.0.0b3

[<kba...@ce...>]

Hi,

KBarcode 3.0.0b3 has been released.
Source and a deb package for amd64 architecture are available 
on http://sourceforge.net/projects/kbarcode/files/Development/3.0.0b3/
Installation instructions for Debian/Ubuntu are also on the page.

3.0.0b3 is still beta and it is released for the purpose of testing by users.
Please, report all bugs that you willl see. 
To do it visit either http://sourceforge.net/p/kbarcode/bugs/ 
or send an email to mailing lists on 
http://sourceforge.net/mailarchive/forum.php?forum_name=kbarcode-users .


Summary of changes since 3.0.0b2:

KBarcode-kde4 has been renamed back to KBarcode. 
Sorry for the mess, it is my fault.

Fixed and upgraded implementation of Barcode Writer in Pure Postscript.
Version 3.0.0b3 uses the version 2013-01-17-1 
of Barcode Writer In Pure Postscript (BWIPP).
So you are able to create QR code, Aztec Code 
and many other codes with KBarcode.
Do you want to use a more up-to-date version 
of Barcode Writer in Pure Postscript with KBarcode?
You can specify which version of BWIPP placed on your system 
to use via KBarcode's configuration dialog.

Fixed TBarcode support.

Fixed moving multiple items.

Added Ukrainian localization.
Updated German localization.

Small gui enhancements.


Known bugs:

The size of generated pdf files is huge.
The application Glabels seems to have the correct and the most efficient way 
of generating pdf files. We'll have a look at it and see what we can do.

In chroot jail environment I noted that when a label editor is started
and a label is chosen then a default label is displayed instead of the chosen one.
The chosen label is displayed only after inserting an item or moving the scroll bar.
The bug doesn't emerge on my normal system but it can emerge on some systems. 
If it does, please, report it. I want to know how common this bug is.

Also in chroot jail environment initially I wasn't able to switch application language 
via "Switch Application Language" in Help menu. 
http://serverfault.com/a/344423 solved the issue for me.


Regards,

Fanda