Saturday, October 08, 2016

My ongoing argument with Zazzle

A message I submitted on their Contact Us page:



The problem with fonts being displayed differently on different tees still hasn't been addressed after existing for several years. Please address this issue.

In the attached image of a tee design, which is found at http://www.zazzle.com/bird_of_paradise_t_shirt-235501214256001306, it's obvious that the design on the first two tees has been corrupted compared to the identical design on the remaining tees. There is only one design, composed of parentheses from the Typo Upright and French fonts at different point sizes, and the design on each of the tees should be identical. If you'll click on See All Styles and scroll down through the styles, you'll see that the problem appears on some of the tees but not all.

The tees which display a corrupted design seem to have a zone around the edges of the printable area that will change the point size of any text object that extends into it. The tees which don't corrupt the design don't have this zone, and image files are unaffected by this zone. I believe that an effort was made to keep designers' texts from extending outside the printable area some time ago, but the project wasn't completed and so some of the tees don't display this function. It may be that the project was abandoned because it was seen not to work, but it was left in place on the tees that had been altered.

It seems that it would be a simple matter to go into the code that controls how, for example, the Women's Basic T-Shirt and the Women's American Apparel Fine Jersey T-Shirt, treats text, and remove that function. This should be done for the sake of the customer shopping for tees. The customer could find a design they like but see that the design is corrupted on the tee they're interested in, and so they don't purchase the item. One wonders how many lost sales have resulted from this glitch over the years.

The design tool is pretty awesome otherwise, and I'm surprised that other POD sites haven't implemented something like it.

Thanks.

No comments: