Re: [PROPOSAL] Using code128 instead of code39 for barcode generation

[Pritam Kute]

Yes, definitely we can use code128 all over the application.

Kind Regards,
--
Pritam Kute


On Sat, Mar 30, 2019 at 2:53 PM Aditya Sharma <
aditya.sha...@hotwaxsystems.com> wrote:

> +1
>
> Thanks and Regards,
> *Aditya Sharma* | Enterprise Software Engineer
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore,
> M.P 452010
> Linkedin: *Aditya Sharma* 
>
>
>
> On Sat, Mar 30, 2019 at 2:14 PM Rishi Solanki 
> wrote:
>
> > +1
> >
> > Best,
> > --
> > *Rishi Solanki* | Sr Manager, Enterprise Software Development
> > HotWax Systems 
> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> > Indore,
> > M.P 452010
> > Linkedin: *Rishi Solanki*
> > 
> > Direct: +91-9893287847
> >
> >
> > On Sat, Mar 30, 2019 at 12:19 PM Pawan Verma <
> > pawan.ve...@hotwaxsystems.com>
> > wrote:
> >
> > > Hello All,
> > >
> > > While researching on OFBIZ-10743, I have found that currently, we are
> > using
> > > code39 to generate barcodes but there are some limitations of code39 as
> > it
> > > only able to encrypt letters from A to Z, digits from 0 to 9 and an
> > > additional set of special characters – “. $ % + – / *”.
> > >
> > > To enhance the support for more characters in barcode I would suggest
> > using
> > > code128 instead of code39.
> > >
> > > Below are some of the advantages of code128:
> > >
> > >1. code128 supports all the 128 ASCII symbols.
> > >2. code128 standard is more concise and space-efficient. It also
> > >provides its users with higher degrees of data security.
> > >
> > >
> > > Thank You *Pritam Kute* for suggesting code128.
> > >
> > > Everyone, Please share your thoughts on this. Thanks!
> > >
> > > --
> > > Kind Regards,
> > > *Pawan Verma* | Technical Consultant
> > > HotWax Systems 
> > > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> > > Indore,
> > > M.P. 452010
> > > Linkedin: *Pawan Verma <
> > https://www.linkedin.com/in/pawan-verma-aa1053a2/
> > > >*
> > >
> >
>

Re: [PROPOSAL] Using code128 instead of code39 for barcode generation

[Aditya Sharma]

+1

Thanks and Regards,
*Aditya Sharma* | Enterprise Software Engineer
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Aditya Sharma* 



On Sat, Mar 30, 2019 at 2:14 PM Rishi Solanki 
wrote:

> +1
>
> Best,
> --
> *Rishi Solanki* | Sr Manager, Enterprise Software Development
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore,
> M.P 452010
> Linkedin: *Rishi Solanki*
> 
> Direct: +91-9893287847
>
>
> On Sat, Mar 30, 2019 at 12:19 PM Pawan Verma <
> pawan.ve...@hotwaxsystems.com>
> wrote:
>
> > Hello All,
> >
> > While researching on OFBIZ-10743, I have found that currently, we are
> using
> > code39 to generate barcodes but there are some limitations of code39 as
> it
> > only able to encrypt letters from A to Z, digits from 0 to 9 and an
> > additional set of special characters – “. $ % + – / *”.
> >
> > To enhance the support for more characters in barcode I would suggest
> using
> > code128 instead of code39.
> >
> > Below are some of the advantages of code128:
> >
> >1. code128 supports all the 128 ASCII symbols.
> >2. code128 standard is more concise and space-efficient. It also
> >provides its users with higher degrees of data security.
> >
> >
> > Thank You *Pritam Kute* for suggesting code128.
> >
> > Everyone, Please share your thoughts on this. Thanks!
> >
> > --
> > Kind Regards,
> > *Pawan Verma* | Technical Consultant
> > HotWax Systems 
> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> > Indore,
> > M.P. 452010
> > Linkedin: *Pawan Verma <
> https://www.linkedin.com/in/pawan-verma-aa1053a2/
> > >*
> >
>

Re: [Discussion] Username should allow space/special characters?

[Rishi Solanki]

Hi Ayushi,
Thanks for your concern and reporting. In OFBiz we use email address as
user name. So all the characters allowed in email address should be allowed
in user name.
In your case it seems you are not using email address as user name, in that
case as well I would say email address practices should follow. As it is
globally accepted and known to general users.

If community agree on some point to allow other characters in user name
then we should look for the practices adaption at global level and then we
can decide how should we proceed. Again my vote is to go with email address
practice which is already accepted at [1].

[1] https://en.wikipedia.org/wiki/Email_address

Best Regards,
--
*Rishi Solanki* | Sr Manager, Enterprise Software Development
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Rishi Solanki*

Direct: +91-9893287847


On Sat, Mar 30, 2019 at 1:00 PM Ayushi Rathod 
wrote:

> Hello All,
>
> While exploring e-commerce I found that when I register as a new customer
> with a space in the username field, a weird server side error is shown on
> the UI.
>
> The question arrives here, whether space or any other characters should be
> allowed in the username or not.
>
> In my opinion, space should not be allowed in the username and the possible
> way to handle is that we can add client and server side validations to
> check if the username matches the regex.
>
> This issue has been reported under OFBIZ-10671. Please let me know your
> view on it so that we can fix the issue.
>
> Thanks in advance!!
>
> Kind Regards,
> *Ayushi Rathod*
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore,
> M.P 452010
> Linkedin: *Ayushi  Rathod*
> 
>

Re: [PROPOSAL] Using code128 instead of code39 for barcode generation

[Rishi Solanki]

+1

Best,
--
*Rishi Solanki* | Sr Manager, Enterprise Software Development
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Rishi Solanki*

Direct: +91-9893287847


On Sat, Mar 30, 2019 at 12:19 PM Pawan Verma 
wrote:

> Hello All,
>
> While researching on OFBIZ-10743, I have found that currently, we are using
> code39 to generate barcodes but there are some limitations of code39 as it
> only able to encrypt letters from A to Z, digits from 0 to 9 and an
> additional set of special characters – “. $ % + – / *”.
>
> To enhance the support for more characters in barcode I would suggest using
> code128 instead of code39.
>
> Below are some of the advantages of code128:
>
>1. code128 supports all the 128 ASCII symbols.
>2. code128 standard is more concise and space-efficient. It also
>provides its users with higher degrees of data security.
>
>
> Thank You *Pritam Kute* for suggesting code128.
>
> Everyone, Please share your thoughts on this. Thanks!
>
> --
> Kind Regards,
> *Pawan Verma* | Technical Consultant
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore,
> M.P. 452010
> Linkedin: *Pawan Verma  >*
>

[Discussion] Username should allow space/special characters?

[Ayushi Rathod]

Hello All,

While exploring e-commerce I found that when I register as a new customer
with a space in the username field, a weird server side error is shown on
the UI.

The question arrives here, whether space or any other characters should be
allowed in the username or not.

In my opinion, space should not be allowed in the username and the possible
way to handle is that we can add client and server side validations to
check if the username matches the regex.

This issue has been reported under OFBIZ-10671. Please let me know your
view on it so that we can fix the issue.

Thanks in advance!!

Kind Regards,
*Ayushi Rathod*
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Ayushi  Rathod*