I have 3 publish ranges in this Zoho spreadsheet that I have arranged side-by-side (horizontally) with a couple of empty columns in between each range.  The first range begins in column A and ends in column G and when I insert that range into this web page page, the columns are the widths set in the spreadsheet. 

The problem is the column widths of the 2nd and 3rd published ranges do NOT display on a web page with the correct widths.  And, if I leave the ranges in their current positions, there does not appear to be anything that I can do with either the spreadsheet or the HTML code to fix this problem.

There does appear to be one "work around", albeit a very unsatisfactory one ...
If the published ranges are arranged vertically, in the same columns, starting with column A, then all of them have the correct widths when published on a web page.  I know this because I have this spreadsheet where I have two published ranges arrange in just that way and they are displayed on this web page.

However, because each range is simply the same data with different sorting, this "work around" is unsatisfactory.
Here's why:

• When adding/or deleting entries from the first range, the number of rows in each range needs to be kept "in sync".
  So, ideally, by arranging the ranges horizontally, on the same rows, adding or deleting rows becomes a one step operation and has a much greater assurance that the ranges will stay in sync.
  Arranging them vertically means that adding/deleting the same number of rows has to be done as a separate step to each range and means there is a greater chance for error or for the ranges to become out of sync.
  
  
• The code for the macros becomes more complicated. 
  This spreadsheet uses macros so that, when updating scores or adding new scores... the user simply edits the first range, then uses macros to update and format the 2nd and 3rd published ranges.  If the ranges are horizontal, then the beginning of each range is already known.  But when they're arranged vertically, the beginning of the 2nd and 3rd range has to be determined programatically. which is more error prone and also causes the macros to run that much longer.