It's because when you're editing the document it has the print layout (they used to have an option to edit in a different view but not anymore) and when you are publishing it they are removing the page layout and showing only the contains as an html page.
If you want to preserve the page layout for the published document as well and make it look exactly the same as in edit mode, then you have two options. From the sharing options select one of the following:
- Public on the web
- Anyone with the link
and you will get in both cases a link that will look exactly the same. The only downside with these options is that everybody will be able to see who is currently viewing your document.
Here is a screenshot of these two options:
![alt text](https://i.stack.imgur.com/A0qMQ.png)
I'm afraid this is more answering "do you have any idea?" rather than giving a solution.
The primary issue here is your locale, as mentioned in your comment on the question. Custom number formats are not agnostic to the locale-specific number formats. In the case of the UK locale, commas are regarded as thousands separators, and periods are regarded as decimal separators. So your custom format #,#" days"
is essentially just instructing Sheets to format with a comma as a thousands separator, with no decimal places (it is functionally equivalent to #,###" days"
.
As you saw, when you directly enter 1,5
, this isn't formatted at all, because in the UK locale this is not recognised as a valid number (or date, or anything numeric), and is stored as a text string.
So an option is to change to a locale that uses a comma as a decimal separator (eg Italy). However (and this is a big "however") I have had a lot of trouble getting the custom formats to work in such locales; the implementation appears to leave a bit to be desired.
Another option is to keep your current locale, and make do with a period for a decimal separator, and use the format #.# "days"
. The "however" here is that the decimal point is included even when it is not needed (ie whole numbers), which is irritating, and I don't know of a workaround in Sheets using custom formatting alone.
A third option is to use spreadsheet formulae to reproduce the values in the appropriate format. The reproduced data would be text strings, so you should still reference the raw values (which might be in a column that could be hidden) in formulae. Downside is of course the duplication of data and reduced usability.
And lastly, Google Apps Script could auto convert values to text strings in the desired format; again you would have to consider formulae that reference these cells.
I hope this gives some insight, and I really hope to be able to delete this answer if someone has a watertight solution that can be achieved in custom formatting alone.
Best Answer
cases
isn't natively supported by Google Documents as you can see in the list of supported LaTeX operators†. Some projects try to extend GDoc's LaTeX capabilities.† Not at present, but Wayback Machine has a copy: https://web.archive.org/web/20160409034821/https://support.google.com/docs/answer/160749?hl=en