When will the packing slip and invoice format be fixed?

Question

Packing slips and invoices put all products in one column which gives poor formatting that is not suitable for use as a picking slip (using packing slip).  If the code below is used:
                    <table width="100%" cellspacing="0" cellpadding="6" class="border">
                        <tbody>
                            <tr>
                                <td style="width: 10%;"><span>Product Code</span></td>
                                <td style="width: 20%;"><span>Product</span></td>
                                <td style="width: 30%;"><span>Description</span></td>
                                <td style="width: 10%;"><span>Unit Price</span></td>
                                <td style="width: 10%;"><span>Tax</span></td>
                                <td style="width: 10%;"><span>Quantity</span></td>
                                <td style="width: 10%;"><span>Total</span></td>
                            </tr>
                            <tr class="text">
                                <td style="width: 10%;">{tag_productcode}</td>
                                <td style="width: 20%;">{tag_productname}</td>
                                <td style="width: 30%;">{tag_productdescription}</td>
                                <td style="width: 10%;">{tag_productextaxamount}</td>
                                <td style="width: 10%;">{tag_producttaxamount}</td>
                                <td style="width: 10%;">{tag_productquantity}</td>
                                <td style="width: 10%;">{tag_producttotal}</td>
                            </tr>
                        </tbody>
                    </table>
Or any variations on width and other types of formatting the output isn't usable as all the product codes are in one cell, all the product names in another cell etc and none line up if the content is wider than the cells.
As the information is sent by email various CSS and javascript techniques can't be used.
When is BC going to be fixed so each product code, product desc etc is in its own cell and related items are on the same row?
Another topic (although closely related to this), I started using BC because it was a powerful tool that was being improved constantly with new features and issues fixed.  The last 12 months have seen a very static system that isn't meeting my clients needs and problems like the one here aren't being fixed.  It honestly can't be called a packing slip or invoice if the rows don't line up and if the system isn't going to be fixed then time to start chosing a system that will be.
There needs to be a features roadmap and problems like this need to be fixed.
Unhappy Jan.

Answer 1

Liam,
Just to clarify "Not happy Jan" is a joke here in Australia based on a TV commercial.
I don't think I have missed the point as my customers are demanding from me that problems with the system are fixed and that functions they would like are added.  In the end they will chose the system that does what they need.  I know strong foundations are vitally important BUT my clients don't ask for strong foundations, they ask for functionality and while other systems have been adding functionality and fixing problems (or at least having solutions for problems) BC hasn't.  I don't want to change to another system as I have invested a lot of time and effort into BC but it is a tough sell when silly problems (my issue which is the result of a poorly structured system for this function) aren't able to be rectified.  Yes I can restyle but in the end I can't have the output I need or should be able to have.
I felt much more comfortable with the system when there were frequent updates that added features and fixed broken components.  There have been a few additions this year and some have been great - additional users, dynamic content in newsletters - but I want to see more.  Our competitors are using products that are evolving all the time and extensible so to keep up we must have a tool that if it isn't going to be properly extensible (and I get why it isn't and am comfortable with that) it needs to be dynamic, adding functions and fixing problems. 
In the end if I or other businesses like mine move to another system we won't be coming back and there lies the issue for BC.